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: Wed, 11 Apr 2012 01:23:00 -0000 [thread overview] Message-ID: <20120411012330.22012.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: jbrassow@sourceware.org 2012-04-11 01:23:29 Modified files: . : WHATS_NEW lib/metadata : raid_manip.c Log message: RAID LVs could not handle a down-convert if a device other than the last one in the array was specified for removal. This change addresses that (bz806111). Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2376&r2=1.2377 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/metadata/raid_manip.c.diff?cvsroot=lvm2&r1=1.25&r2=1.26 --- LVM2/WHATS_NEW 2012/04/10 23:34:41 1.2376 +++ LVM2/WHATS_NEW 2012/04/11 01:23:29 1.2377 @@ -1,5 +1,6 @@ Version 2.02.96 - ================================ + Fix problems when specifying PVs during RAID down-converts. Fix ability to handle failures in mirrored log (regression intro 2.02.89). Fix unlocking volume group in vgreduce in error path. Exit immediately if LISTEN_PID env var incorrect during systemd handover. --- LVM2/lib/metadata/raid_manip.c 2012/03/15 20:00:54 1.25 +++ LVM2/lib/metadata/raid_manip.c 2012/04/11 01:23:29 1.26 @@ -975,6 +975,8 @@ static int _raid_remove_images(struct logical_volume *lv, uint32_t new_count, struct dm_list *pvs) { + uint32_t s; + struct lv_segment *seg; struct dm_list removal_list; struct lv_list *lvl; @@ -1024,9 +1026,21 @@ } /* - * Resume original LV - * This also resumes all other sub-LVs + * Resume the remaining LVs + * We must start by resuming the sub-LVs first (which would + * otherwise be handled automatically) because the shifting + * of positions could otherwise cause name collisions. For + * example, if position 0 of a 3-way array is removed, position + * 1 and 2 must be shifted and renamed 0 and 1. If position 2 + * tries to rename first, it will collide with the existing + * position 1. */ + seg = first_seg(lv); + for (s = 0; (new_count > 1) && (s < seg->area_count); s++) { + if (!resume_lv(lv->vg->cmd, seg_lv(seg, s)) || + !resume_lv(lv->vg->cmd, seg_metalv(seg, s))) + return_0; + } if (!resume_lv(lv->vg->cmd, lv)) { log_error("Failed to resume %s/%s after committing changes", lv->vg->name, lv->name);
next reply other threads:[~2012-04-11 1:23 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-11 1:23 jbrassow [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-04-24 20:05 jbrassow 2012-04-12 3:16 jbrassow 2012-04-11 14:20 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=20120411012330.22012.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).