From: Dan Williams <dan.j.williams@intel.com>
To: Neil Brown <neilb@suse.de>
Cc: Doug Ledford <dledford@redhat.com>,
"Labun, Marcin" <Marcin.Labun@intel.com>,
Linux RAID Mailing List <linux-raid@vger.kernel.org>,
"Ciechanowski, Ed" <ed.ciechanowski@intel.com>,
"Hawrylewicz Czarnowski,
Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@intel.com>
Subject: Re: More Hot Unplug/Plug work
Date: Wed, 28 Apr 2010 18:19:45 -0700 [thread overview]
Message-ID: <4BD8DEB1.40801@intel.com> (raw)
In-Reply-To: <20100429110153.7148bb9b@notabene.brown>
Neil Brown wrote:
> I'm not sure how this fits with imposing platform constraints.
> As platform constraints are closely tied to metadata types, it might be OK
> to have a metadata-specific tags (imsm=???) and leave to details to the
> metadata handler???
>
> Dan: help me understand these platform constraints: what is the most complex
> constraint that you can think of that you might want to impose?
At this point we really only need one constraint: prevent controller
spanning. If for example I take an existing imsm member off of ahci and
reattach it via a usb-to-sata enclosure mdadm needs a policy to prevent
associating that drive with anything on ahci.
In a pinch this policy can be disabled, but you wouldn't want to rebuild
across usb or any other controller because the option-rom only talks
ahci and will mark the drive missing.
So something like DOMAIN spanning=imsm, to tell mdadm to follow imsm
rules for this domain. Where 'spanning' is policy tag??
--
Dan
next prev parent reply other threads:[~2010-04-29 1:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 16:45 More Hot Unplug/Plug work Doug Ledford
2010-04-27 19:41 ` Christian Gatzemeier
2010-04-28 16:08 ` Labun, Marcin
2010-04-28 17:47 ` Doug Ledford
2010-04-28 18:34 ` Labun, Marcin
2010-04-28 21:05 ` Doug Ledford
2010-04-28 21:13 ` Dan Williams
2010-04-30 13:38 ` Doug Ledford
2010-04-29 1:01 ` Neil Brown
2010-04-29 1:19 ` Dan Williams [this message]
2010-04-29 2:37 ` Neil Brown
2010-04-29 18:22 ` Labun, Marcin
2010-04-29 21:55 ` Dan Williams
2010-05-03 5:58 ` Neil Brown
2010-05-08 1:06 ` Dan Williams
2010-04-30 16:13 ` Doug Ledford
2010-04-30 11:14 ` John Robinson
2010-04-30 15:52 ` Doug Ledford
2010-04-28 20:59 ` Luca Berra
2010-04-28 21:16 ` Doug Ledford
2010-04-29 20:32 ` Dan Williams
2010-04-29 21:22 ` Dan Williams
2010-04-30 16:26 ` Doug Ledford
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=4BD8DEB1.40801@intel.com \
--to=dan.j.williams@intel.com \
--cc=Marcin.Labun@intel.com \
--cc=dledford@redhat.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=przemyslaw.hawrylewicz.czarnowski@intel.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.