From: James Bottomley <James.Bottomley@steeleye.com>
To: dougg@torque.net
Cc: Christoph Hellwig <hch@infradead.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
ballen@gravity.phys.uwm.edu
Subject: Re: [2.6.0-test4] blocking access to mounted scsi devices
Date: 26 Aug 2003 09:08:54 -0500 [thread overview]
Message-ID: <1061906937.1830.11.camel@mulgrave> (raw)
In-Reply-To: <3F4B3482.4060304@torque.net>
On Tue, 2003-08-26 at 05:20, Douglas Gilbert wrote:
> Christoph Hellwig wrote:
> > That's because both mount (or e.g. volume managers) claims
> > devices for exclusive use, as does drivers/block/scsi_ioctl.c
>
> Well it is reasonable that mount should exclude other attempts
> to mount. However the device holding the root file system
> may be an ATA or SCSI disk and the ide-disk and sd drivers
> do not support SMART probing directly.
Hang on, that's not the way it's supposed to work.
Mount should be on partition devices (like /dev/sda1) whereas the tools
should be on whole disc devices (like /dev/sda). I thought we'd agreed
that even opening a partition exclusively wouldn't affect the ability to
open the whole disc device (but opening the whole disc device
exclusively would block access to all partitions).
Therefore, the only issue we should have is with volume managers that
need to open whole disc devices exclusively, and possibly with the
device mapper.
James
next prev parent reply other threads:[~2003-08-26 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 7:04 [2.6.0-test4] blocking access to mounted scsi devices Douglas Gilbert
2003-08-25 12:08 ` Christoph Hellwig
2003-08-26 10:20 ` Douglas Gilbert
2003-08-26 14:08 ` James Bottomley [this message]
2003-08-26 14:32 ` Christoph Hellwig
2003-08-26 14:57 ` James Bottomley
2003-08-26 16:23 ` Bruce Allen
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=1061906937.1830.11.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=ballen@gravity.phys.uwm.edu \
--cc=dougg@torque.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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