From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
Cc: NeilBrown <neilb@suse.com>, Mikael Abrahamsson <swmike@swm.pp.se>,
linux-raid@vger.kernel.org
Subject: Re: Linux Plumbers MD BOF discussion notes
Date: Wed, 4 Oct 2017 19:30:59 +0200 [thread overview]
Message-ID: <20171004173059.GB3181@lazy.lzy> (raw)
In-Reply-To: <076977d4-dfae-e8d3-7606-29e838f422ec@intel.com>
On Wed, Oct 04, 2017 at 01:23:02PM +0200, Artur Paszkiewicz wrote:
> On 10/04/2017 01:02 PM, Artur Paszkiewicz wrote:
> > Applications like mdadm can use this to hide/unhide their component
> > devices.
>
> And here is an example patch for mdadm. It adds options to manually hide
> or unhide the component devices:
>
> mdadm --hide-components /dev/md0
> mdadm --unhide-components /dev/md0
This seems to me already quite sensible.
>
> And an option for mdadm.conf that automatically hides the array's member
> disks when assembling and when new disks are added:
>
> ARRAY /dev/md/0 metadata=1.2 UUID=c2c4f8c6:cd775924:9cb2cc62:88fa45bd
> name=linux-ns31:0 hide-components=yes
>
> Hidden disks (by mdadm --hide-components or by config) should unhide
> when the array is stopped or disks are removed. It only works for whole
> devices, not partitions.
Well, this, on the other hands, it makes
it not really useful.
Furthermore, how about "cat /proc/mdstat"?
Will this show what? In case of hidden components.
Thanks,
bye,
--
piergiorgio
next prev parent reply other threads:[~2017-10-04 17:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 14:27 Linux Plumbers MD BOF discussion notes Shaohua Li
2017-09-15 20:42 ` Coly Li
2017-09-15 21:20 ` Shaohua Li
2017-09-16 0:08 ` NeilBrown
2017-09-18 4:54 ` Shaohua Li
2017-09-18 7:04 ` Mikael Abrahamsson
2017-09-18 8:56 ` NeilBrown
2017-10-01 5:32 ` Mikael Abrahamsson
2017-10-04 0:49 ` NeilBrown
2017-10-04 11:02 ` Artur Paszkiewicz
2017-10-04 11:23 ` Artur Paszkiewicz
2017-10-04 17:30 ` Piergiorgio Sartor [this message]
2017-10-04 18:03 ` John Stoffel
2017-10-04 21:18 ` Phil Turmel
2017-10-04 21:41 ` NeilBrown
2017-10-05 18:52 ` Artur Paszkiewicz
2017-10-05 23:39 ` NeilBrown
2017-10-06 7:13 ` Christoph Hellwig
2017-10-06 7:59 ` Mikael Abrahamsson
2017-10-04 17:28 ` Piergiorgio Sartor
2017-10-04 18:13 ` Anthony Youngman
2017-09-18 13:57 ` Wols Lists
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=20171004173059.GB3181@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--cc=artur.paszkiewicz@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=swmike@swm.pp.se \
/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).