On Mon, Feb 04, 2008 at 03:22:06PM +0100, maximilian attems wrote: (Added Bart to CC) > hello borislav, > > may i forward you that *old* Debian kernel bug, > have seen you working on ide-tape: > http://bugs.debian.org/11922 > no we don't carry any ide patches anymore. > > maybe you've already fixed it in latest? > > thanks > > -- > maks > > ----- Forwarded message from Stephen Kitt <steve@xxxxxxx> ----- > > Subject: Bug#11922: I/O error on blank tapes > Date: Sat, 1 Dec 2007 19:06:18 +0100 > From: Stephen Kitt <steve@xxxxxxx> > To: 11922@xxxxxxxxxxxxxxx > > Hi, > > This does still occur with 2.6.22; with a blank tape in my HP DDS-4 drive: > > $ tar tzvf /dev/nst0 > tar: /dev/nst0: Cannot read: Input/output error > tar: At beginning of tape, quitting now > tar: Error is not recoverable: exiting now > > gzip: stdin: unexpected end of file > tar: Child returned status 2 > tar: Error exit delayed from previous errors > > Nothing gets logged anywhere, which fits the original bug description. > > This is a well-known issue: see for example > http://www.sibbald.com/bacula/html-manual/Bacula_Console.html (search for > "blank tape"). > > Regards, > > Stephen > > > > -- > To UNSUBSCRIBE, email to debian-kernel-REQUEST@xxxxxxxxxxxxxxxx > with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx > > > ----- End forwarded message ----- Hi Maks, we're currently in the process of aggressively cleaning up ide-tape. However, this brings (almost) no functional changes to the driver and we haven't looked at any bugs that might exist. Actually, I wanted to probe the community to see whether anyone is using ide-tape at all, and if not, to remove it completely. Since i don't have the hardware, i'm gonna have to ask you (or Stephen) to wait until all changes have entered mainline and then to try to reproduce the bug again after having enabled debugging (IDETAPE_DEBUG_LOG) and send me the syslog output. Thanks. -- Regards/Gruß, Boris. - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
