From: Mike Fedyk <mfedyk@matchmail.com>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
=?unknown-8bit?Q?ChristianBorntr=E4ger?=
<christian@borntraeger.net>,
linux-kernel@vger.kernel.org, andre@linux-ide.org
Subject: Re: some ide-scsi commands starve drives on the same cable
Date: Mon, 18 Mar 2002 08:24:43 -0800 [thread overview]
Message-ID: <20020318162443.GH2254@matchmail.com> (raw)
In-Reply-To: <E16mIEq-0006nO-00@the-village.bc.nu> <3C95E7E3.4020300@evision-ventures.com>
On Mon, Mar 18, 2002 at 02:13:07PM +0100, Martin Dalecki wrote:
> Alan Cox wrote:
> >>during some activities (e.g. erasing a CDRW or fixating a CDR on my
> >>CD-Burner) the hard disc on the same cable cannot be accessed.All data
> >>and swap partitions are inaccessable. There is no dmesg output, just
> >>entering the
> >>mount point fails.
> >>I am not sure if it is a kernel problem or if it is a firmware-bug.
> >
> >
> >Neither. Its an IDE design limitation. IDE can't handle disconnects like
> >real scsi does. The fixate command effectively locks the bus until it
> >completes.
> >
> >There has been some movement forward in the standards on this. You might
> >want to ask our new 2.5 IDE maintainer if/when it will be implemented - I
> >suspect you have to wait a while though. There is much IDE to clean up
> >first
>
> Just for the record: I'm aware of it.
>
That doesn't say much about your plans for it though.
next prev parent reply other threads:[~2002-03-18 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 13:58 some ide-scsi commands starve drives on the same cable Christian Bornträger
2002-03-16 17:45 ` Alan Cox
2002-03-18 13:13 ` Martin Dalecki
2002-03-18 16:24 ` Mike Fedyk [this message]
2002-03-18 16:30 ` Christian Bornträger
2002-03-18 16:37 ` Martin Dalecki
2002-03-18 17:16 ` 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=20020318162443.GH2254@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=christian@borntraeger.net \
--cc=dalecki@evision-ventures.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