From: Mark Lord <lkml@rtr.ca>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Mark Lord <lsml@rtr.ca>, Anton Blanchard <anton@samba.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Core scsi layer crashes in 2.6.8.1
Date: Tue, 05 Oct 2004 11:46:34 -0400 [thread overview]
Message-ID: <4162C1DA.5000808@rtr.ca> (raw)
In-Reply-To: <1096988167.2064.7.camel@mulgrave>
James Bottomley wrote:
>
> This is expected behaviour. For orderly removal an cache sync command
> must be sent to drives with a writeback cache before they're powered
> down. For forced ejection, the driver has to error the command.
Yup, that's how it has to be done at present.
Another weirdness I ran into at one point, was that the mid-layer
could be made to segfault if a LLD asked it to remove a drive that
had previously been set "offline" -- it complains about an illegal
state transition during the removal, and then dies. This sequence
no longer occurs in the QStor driver, but it might resurface soon
as more drivers begin to support hot insertion/removal.
Cheers
--
Mark Lord
(hdparm keeper & the original "Linux IDE Guy")
next prev parent reply other threads:[~2004-10-05 15:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 20:03 Core scsi layer crashes in 2.6.8.1 Alan Cox
2004-09-29 14:11 ` James Bottomley
2004-09-29 13:24 ` Alan Cox
2004-09-29 14:34 ` James Bottomley
2004-09-29 14:27 ` Matthew Wilcox
2004-10-05 11:49 ` Anton Blanchard
2004-10-05 13:56 ` James Bottomley
2004-10-05 14:44 ` Mark Lord
2004-10-05 14:56 ` James Bottomley
2004-10-05 15:46 ` Mark Lord [this message]
2004-10-05 15:49 ` Oliver Neukum
2004-10-05 15:54 ` James Bottomley
2004-10-05 15:57 ` Mark Lord
2004-10-05 16:01 ` James Bottomley
2004-10-05 16:53 ` Jeff Garzik
2004-10-05 16:01 ` Oliver Neukum
2004-10-05 16:07 ` James Bottomley
2004-10-05 16:26 ` Oliver Neukum
2004-10-05 16:38 ` James Bottomley
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=4162C1DA.5000808@rtr.ca \
--to=lkml@rtr.ca \
--cc=James.Bottomley@SteelEye.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsml@rtr.ca \
/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