From: jbrassow@sourceware.org <jbrassow@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW tools/lvconvert.c
Date: 6 Jul 2010 17:02:04 -0000 [thread overview]
Message-ID: <20100706170204.5474.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: jbrassow at sourceware.org 2010-07-06 17:02:04
Modified files:
. : WHATS_NEW
tools : lvconvert.c
Log message:
Fix for bug 607347: failing both redundant mirror log legs...
Rather than attempting to remove all the images of a mirrored
log volume via remove_mirror_images, simply remove the log
if all its devices have failed.
Taka was the first to report that there is still an outstanding
issue with handling this case. I've managed to reproduce it
only very rarely, and am still working on identifying the problem.
Failing to handle the problem rarely is better than not handling
the scenario at all, so I'm checking this in.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1653&r2=1.1654
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/lvconvert.c.diff?cvsroot=lvm2&r1=1.136&r2=1.137
--- LVM2/WHATS_NEW 2010/07/06 16:49:38 1.1653
+++ LVM2/WHATS_NEW 2010/07/06 17:02:03 1.1654
@@ -1,5 +1,6 @@
Version 2.02.70 - 6th July 2010
===============================
+ Change logic to handle double failure of a "mirrored" mirror log.
Randomly select which mdas to use or ignore.
Add some missing standard configure.in checks.
Add printf format attributes to yes_no_prompt and fix a caller.
--- LVM2/tools/lvconvert.c 2010/07/01 10:10:52 1.136
+++ LVM2/tools/lvconvert.c 2010/07/06 17:02:03 1.137
@@ -705,9 +705,12 @@
return 1;
/* Reducing redundancy of the log */
- return remove_mirror_images(log_lv, log_count,
- is_mirror_image_removable,
- operable_pvs, 0U);
+ if (log_count)
+ return remove_mirror_images(log_lv, log_count,
+ is_mirror_image_removable,
+ operable_pvs, 0U);
+
+ return remove_mirror_log(lv->vg->cmd, lv, operable_pvs);
}
static int _lv_update_log_type(struct cmd_context *cmd,
next reply other threads:[~2010-07-06 17:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 17:02 jbrassow [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-30 8:58 LVM2 ./WHATS_NEW tools/lvconvert.c prajnoha
2012-02-22 17:18 jbrassow
2011-06-01 12:24 prajnoha
2011-01-05 23:18 jbrassow
2011-01-05 20:02 jbrassow
2010-07-30 17:50 taka
2010-04-26 18:31 agk
2010-02-05 21:49 jbrassow
2009-10-23 1:24 agk
2009-06-26 9:04 agk
2009-06-15 13:43 mbroz
2009-06-15 12:08 mbroz
2008-06-26 21:38 agk
2008-04-18 12:50 agk
2008-02-12 13:29 agk
2008-02-12 13:26 agk
2008-01-14 21:11 agk
2007-08-22 20:03 agk
2007-08-22 19:32 agk
2007-08-10 13:33 wysochanski
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=20100706170204.5474.qmail@sourceware.org \
--to=jbrassow@sourceware.org \
--cc=lvm-devel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.