lkml.org 
[lkml]   [1999]   [Jan]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [BUG] Tape access broken in 2.2.0pre
    More info.  after mt setblk 0, mt tell no longer works properly.  Something
    has changed very much between 2.0.x and here, and it's not a change for the
    better apparently.

    Hmm.

    Any hints at all?

    On Fri, Jan 08, 1999 at 09:07:52PM -0600, John Goerzen wrote:

    > Oops, forgot to send this to the list.
    >
    > On Fri, Jan 08, 1999 at 02:32:30PM +0100, Harald Koenig wrote:
    >
    > > this write error can also happen when your EXABYTE is not using variable blocks
    > > (block size 0) and you are (cat is) trying to write blocks which are not
    > > integer multiples of the tape block size.
    > > check the output of `mt stat' or similar, maybe someone changed the setting
    > > of your drive ?!
    >
    > Interesting:
    >
    > drive type = Generic SCSI-2 tape
    > drive status = 1024
    > sense key error = 0
    > residue count = 0
    > file number = -1
    > block number = -1
    > Tape block size 1024 bytes. Density code 0x0 (default).
    > Soft error count since last status=0
    > General status bits on (1010000):
    > ONLINE IM_REP_EN
    >
    > I tried mt setblk 0. That fixed the problem. But:
    >
    > 1. Why do I need to do this now when I didn't have to do so before?
    >
    > 2. What exactly does this control?
    >

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:49    [W:0.019 / U:2.956 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site