On 04/10/2011 13:53, Christine Caulfield wrote:
That's quite correct, clvmd does not do device locking. When you activate a volume it will take out a (shared) lock on the device. What you do with the device after that is up to you. It doesn't have to be a filesyste, it could be a raw volume used for perhaps a database.
right, let's clarify myself: clvmd is not in sync between nodes, i see the device open in one node and not open in another node.
logs attached. thanks, d. pvsrv01 xen # lvdisplay /dev/vgAOE20/backup-root --- Logical volume --- LV Name /dev/vgAOE20/backup-root VG Name vgAOE20 LV UUID 4XUeC3-Pa3u-W2tT-ghjc-41hR-SHQG-7Jj4NI LV Write Access read/write LV Status available # open 1 LV Size 5.00 GiB Current LE 1280 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 4096 Block device 252:5 pvsrv01 xen # pvsrv04 ~ # lvdisplay /dev/vgAOE20/backup-root --- Logical volume --- LV Name /dev/vgAOE20/backup-root VG Name vgAOE20 LV UUID 4XUeC3-Pa3u-W2tT-ghjc-41hR-SHQG-7Jj4NI LV Write Access read/write LV Status available # open 0 LV Size 5.00 GiB Current LE 1280 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 4096 Block device 252:62 pvsrv04 ~ # _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
