linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: No equivalent for ide-scsi available with the new PATA drivers?
Date: Mon, 23 Jul 2007 12:17:00 -0500	[thread overview]
Message-ID: <1185211020.3417.19.camel@localhost.localdomain> (raw)
In-Reply-To: <46A4DEF3.4050106@redhat.com>

On Mon, 2007-07-23 at 13:01 -0400, Chuck Ebbert wrote:
> On 07/23/2007 12:52 PM, Alan Cox wrote:
> >> People with IDE tape drives are complaining there's no ide-scsi
> >> driver available anymore with the new PATA layer. Is anyone
> >> working on one?
> > 
> > It would make no sense. The libata layer is already using the SCSI
> > midlayer so compliant devices should already appear with the st driver.
> > 
> > We might need some tape detect logic, but I don't have any tape devices
> > so its up to someone with a tape drive handy to help out...
> 
> I should have posted this earlier:

It looks like an error handling issue ... which command was being
executed at the time the tape at ata2.01 went into the error state?

I haven't looked, but it's entirely possible that it's a simple timeout
issue:  libata does some of its own error handling, but the tape
commmands have to run with timeouts set to huge values (because it can
take so long to rewind a tape or write a long block).

James



  reply	other threads:[~2007-07-23 17:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23 16:36 No equivalent for ide-scsi available with the new PATA drivers? Chuck Ebbert
2007-07-23 16:48 ` James Bottomley
2007-07-23 16:52 ` Alan Cox
2007-07-23 17:01   ` Chuck Ebbert
2007-07-23 17:17     ` James Bottomley [this message]
2007-08-02 12:24   ` Mark Lord
2007-08-07 18:53     ` Alan Cox

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=1185211020.3417.19.camel@localhost.localdomain \
    --to=james.bottomley@steeleye.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cebbert@redhat.com \
    --cc=linux-ide@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).