public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: agk@sourceware.org To: lvm2-cvs@sourceware.org Subject: LVM2 ./WHATS_NEW tools/vgreduce.c Date: Thu, 07 Sep 2006 23:23:00 -0000 [thread overview] Message-ID: <20060907232345.10894.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: agk@sourceware.org 2006-09-07 23:23:45 Modified files: . : WHATS_NEW tools : vgreduce.c Log message: fix vgreduce clustered check Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.435&r2=1.436 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/vgreduce.c.diff?cvsroot=lvm2&r1=1.52&r2=1.53 --- LVM2/WHATS_NEW 2006/09/02 01:18:16 1.435 +++ LVM2/WHATS_NEW 2006/09/07 23:23:45 1.436 @@ -1,5 +1,6 @@ Version 2.02.10 - ================================== + Don't attempt automatic recovery without proper locking. When using local file locking, skip clustered VGs. Add fallback_to_clustered_locking and fallback_to_local_locking parameters. lvm.static uses built-in cluster locking instead of external locking. --- LVM2/tools/vgreduce.c 2006/09/02 01:18:17 1.52 +++ LVM2/tools/vgreduce.c 2006/09/07 23:23:45 1.53 @@ -476,7 +476,7 @@ return ECMD_FAILED; } - if ((vg->status & CLUSTERED) && !locking_is_clustered() && + if (vg && (vg->status & CLUSTERED) && !locking_is_clustered() && !lockingfailed()) { log_error("Skipping clustered volume group %s", vg->name); unlock_vg(cmd, vg_name);
next reply other threads:[~2006-09-07 23:23 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-09-07 23:23 agk [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-03-30 14:59 zkabelac 2007-01-31 16:26 agk 2005-12-21 18:51 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=20060907232345.10894.qmail@sourceware.org \ --to=agk@sourceware.org \ --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).