From: Mike Dresser <mdresser@windsormachine.com>
To: Camm Maguire <camm@enhanced.com>
Cc: Khalid Aziz <khalid@fc.hp.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.2.18 IDE tape problem, with ide-scsi
Date: Tue, 27 Feb 2001 13:34:40 -0500 [thread overview]
Message-ID: <3A9BF340.B8DD9F56@windsormachine.com> (raw)
In-Reply-To: <54u25g3yb9.fsf_-_@intech19.enhanced.com> <3A9BC2A9.F5EE8554@fc.hp.com> <544rxg2gde.fsf@intech19.enhanced.com> <3A9BE4C1.1868F020@windsormachine.com> <54u25gvuyg.fsf@intech19.enhanced.com>
Camm Maguire wrote:
> Greetings! You are certainly right here, at least in part. The ide
> patches for 2.2 definitely impair tape operation on these boxes.
> There was a crude workaround suggested on this list to use the
> ide-scsi driver -- this basically worked, but gave *many* error
> messages in the kernel log, and was significantly less reliable than
> stock 2.2.18. I'm still using ide-scsi out of inertia, but I suspect
> that ide-tape might be just fine with stock 2.2.18 too. And when I
> saw some support for the ALI chipset, the decision was clear to drop
> the latest ide stuff.
>
> This has been the situation for some time. Is this going to be
> resolved soon?
Wish i knew, I'm praying that 2.2.19 hasn't/doesn't implement the ide patches like 2.4.x did. If so, and a major problem is found in
2.2.18, then I have to maintain another machine running 2.2.18 to restore tapes. Also means i'd have to stop using taper or dump,
and stick to tar only, as both want to read the tape back in at some point.
Mike
next prev parent reply other threads:[~2001-02-27 18:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 16:06 2.2.18 IDE tape problem, with ide-scsi Camm Maguire
2001-02-27 15:07 ` Khalid Aziz
2001-02-27 17:19 ` Camm Maguire
2001-02-27 15:34 ` Khalid Aziz
2001-02-27 19:52 ` Camm Maguire
2001-02-27 18:18 ` Khalid Aziz
2001-02-27 20:26 ` Andre Hedrick
2001-02-27 21:26 ` Khalid Aziz
2001-02-28 15:23 ` Camm Maguire
2001-02-28 15:34 ` Mike Dresser
2001-03-07 22:54 ` Camm Maguire
2001-03-12 16:52 ` Khalid Aziz
2001-03-13 14:14 ` Camm Maguire
2001-02-27 17:32 ` Mike Dresser
2001-02-27 18:31 ` Camm Maguire
2001-02-27 18:34 ` Mike Dresser [this message]
2001-02-27 19:05 ` Andre Hedrick
2001-02-27 19:40 ` Camm Maguire
2001-03-01 17:02 ` Khalid Aziz
2001-02-27 22:21 ` Alan Cox
2001-02-27 19:01 ` Andre Hedrick
2001-02-27 19:04 ` Mike Dresser
2001-03-07 0:34 ` [PATCH] " Chip Salzenberg
2001-03-07 1:09 ` Andre Hedrick
[not found] <Pine.LNX.4.10.10102271153560.29323-100000@coffee.psychology.mcmaster.ca>
2001-02-27 17:16 ` Camm Maguire
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=3A9BF340.B8DD9F56@windsormachine.com \
--to=mdresser@windsormachine.com \
--cc=camm@enhanced.com \
--cc=khalid@fc.hp.com \
--cc=linux-kernel@vger.kernel.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).