From: Andreas Pflug <pgadmin@pse-consulting.de>
To: Vladislav Bogdanov <bubble@hoster-ok.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM snapshot with Clustered VG [SOLVED]
Date: Wed, 13 Mar 2013 16:14:16 +0100 [thread overview]
Message-ID: <514097C8.4030602@pse-consulting.de> (raw)
In-Reply-To: <5137447B.7030906@hoster-ok.com>
Hi Vladislav,
I finally succeeded making all working as expected!
What I did:
- compile corosync 2.3.0
(http://corosync.org/download/corosync-2.3.0.tar.gz)
- compile libqb 0.14.4
(https://fedorahosted.org/releases/q/u/quarterback/libqb-0.14.4.tar.gz)
- compile dlm_4.0.1
(http://git.fedorahosted.org/cgit/dlm.git/snapshot/dlm-4.0.1.tar.gz)
- Compiled LVM 2.2.98
(http://git.fedorahosted.org/cgit/lvm2.git/snapshot/lvm2-2_02_98.tar.gz)
with your PREVIOUS patch (
https://www.redhat.com/archives/linux-lvm/2013-January/msg00006.html )
I made a 2-node test cluster, both accessing a test iscsi target, all
daemons load fine.
Everything works as expected! Snapshotting is possible after -aey
--force explicit exclusive locking, lvresize works as well.
Previously, I tried your latest patch. I had a plethiora of errors,
starting with lvcreate failing:
#metadata/lv_manip.c:4137 Clearing start of logical volume "testvol2"
#device/dev-cache.c:599 /dev/san2/testvol2: stat failed: No such
file or directory
#metadata/lv_manip.c:4140 /dev/san2/testvol2: not found: device not
cleared
#metadata/lv_manip.c:4620 Aborting. Failed to wipe start of new LV.
I need to add -Z n to have it created. After that, most activations
failed, with error code 5. I went back to vanilla 2.2.98, all ok except
exclusive locking, applied the initial locking patch and voila! All done.
Thanks for your support!
Andreas
next prev parent reply other threads:[~2013-03-13 15:14 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 11:28 [linux-lvm] LVM snapshot with Clustered VG Andreas Pflug
2013-03-01 15:41 ` Vladislav Bogdanov
2013-03-06 7:40 ` Andreas Pflug
2013-03-06 7:58 ` Vladislav Bogdanov
2013-03-06 9:15 ` Andreas Pflug
2013-03-06 9:35 ` Vladislav Bogdanov
2013-03-06 9:59 ` Andreas Pflug
2013-03-06 11:20 ` Vladislav Bogdanov
2013-03-06 12:17 ` Andreas Pflug
2013-03-06 13:28 ` Vladislav Bogdanov
2013-03-12 6:52 ` Andreas Pflug
2013-03-13 15:14 ` Andreas Pflug [this message]
2013-03-13 16:53 ` [linux-lvm] LVM snapshot with Clustered VG [SOLVED] Vladislav Bogdanov
2013-03-13 17:37 ` Andreas Pflug
2013-03-13 18:30 ` Vladislav Bogdanov
2013-03-14 21:57 ` Andreas Pflug
2013-03-15 9:00 ` Zdenek Kabelac
2013-03-15 9:29 ` Vladislav Bogdanov
2013-03-15 9:37 ` Zdenek Kabelac
2013-03-15 12:53 ` Vladislav Bogdanov
2013-03-15 13:11 ` Vladislav Bogdanov
2013-03-15 13:32 ` Zdenek Kabelac
2013-03-15 14:51 ` Vladislav Bogdanov
2013-03-15 15:02 ` Zdenek Kabelac
2013-03-15 15:36 ` Vladislav Bogdanov
2013-03-15 15:55 ` Zdenek Kabelac
2013-03-15 17:16 ` Vladislav Bogdanov
-- strict thread matches above, loose matches on Subject: below --
2013-03-15 16:31 David Teigland
2013-03-15 17:46 ` Vladislav Bogdanov
2013-03-15 18:38 ` David Teigland
2013-03-16 11:00 ` Vladislav Bogdanov
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=514097C8.4030602@pse-consulting.de \
--to=pgadmin@pse-consulting.de \
--cc=bubble@hoster-ok.com \
--cc=linux-lvm@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 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 NNTP newsgroup(s).