On Wed, 1 Dec 2010, Lukas Kolbe wrote: > Am Dienstag, den 30.11.2010, 18:20 +0200 schrieb Kai Makisara: > ... > > If you see error with 64 kB block size, I would like to see any messages > > associated with these errors. > > I have now hit this bug again. Trying to read and write a label from the > tape drive in question results in this (via bacula's btape command): > > *readlabel > 01-Dec 17:47 btape JobId 0: Error: block.c:1002 Read error on fd=3 at > file:blk 0:0 on device "drv1" (/dev/nst1). ERR=Value too large for > defined data type. > btape: btape.c:525 Volume has no label. > > Volume Label: > Id : **error**VerNo : 0 > VolName : > PrevVolName : > VolFile : 0 > LabelType : Unknown 0 > LabelSize : 0 > PoolName : > MediaType : > PoolType : > HostName : > Date label written: -4712-01-01 at 00:00 > *label > Enter Volume Name: AAA543 > 01-Dec 17:47 btape JobId 0: Error: block.c:577 Write error at 0:0 on > device "drv1" (/dev/nst1). ERR=Input/output error. > 01-Dec 17:48 btape JobId 0: Error: Backspace record at EOT failed. > ERR=Input/output error > Wrote Volume label for volume "AAA543". > > dmesg says (as expected): > > [158529.011206] st1: Can't allocate 2097152 byte tape buffer. > [158544.348411] st: append_to_buffer offset overflow. > [158544.348416] st: append_to_buffer offset overflow. > [158544.348418] st: append_to_buffer offset overflow. > [158544.348419] st: append_to_buffer offset overflow. > The messages except the first one are something that should never happen. I think that there is something wrong with returning from enlarge_buffer() when it fails. I will look at this when I have time. ... > Trying to write to the tape looks like below, which seems to match your > earlier description; ie 64/65k works, 128k blocksize works, 256k > blocksize and above don't work anymore. I wasn't able to reproduce not > being able to write with a 64k blocksize at the moment. > Assuming that the MPT driver is configured for 128 segments, you should always be able to read and write 512 kB blocks. ... > I hope this somehow helps, > Lukas > These messages are helpful. Thanks, Kai -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
