All of lore.kernel.org
 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:07:55 -0500	[thread overview]
Message-ID: <1123776475.5062.22.camel@mulgrave> (raw)
In-Reply-To: <547AF3BD0F3F0B4CBDC379BAC7E4189F01684D52@otce2k03.adaptec.com>

On Thu, 2005-08-11 at 11:51 -0400, Salyzyn, Mark wrote:
> The problem with pushing this policy to the user is that software
> applications have no means to determine that a device is currently
> in-use. For instance, the net result of pulling a device on a mounted
> filesystem is an eventual kernel panic.

The kernel only panics if you told it to with the mount option
errors=panic (or if you have errors=panic set in the superblock flags).

For file systems on removable devices you shouldn't be telling it to
panic on error, you should be telling it to continue or remount-ro.  If
you do this then you can happily yank the undelying device on a mounted
fs, which was one of the design goals of the 2.6 SCSI state model and
refcounting reworks.

James



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

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11 15:51 remove-single-device removes mounted HDDs (kernel 2.6) Salyzyn, Mark
2005-08-11 16:07 ` James Bottomley [this message]
2005-08-11 17:40   ` Bryan Henderson
2005-08-11 22:06     ` Stefan Richter
  -- 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 16:37 Salyzyn, Mark
2005-08-11 16:53 ` James Bottomley
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=1123776475.5062.22.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 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.