All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "Darrick J. Wong" <djwong@us.ibm.com>
Cc: Krzysztof B??aszkowski <kb@sysmikro.com.pl>,
	linux-scsi@vger.kernel.org, vst@vlnb.net,
	Alexis Bruemmer <alexisb@us.ibm.com>
Subject: Re: aic94xx or libsas crash on X7DB3 supermicro with enclosure and sata drives
Date: Mon, 03 Dec 2007 14:43:09 -0500	[thread overview]
Message-ID: <47545C4D.1070708@garzik.org> (raw)
In-Reply-To: <20071203193652.GB7066@tree.beaverton.ibm.com>

Darrick J. Wong wrote:
> On Mon, Dec 03, 2007 at 05:09:54PM +0100, Krzysztof B??aszkowski wrote:
>> I noticed also another failure when i removed a drive. The event was not 
>> notified by anything (ie the block device and corresponding sg were 
>> registered) so i run dd on this truly "virtual" drive.
>>
>> dd reached D state (as well as scsi_wq) . i think it shouldn't happen no 
>> matter it was AIC failure or LSI expander failure.
> 
> "It's wireless!" ;)
> 
> Seriously, though, it's a good idea to tell the kernel that you're
> about to unplug a disk before actually doing it:
> 
> echo 1 > /sys/block/sdX/device/delete
> 
> This way, the kernel can tell the disk to flush its caches long before
> power actually gets removed.  Otherwise, the device removal code can
> get hung up just like you observed, and whatever's in the write cache
> may or may not actually get written to the media.


What you say is quite true about write cache -- you can clearly lose 
some data by hot-unplugging a device.  And there's nothing we can do 
about that.

But what do you mean by "device removal code can get hung up"?  That 
sounds like a bug we should fix.

	Jeff



  reply	other threads:[~2007-12-03 19:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30  9:22 aic94xx or libsas crash on X7DB3 supermicro with enclosure and sata drives Krzysztof Błaszkowski
2007-11-30 21:33 ` Darrick J. Wong
2007-12-03 15:11   ` Krzysztof Błaszkowski
2007-12-03 16:09   ` Krzysztof Błaszkowski
2007-12-03 19:36     ` Darrick J. Wong
2007-12-03 19:43       ` Jeff Garzik [this message]
2007-12-03 21:31         ` Darrick J. Wong
2007-12-03 20:06       ` Krzysztof Błaszkowski
2007-12-04 22:35         ` [PATCH] libsas: Don't issue commands to devices that have been hot-removed Darrick J. Wong
2007-12-04 22:48           ` Jeff Garzik
2007-12-04 23:17             ` Darrick J. Wong
2007-12-04 23:40               ` Jeff Garzik
2007-12-06 16:55               ` Brian King
2008-02-25 23:39               ` Jeff Garzik

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=47545C4D.1070708@garzik.org \
    --to=jeff@garzik.org \
    --cc=alexisb@us.ibm.com \
    --cc=djwong@us.ibm.com \
    --cc=kb@sysmikro.com.pl \
    --cc=linux-scsi@vger.kernel.org \
    --cc=vst@vlnb.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.