From: Jens Axboe <axboe@suse.de>
To: Mike Dresser <mdresser@windsormachine.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: issues with ide-tape under 2.4.x and with 2.2.x+ide patches
Date: Thu, 2 Nov 2000 19:54:03 -0800 [thread overview]
Message-ID: <20001102195403.A18806@suse.de> (raw)
In-Reply-To: <3A017F1E.C699593A@windsormachine.com>
In-Reply-To: <3A017F1E.C699593A@windsormachine.com>; from mdresser@windsormachine.com on Thu, Nov 02, 2000 at 09:50:07AM -0500
On Thu, Nov 02 2000, Mike Dresser wrote:
> I'm currently running 2.4.0test10, running backups onto an IDE HP 7/14
> gb drive. Using tar -cpvf /dev/ht0 myfiles backs up fine, no errors.
>
> But..
>
> promise:~# tar -tf /dev/ht0
> tar: /dev/ht0: Cannot read: Input/output error
> tar: At beginning of tape, quitting now
> tar: Error is not recoverable: exiting now
>
> and from dmesg:
> ide-tape: ht0: I/O error, pc = 1e, key = 5, asc = 20, ascq = 0
> ide-tape: ht0: I/O error, pc = 8, key = 5, asc = 2c, ascq = 0
> ide-tape: ht0: I/O error, pc = 1e, key = 5, asc = 20, ascq = 0
>
> (normal, i get those cause of the lock drive/unlock drive, which the
> drive doesn't support)
Interesting, and this is test10? I submitted a patch for test10 to
not attempt prevent-removal commands in the ide-tape drives that
do not support it. If this is indeed test10, that would mean that
the HP drive misreports that capability. It'd be nice to know.
--
* Jens Axboe <axboe@suse.de>
* SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-03 2:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-02 14:50 issues with ide-tape under 2.4.x and with 2.2.x+ide patches Mike Dresser
2000-11-03 3:54 ` Jens Axboe [this message]
2000-11-03 14:38 ` Mike Dresser
2000-11-06 15:02 ` Mike Dresser
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=20001102195403.A18806@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mdresser@windsormachine.com \
/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