From: Michael Tokarev <mjt@tls.msk.ru>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Hannes Reinecke <hare@suse.de>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Un-remove aacraid devices
Date: Wed, 23 May 2007 21:08:05 +0400 [thread overview]
Message-ID: <465474F5.9080504@msgid.tls.msk.ru> (raw)
In-Reply-To: <AE4F746F2AECFC4DA4AADD66A1DFEF019E1B5C@otce2k301.adaptec.com>
Salyzyn, Mark wrote:
> NAK
>
> This will break all our management applications, and will not allow us to manipulate the array configurations from within Linux. This will also break online expansion of capacity.
>
> This flag has been set from the beginning to allow partition tables, capacity and device locking to be changed without requiring an intervening reboot or needing the device to be taken offline. Fixed disk result in these pieces of information being cached.
I think I've seen this very discussion before.
It looks like kernel needs to distinguish things like removable
media (truely removable - CDRoms etc) and some "dynamic" things
like in this case (like with any raid array really), with iSCSI
devices and so on.
Currently, 'removable' is handy at detecting devices which should
be handed to 'cdrom' or 'floppy' group (i think it was the cause
of previous incarnation of this discussion).
Right now, both ways are causing problems here or there. "Removable"
is bad because it confuses "regular" linux tools, while !removable
breaks configurability of arrays.
/mjt
prev parent reply other threads:[~2007-05-23 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 12:50 [PATCH] Un-remove aacraid devices Hannes Reinecke
2007-05-23 16:35 ` Salyzyn, Mark
2007-05-23 17:07 ` James Bottomley
2007-05-23 17:17 ` Salyzyn, Mark
2007-05-23 17:56 ` Salyzyn, Mark
2007-05-23 17:08 ` Michael Tokarev [this message]
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=465474F5.9080504@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=hare@suse.de \
--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).