From: Dan Williams <dan.j.williams@intel.com>
To: neilb@suse.de
Cc: linux-raid@vger.kernel.org, ed.ciechanowski@intel.com,
marcin.labun@intel.com
Subject: [mdadm PATCH 00/13] rebuild / resync checkpointing and other external metadata fixes
Date: Tue, 22 Dec 2009 16:59:19 -0700 [thread overview]
Message-ID: <20091222235807.31628.23231.stgit@dwillia2-linux.ch.intel.com> (raw)
Hi Neil,
The latter half of this update consumes the new
md/dev-XXX/recovery_start attribute for checkpointing and resuming
resync/rebuild operations. It requires one more kernel patch [1] on top
of 2.6.33-rc1 to ensure that mdmon sees the recovery state. One caveat
is that we only get checkpoint events when the sync_action == idle, at
array shutdown or as a part of 'mdadm --wait-clean --scan'.
The other bits are a collection of fixes to address unrelated issues
discovered along the way. The result is pushed out to:
git://github.com:djbw/mdadm.git master
Please have a look.
Thanks,
Dan
[1]: http://marc.info/?l=linux-raid&m=126144478304488&w=2
---
Dan Williams (13):
imsm: catch attempt to auto-layout zero-length arrays
imsm: honor orom constraints for auto-layout
imsm: fix spare promotion
imsm: fix thunderdome segfault
util: fix devnum2devname for devnum == 0
imsm: cleanup print_imsm_dev()
mdmon: cleanup manage_member() leak
mdmon: cleanup resync_start
Add scaffolding for handling md/dev-XXX/recovery_start
Introduce MaxSector
Teach sysfs_add_disk() callers to use ->recovery_start versus 'insync' parameter
Support external metadata recovery-resume
imsm: add support for checkpointing via 'curr_migr_unit'
Create.c | 2
Manage.c | 1
bitmap.c | 2
managemon.c | 93 ++++++++----
mdadm.h | 27 +++-
mdmon.h | 7 -
monitor.c | 23 +--
super-ddf.c | 14 +-
super-intel.c | 432 +++++++++++++++++++++++++++++++++++++++++++++++----------
super1.c | 6 -
sysfs.c | 15 ++
util.c | 24 +++
12 files changed, 493 insertions(+), 153 deletions(-)
next reply other threads:[~2009-12-22 23:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 23:59 Dan Williams [this message]
2009-12-22 23:59 ` [PATCH 01/13] imsm: catch attempt to auto-layout zero-length arrays Dan Williams
2009-12-22 23:59 ` [PATCH 02/13] imsm: honor orom constraints for auto-layout Dan Williams
2009-12-22 23:59 ` [PATCH 03/13] imsm: fix spare promotion Dan Williams
2009-12-22 23:59 ` [PATCH 04/13] imsm: fix thunderdome segfault Dan Williams
2009-12-22 23:59 ` [PATCH 05/13] util: fix devnum2devname for devnum == 0 Dan Williams
2009-12-22 23:59 ` [PATCH 06/13] imsm: cleanup print_imsm_dev() Dan Williams
2009-12-22 23:59 ` [PATCH 07/13] mdmon: cleanup manage_member() leak Dan Williams
2009-12-23 0:00 ` [PATCH 08/13] mdmon: cleanup resync_start Dan Williams
2009-12-23 0:00 ` [PATCH 10/13] Introduce MaxSector Dan Williams
2009-12-23 0:00 ` [PATCH 11/13] Teach sysfs_add_disk() callers to use ->recovery_start versus 'insync' parameter Dan Williams
2009-12-23 0:00 ` [PATCH 12/13] Support external metadata recovery-resume Dan Williams
2009-12-23 0:00 ` [PATCH 13/13] imsm: add support for checkpointing via 'curr_migr_unit' Dan Williams
2009-12-23 0:13 ` [mdadm PATCH 00/13] rebuild / resync checkpointing and other external metadata fixes Dan Williams
2009-12-30 2:56 ` Neil Brown
2009-12-30 7:19 ` Luca Berra
2009-12-30 7:57 ` Neil Brown
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=20091222235807.31628.23231.stgit@dwillia2-linux.ch.intel.com \
--to=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=marcin.labun@intel.com \
--cc=neilb@suse.de \
/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).