From: Christoph Hellwig <hch@infradead.org>
To: Douglas Gilbert <dougg@torque.net>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
ballen@gravity.phys.uwm.edu
Subject: Re: [2.6.0-test4] blocking access to mounted scsi devices
Date: Mon, 25 Aug 2003 13:08:23 +0100 [thread overview]
Message-ID: <20030825130822.A4258@infradead.org> (raw)
In-Reply-To: <3F49B515.6010107@torque.net>; from dougg@torque.net on Mon, Aug 25, 2003 at 05:04:53PM +1000
On Mon, Aug 25, 2003 at 05:04:53PM +1000, Douglas Gilbert wrote:
> A recent test of smartmontools on lk 2.6.0-test4 failed
> miserably on my main SCSI disk. It would seem that
> attempts to use either the:
> SCSI_IOCTL_SEND_COMMAND
> SG_IO
> ioctls on a mounted SCSI "block" device fail with EBUSY.
> These ioctls work fine on devices that don't have mounted
> file systems on then. If this is a new policy then it needs
> to be reconsidered. smartmontools still works ok on ATA disks
> in lk 2.6.0-test4.
That's because both mount (or e.g. volume managers) claims
devices for exclusive use, as does drivers/block/scsi_ioctl.c
> Both the ioctls in question still work via the corresponding
> scsi generic device.
Well, we either want both to work or not work. The current
situation is inconsistant.
> Will scsi generic devices make a
> re-appearance in sysfs (as indicated by Christoph when the
> relevant code in sg was removed)?
Yeah, I still need to come up with a way for class_interfaces
like sg to have sysfs entries. the TODO list is growing but
I'll take a look at this, promised.
next prev parent reply other threads:[~2003-08-25 12:08 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 [this message]
2003-08-26 10:20 ` Douglas Gilbert
2003-08-26 14:08 ` James Bottomley
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=20030825130822.A4258@infradead.org \
--to=hch@infradead.org \
--cc=ballen@gravity.phys.uwm.edu \
--cc=dougg@torque.net \
--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