linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Harald Seipp <SEIPP@de.ibm.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: RE: remove-single-device removes mounted HDDs (kernel 2.6)
Date: Thu, 11 Aug 2005 11:53:19 -0500	[thread overview]
Message-ID: <1123779199.5062.33.camel@mulgrave> (raw)
In-Reply-To: <547AF3BD0F3F0B4CBDC379BAC7E4189F01684D95@otce2k03.adaptec.com>

On Thu, 2005-08-11 at 12:37 -0400, Salyzyn, Mark wrote:
> Cool, must try that to see if the issues are mitigated, the issues are
> reported on Distributions in default configurations.

Well ... this was one of the nastiest features to get right; we didn't
get it fully sorted out until quite recently.  I'm not sure if the
distros backported all the fixes.  However, on a modern 2.6 based
distro, it works for me and my trusty USB stick with the latest kernel.

> Since it is a design goal to survive, then I better be putting up traces
> and submitting fs patches, rather than b*&^ing eh? I'd still feel more
> comfortable having the RAID management GUIs put up a popup box warning
> the user that what he is about to do to a device currently in-use is
> dangerous. Reporting a refcount (which covers both filesystem and direct
> i/o as used by database engines) would help.

Well ... look at it this way.  The system is designed to survive
surprise ejection (that's for USB, firewire et al.)  If you want to have
a GUI that does notified ejection then that's fine too, but it's not a
kernel issue: You clean up everything from userspace by asking nicely
and then eject the device, which we see as a surprise ejection where we
think that we fortuitously have no work to do.

James



  reply	other threads:[~2005-08-11 16:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11 16:37 remove-single-device removes mounted HDDs (kernel 2.6) Salyzyn, Mark
2005-08-11 16:53 ` James Bottomley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-06 21:28 [RFC] SCSI target for IBM Power5 LPAR Dave C Boutcher
2005-09-07 10:49 ` Christoph Hellwig
2005-09-07 12:45   ` Dave C Boutcher
2005-09-07 12:58     ` FUJITA Tomonori
2005-09-07 17:17       ` Mike Christie
2005-09-07 17:48         ` remove-single-device removes mounted HDDs (kernel 2.6) Steve Byan
2005-08-12 15:07 corene
2005-08-12 11:36 Salyzyn, Mark
2005-08-11 17:05 Salyzyn, Mark
2005-08-11 17:52 ` James Bottomley
2005-08-11 15:51 Salyzyn, Mark
2005-08-11 16:07 ` James Bottomley
2005-08-11 17:40   ` Bryan Henderson
2005-08-11 22:06     ` Stefan Richter
2005-08-11 10:09 Harald Seipp
2005-08-11 11:55 ` Douglas Gilbert
2005-08-11 16:57   ` Harald Seipp
2005-08-11 13:59 ` James Bottomley
2005-08-11 14:32   ` Harald Seipp
2005-08-11 14:46     ` Matthew Wilcox
2005-08-11 14:51     ` James Bottomley
2005-08-11 15:44       ` Harald Seipp
2005-08-11 16:40         ` Christoph Hellwig
2005-08-11 16:50           ` Harald Seipp
2005-09-06 11:43             ` Christoph Hellwig
2005-08-11 17:47         ` Bryan Henderson
2005-08-12  8:59           ` Harald Seipp

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=1123779199.5062.33.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=SEIPP@de.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.com \
    /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).