lkml.org 
[lkml]   [2001]   [Mar]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.2.18 IDE tape problem, with ide-scsi
Camm Maguire wrote:
>The third error I get is:
>
>Feb 27 16:01:45 intech9 kernel: st0: Error: 28000000, cmd: 8 1 0 0 40 0 Len: 16
>Feb 27 16:01:45 intech9 kernel: Info fld=0x40, FMK Current st09:00: sns = f0 80
>Feb 27 16:01:45 intech9 kernel: ASC= 0 ASCQ= 1
>Feb 27 16:01:45 intech9 kernel: Raw sense data:0xf0 0x00 0x80 0x00 0x00 0x00 0x40 0x0a 0x00 0x00 0x00 0x00 0x00 0x01 0x00 0x00
>Feb 27 16:01:45 intech9 kernel: st0: Sense: f0 0 80 0 0 0 40 a
>Feb 27 16:01:45 intech9 kernel: st0: EOF detected (0 bytes read).
>
>Restoring a tape typically then says 'gunzip: unexpected end of
>file'. My guess was that the last fractional block of 32k wasn't
>flushed to the drive. Of course, if I'm having media troubles
>indicated by the first error above, then something else could be
>happening, I suppose. But does erroneous block flushing in the driver
>sound like a possibility?

Above sense data indicates drive has encountered a filemark on a READ
command. This READ did not read a partial block since the residual count
in Sense data is set to 0x40 which is the same block count requested by
the READ command. If you were writing 32K blocks to the tape and there
indeed was a partial block at the end, the current position of the tape
is not at that partial block. Tape seems to be positioned immediately
after the last block where a filemark was written indicating end of
archive.

Looking at the READ command (8 1 0 0 40 0), the "fixed" bit is set which
means the tape is being read in fixed block length mode. This read
command is trying to read 64 blocks from the tape. If the application is
reading data in blocks of 32K, it implies the block size on the physical
media is 512 Bytes. So when you say last 32K block may not have been
flushed to the drive, I am assuming you mean not being flushed from the
host to the tape drive. This is possible but there may be something else
going on. I would suggest setting no block limits on the drive using "mt
stsetoptions no-blklimits". See if that helps.

====================================================================
Khalid Aziz Linux Development Laboratory
(970)898-9214 Hewlett-Packard
khalid@fc.hp.com Fort Collins, CO
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:29    [W:0.067 / U:3.740 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site