public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: jbrassow@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 ./WHATS_NEW lib/metadata/raid_manip.c Date: Tue, 24 Apr 2012 20:05:00 -0000 [thread overview] Message-ID: <20120424200532.15146.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: jbrassow@sourceware.org 2012-04-24 20:05:31 Modified files: . : WHATS_NEW lib/metadata : raid_manip.c Log message: Allow a subset of failed devices to be replaced in RAID LVs. If two devices in an array failed, it was previously impossible to replace just one of them. This patch allows for the replacement of some, but perhaps not all, failed devices. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2390&r2=1.2391 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/metadata/raid_manip.c.diff?cvsroot=lvm2&r1=1.28&r2=1.29 --- LVM2/WHATS_NEW 2012/04/24 20:00:03 1.2390 +++ LVM2/WHATS_NEW 2012/04/24 20:05:31 1.2391 @@ -1,5 +1,6 @@ Version 2.02.96 - ================================ + Allow subset of failed devices to be replaced in RAID LVs. Prevent resume from creating error devices that already exist from suspend. Improve clmvd singlenode locking for better testing. Update and correct lvs man page with supported column names. --- LVM2/lib/metadata/raid_manip.c 2012/04/12 03:16:37 1.28 +++ LVM2/lib/metadata/raid_manip.c 2012/04/24 20:05:31 1.29 @@ -1632,10 +1632,28 @@ * * - We need to change the LV names when we insert them. */ +try_again: if (!_alloc_image_components(lv, allocate_pvs, match_count, &new_meta_lvs, &new_data_lvs)) { log_error("Failed to allocate replacement images for %s/%s", lv->vg->name, lv->name); + + /* + * If this is a repair, then try to + * do better than all-or-nothing + */ + if (match_count > 1) { + log_error("Attempting replacement of %u devices" + " instead of %u", match_count - 1, match_count); + match_count--; + + /* + * Since we are replacing some but not all of the bad + * devices, we must set partial_activation + */ + lv->vg->cmd->partial_activation = 1; + goto try_again; + } return 0; }
next reply other threads:[~2012-04-24 20:05 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-24 20:05 jbrassow [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-04-12 3:16 jbrassow 2012-04-11 14:20 jbrassow 2012-04-11 1:23 jbrassow 2012-02-13 11:10 zkabelac 2011-12-01 0:21 jbrassow 2011-09-13 16:33 jbrassow 2011-08-18 19:31 jbrassow
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=20120424200532.15146.qmail@sourceware.org \ --to=jbrassow@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).