From: maximilian attems <max@stro.at>
To: Borislav Petkov <bbpetkov@yahoo.de>
Cc: linux-ide@vger.kernel.org, Stephen Kitt <steve@sk2.org>
Subject: (fwd) Bug#11922: I/O error on blank tapes
Date: Mon, 4 Feb 2008 15:22:06 +0100 [thread overview]
Message-ID: <20080204142206.GB5532@stro.at> (raw)
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@sk2.org> -----
Subject: Bug#11922: I/O error on blank tapes
Date: Sat, 1 Dec 2007 19:06:18 +0100
From: Stephen Kitt <steve@sk2.org>
To: 11922@bugs.debian.org
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@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
----- End forwarded message -----
next reply other threads:[~2008-02-04 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 14:22 maximilian attems [this message]
2008-02-04 21:28 ` (fwd) Bug#11922: I/O error on blank tapes Borislav Petkov
2008-02-04 21:49 ` Stephen Kitt
2008-02-04 21:56 ` James Bottomley
2008-02-05 16:56 ` Kai Makisara
2008-02-10 21:23 ` Kai Makisara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080204142206.GB5532@stro.at \
--to=max@stro.at \
--cc=bbpetkov@yahoo.de \
--cc=linux-ide@vger.kernel.org \
--cc=steve@sk2.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).