Pierre-Alain RIVIERE wrote:
Errol Neal wrote:
Quoting Pierre-Alain RIVIERE <[EMAIL PROTECTED]>:
In fact I'm using already this naming schema for udev. And when I
talked about CLVM it wasn't for its consistent naming features. I
remembered myself to have read something (Xen-users may be but I don't
have a link right now) about the use of CLVM to propagate LVM
modification. To be sure about this, I've just proceed some tests
(VMWare is my friend) just before writing this. 3 boxes : 1 openfiler,
2 debian and 1 iSCSI volume from openfiler connected to the 2 debian
boxes.
Then I've initialized LVM : pvcreate, vgcreate, lvcreate. All works
fine and on the 2 boxes pvdisplay, vgdisplay and lvdisplay outputs are
synchronised. But on the kernel side, the modifications are not
propagated.
On the box where I use LVM, the device is present:
/dev/xendomains/testlv. But on the other box (where I didn't neither
pvcreate etc), even if I can display LVM metadata using LVM tools
(lvdisplay, etc), the kernel do not create the device. And that's
where CLVM seems usefull. But CLVM documentation seems to be poor and I
don't really know about its debian support. May be there's an easier
way to propagate LVM changes?
Did you try pvscan/vgscan then vgchange -ay?
Ok you got it ;) With this my device appears on my other box.
But then another problem when extending the volume size. Size changed
on the box where the extension is done, but not changes on the other
box (but lvm related commands)
Hi again,
I've proceed some other tests since this post and I can confirm that
CLVM is mandatory to propagate automatically LVM changes to all nodes.
But CLVM requires CMAN which requires CCS.... you have to install the
whole redhat cluster suite. And the documentation is poor and debian
support erratic...
And by the way thanks for the tips about backup.
_______________________________________________
Openfiler-users mailing list
[email protected]
https://lists.openfiler.com/mailman/listinfo/openfiler-users
