From: Christian Motschke <christian@motschke.de>
To: lvm-devel@redhat.com
Subject: clustered snapshots
Date: Tue, 26 Apr 2011 11:18:06 +0200 [thread overview]
Message-ID: <618B4C17-4670-4CDF-9476-7B4EF7A8675E@motschke.de> (raw)
Hi,
I tried the unstable packages of lvm2 in debian with support for clustered snapshots (2.02.84) (I looked at the sources, the patch is included). It is unusable (at least for me ;-).
I have corosync and clvm with openais support running. Locking type is set to 3 in lvm.conf. I have only 1 server with clvm in this test setup. I hope this is not the problem.
What I did:
gcc:~# vgchange -cy vgtest
Volume group "vgtest" successfully changed
gcc:~# vgdisplay -C
VG #PV #LV #SN Attr VSize VFree
vgtest 1 1 0 wz--nc 4.00g 3.00g
gcc:~# lvdisplay -C
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
test-lv vgtest -wi-a- 1.00g
gcc:~#
gcc:~# lvchange -aey vgtest/test-lv
gcc:~# lvcreate -s -n test-lv-snap -L 100m vgtest/test-lv
Logical volume "test-lv-snap" created
gcc:~# lvdisplay -C
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
test-lv vgtest owi-a- 1.00g
test-lv-snap vgtest swi-a- 100.00m test-lv 100.00
So, after I created the snapshot it is immediately disabled and 100% full. What am I doing wrong?
With kind regards.
Christian Motschke
next reply other threads:[~2011-04-26 9:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 9:18 Christian Motschke [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-28 23:16 clustered snapshots Mikulas Patocka
2009-09-29 21:39 ` Mikulas Patocka
2009-09-30 16:17 ` Jonathan Brassow
2009-10-01 5:43 ` Mikulas Patocka
2009-10-02 17:26 ` Mike Snitzer
2009-10-02 17:55 ` Mikulas Patocka
2009-10-04 3:48 ` Mike Snitzer
2009-10-05 2:25 ` Mikulas Patocka
2009-10-05 4:33 ` Mike Snitzer
2009-10-05 13:38 ` Mike Snitzer
2009-10-05 15:57 ` Mikulas Patocka
2009-10-05 16:24 ` Mike Snitzer
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=618B4C17-4670-4CDF-9476-7B4EF7A8675E@motschke.de \
--to=christian@motschke.de \
--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.