From: Neil Brown <neilb@suse.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [mdadm git pull] imsm fixes and general external metadata updates
Date: Mon, 2 Feb 2009 10:46:21 +1100 [thread overview]
Message-ID: <18822.13389.938876.964972@notabene.brown> (raw)
In-Reply-To: message from Dan Williams on Wednesday January 21
On Wednesday January 21, dan.j.williams@intel.com wrote:
> Hi Neil,
>
> The following changes since commit 78fbcc10312649f2f4f88283e3f19dce9b205733:
> NeilBrown (1):
> Merge branch 'master' into scratch-3.0
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/djbw/mdadm.git devel
>
Thanks.
> Dan Williams (12):
> mdmon: fix missing ->subarray initialization
> imsm: fix dev_open return value handling
> imsm: imsm_read_serial check for zero-length response
> mdmon: expand permissible container device names
> mdmon: support scanning for containers
> Assemble: fix busy detection
> mdmon: make switchroot an undecorated option
> Create: allow per-metadata default layouts
> imsm: rename vprintf macro to pr_vrb
> imsm: enforce num_disks constraints
> imsm: enforce "all member disks must be members of all arrays"
> Create: warn when a metadata format's platform components are missing
This all looks fine, though I confess that I didn't read "all
member disks must be members of all arrays" very closely...
>
> Beyond the straightforward fixes the more interesting bits are:
>
> mdmon: support scanning for containers
> This is an attempt to make mdmon more manageable in the initramfs
> environment. Once mdadm has assembled the rootfs we need to switch the
> currently running mdmon instance(s) over to the new mount point. With
> the current code it is awkward to do this in a generic way because a
> script needs to know the names of all the active containers. This tree
> allows a script to do "mdmon /proc/mdstat /newroot" to batch convert all
> mdmon instances to /newroot. This is probably a good time to start
> interfacing with initramfs@vger.kernel.org to make sure these "initramfs
> helper" changes are relevant, and to see what else is missing.
We really need a man page for mdmon don't we. Then this sort of text
could be placed there for safely.
All pulled.
Thanks.
NeilBrown
next prev parent reply other threads:[~2009-02-01 23:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 22:20 [mdadm git pull] imsm fixes and general external metadata updates Dan Williams
2009-01-23 22:51 ` Dan Williams
2009-02-01 23:46 ` Neil Brown [this message]
2009-02-23 15:54 ` Doug Ledford
2009-02-23 18:58 ` Dan Williams
2009-02-23 19:53 ` Doug Ledford
2009-02-23 20:16 ` NeilBrown
2009-02-24 7:57 ` Luca Berra
2009-02-24 23:33 ` When read-only isn't read-only (was Re: [mdadm git pull] imsm fixes and general external metadata updates) John Robinson
2009-02-24 23:45 ` Greg Freemyer
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=18822.13389.938876.964972@notabene.brown \
--to=neilb@suse.de \
--cc=dan.j.williams@intel.com \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).