From: wysochanski@sourceware.org <wysochanski@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2/tools vgsplit.c
Date: 9 Jun 2009 14:31:21 -0000 [thread overview]
Message-ID: <20090609143121.7557.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: wysochanski at sourceware.org 2009-06-09 14:31:21
Modified files:
tools : vgsplit.c
Log message:
Update vgsplit to use new vg_reserve_newname() function.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/vgsplit.c.diff?cvsroot=lvm2&r1=1.74&r2=1.75
--- LVM2/tools/vgsplit.c 2009/05/21 03:04:54 1.74
+++ LVM2/tools/vgsplit.c 2009/06/09 14:31:20 1.75
@@ -285,6 +285,7 @@
int consistent;
int r = ECMD_FAILED;
const char *lv_name;
+ uint32_t rc;
if ((arg_count(cmd, name_ARG) + argc) < 3) {
log_error("Existing VG, new VG and either physical volumes "
@@ -321,15 +322,29 @@
return ECMD_FAILED;
log_verbose("Checking for new volume group \"%s\"", vg_name_to);
- if (!lock_vol(cmd, vg_name_to, LCK_VG_WRITE)) {
+ /*
+ * Try to lock the name of the new VG. If we cannot reserve it,
+ * then we assume it exists, and we will not be holding a lock.
+ * We then try to read it - the vgsplit will be into an existing VG.
+ *
+ * Otherwise, if the lock was successful, it must be the case that
+ * we obtained a WRITE lock and could not find the vgname in the
+ * system. Thus, the split will be into a new VG.
+ */
+ rc = vg_lock_newname(cmd, vg_name_to);
+ if (rc == FAILED_LOCKING) {
log_error("Can't get lock for %s", vg_name_to);
unlock_and_release_vg(cmd, vg_from, vg_name_from);
return ECMD_FAILED;
}
-
- consistent = 0;
- if ((vg_to = vg_read_internal(cmd, vg_name_to, NULL, &consistent))) {
+ if (rc == FAILED_EXIST) {
existing_vg = 1;
+ if (!(vg_to = vg_lock_and_read(cmd, vg_name_to, NULL,
+ LCK_VG_WRITE,
+ CLUSTERED | EXPORTED_VG |
+ RESIZEABLE_VG | LVM_WRITE,
+ CORRECT_INCONSISTENT | FAIL_INCONSISTENT)))
+ return ECMD_FAILED;
if (new_vg_option_specified(cmd)) {
log_error("Volume group \"%s\" exists, but new VG "
"option specified", vg_name_to);
@@ -337,7 +352,7 @@
}
if (!vgs_are_compatible(cmd, vg_from,vg_to))
goto_bad;
- } else {
+ } else if (rc == SUCCESS) {
existing_vg = 0;
/* Set metadata format of original VG */
next reply other threads:[~2009-06-09 14:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 14:31 wysochanski [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-02 21:27 LVM2/tools vgsplit.c wysochanski
2009-09-02 21:27 wysochanski
2009-09-02 21:26 wysochanski
2009-09-02 21:26 wysochanski
2009-09-02 21:26 wysochanski
2009-09-02 21:26 wysochanski
2009-09-02 21:25 wysochanski
2009-07-09 5:40 wysochanski
2009-07-08 14:27 wysochanski
2009-07-01 17:04 wysochanski
2009-06-10 11:21 mbroz
2008-04-15 14:57 agk
2008-04-10 21:34 wysochanski
2008-04-10 20:02 agk
2008-04-10 2:15 wysochanski
2008-04-10 1:30 wysochanski
2008-02-29 0:13 wysochanski
2008-01-22 3:49 wysochanski
2008-01-11 20:17 wysochanski
2007-11-15 2:53 agk
2007-07-23 21:10 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=20090609143121.7557.qmail@sourceware.org \
--to=wysochanski@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.