public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: agk@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 ./WHATS_NEW lib/metadata/mirror.c Date: Thu, 18 Sep 2008 19:09:00 -0000 [thread overview] Message-ID: <20080918190947.32654.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: agk@sourceware.org 2008-09-18 19:09:47 Modified files: . : WHATS_NEW lib/metadata : mirror.c Log message: Add missing LV error target activation in _remove_mirror_images. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.953&r2=1.954 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/metadata/mirror.c.diff?cvsroot=lvm2&r1=1.73&r2=1.74 --- LVM2/WHATS_NEW 2008/09/18 18:51:58 1.953 +++ LVM2/WHATS_NEW 2008/09/18 19:09:47 1.954 @@ -1,5 +1,6 @@ Version 2.02.40 - ================================ + Add missing LV error target activation in _remove_mirror_images. Prevent resizing an LV while lvconvert is using it. Avoid repeatedly wiping cache while VG_GLOBAL is held in vgscan & pvscan. Fix pvresize to not allow resize if PV has two metadata areas. --- LVM2/lib/metadata/mirror.c 2008/06/26 23:05:11 1.73 +++ LVM2/lib/metadata/mirror.c 2008/09/18 19:09:47 1.74 @@ -552,6 +552,17 @@ log_very_verbose("Updating \"%s\" in kernel", mirrored_seg->lv->name); + /* + * Avoid having same mirror target loaded twice simultaneouly by first + * activating the removed LV which now contains an error segment. + * As it's now detached from mirrored_seg->lv we must activate it + * explicitly. + */ + if (lv1 && !activate_lv(lv1->vg->cmd, lv1)) { + log_error("Problem reactivating removed %s", lv1->name); + return 0; + } + if (!resume_lv(mirrored_seg->lv->vg->cmd, mirrored_seg->lv)) { log_error("Problem reactivating %s", mirrored_seg->lv->name); return 0;
next reply other threads:[~2008-09-18 19:09 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-09-18 19:09 agk [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-03-23 16:28 mbroz 2012-02-01 13:50 zkabelac 2011-10-25 13:17 jbrassow 2011-10-06 14:49 jbrassow 2011-09-14 2:45 jbrassow 2011-09-13 21:13 jbrassow 2011-09-13 14:37 jbrassow 2011-09-13 13:59 jbrassow 2011-09-01 19:22 jbrassow 2011-06-17 14:27 zkabelac 2010-08-16 18:02 jbrassow 2010-07-13 22:24 jbrassow 2010-07-13 21:48 jbrassow 2010-07-09 15:08 jbrassow 2010-06-28 14:19 jbrassow 2010-06-21 16:12 jbrassow 2010-04-27 15:27 jbrassow 2010-04-27 14:57 jbrassow 2009-12-09 19:53 mbroz 2009-12-09 18:09 mbroz 2009-04-10 9:53 mbroz 2008-10-17 10:50 agk 2008-06-13 12:15 meyering 2008-02-22 13:28 agk 2007-11-22 13:57 agk 2006-11-30 17:52 agk 2006-11-10 19:35 agk 2006-07-20 20:37 agk
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=20080918190947.32654.qmail@sourceware.org \ --to=agk@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).