From: Doug Ledford <dledford@redhat.com>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Bryan Henderson <hbryan@us.ibm.com>,
Scott Merritt <Scsi@PragmaSoft.com>,
linux-scsi@vger.kernel.org
Subject: Re: Inhibit auto-attach of scsi disks ?
Date: Wed, 2 Oct 2002 17:44:40 -0400 [thread overview]
Message-ID: <20021002214440.GA30503@redhat.com> (raw)
In-Reply-To: <20021002233045.A12192@bitwizard.nl>
On Wed, Oct 02, 2002 at 11:30:45PM +0200, Rogier Wolff wrote:
> On Wed, Oct 02, 2002 at 08:51:39PM +0100, Alan Cox wrote:
> > On Wed, 2002-10-02 at 19:10, Bryan Henderson wrote:
> > > But when we speak of inhibiting partition table reading, I think that's
> > > another (missing) feature: I should be able to control whether Linux
> > > considers there to be partitions on my disk or not (and change the fact
> >
> > Why do you want to. Linux always offers you the entire disk anyway.
>
> Andries has argued this before, but I encountered a real-life example
> today.
>
> Today I was asked to recover data from a device where reading one
> of the "bad" blocks would cause an immediate "lockup" of the device:
> It would report ALL future blocks as bad as well. Only a power-cycle
> could revert it to reporting other blocks as "working".
>
> In this case, the partition table luckily didn't reference any of the
> bad blocks. But if it did, it would have made the recoverable 99% of
> the device unaccessable.
There's also the additional case of certain drives which may be reserved
by another initiator in a multi-initiator state which will then return an
I/O error for attempts to read the partition table (this can also happen
when certain drives, such as EMC type stuff (I'm not actually implying
EMC, because I can't remember the brand I saw this on), where the INQUIRY
data doesn't indicate that the device is actually offline, but it really
is, so attempts to read from it generate errors). It's not real urgent
stuff, but there are a few reasons to not read the partition table nor the
geometry or capacity of the device until you actually want to use it (for
example catch the first attempt to open any partition on a device and if
we haven't read the partition table yet then do so and then determine if
the open succeeds, something like that).
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
next prev parent reply other threads:[~2002-10-02 21:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 18:10 Inhibit auto-attach of scsi disks ? Bryan Henderson
2002-10-02 19:51 ` Alan Cox
2002-10-02 21:30 ` Rogier Wolff
2002-10-02 21:44 ` Doug Ledford [this message]
2002-10-02 21:56 ` Rogier Wolff
2002-10-02 20:52 ` Scott Merritt
2002-10-02 21:53 ` Rogier Wolff
-- strict thread matches above, loose matches on Subject: below --
2002-10-03 17:09 Bryan Henderson
2002-10-03 16:52 Bryan Henderson
2002-10-01 15:01 [PATCH] first cut at fixing unable to requeue with no outstanding commands Patrick Mansfield
2002-10-01 15:14 ` James Bottomley
2002-10-01 20:18 ` Inhibit auto-attach of scsi disks ? Scott Merritt
2002-10-02 0:46 ` Alan Cox
2002-10-02 1:49 ` Scott Merritt
2002-10-02 1:58 ` Doug Ledford
2002-10-02 2:45 ` Scott Merritt
2002-10-02 13:40 ` Alan Cox
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=20021002214440.GA30503@redhat.com \
--to=dledford@redhat.com \
--cc=R.E.Wolff@BitWizard.nl \
--cc=Scsi@PragmaSoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hbryan@us.ibm.com \
--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 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.