lvm locking type 2, still used? PART 2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Actually, in addition to this message, I've also now found that some nodes can 
still see the logical volumes and are running just fine while others can now 
only see the volume groups and not the lv's? What's going on?

Mike

----------------

I am adding nodes and just noticed something interesting. When I started with
GFS/Clustering, one of the requirements which I made a note of was having to 
modify the /etc/lvm/lvm.conf in the following manner for my RHEL4 machines;

locking_type = 2
and
locking_library = "/usr/lib/liblvm2clusterlock.so"

I just noticed that over time, this file was changed back to what it used to 
be by default which is;

locking_type = 1 
and 
locking_library path has been removed. 

This is not something I've done, it's happened over time, using yum to keep 
things up to date. Yet, the cluster works just fine and all volumes can be 
seen. Did I miss something about not needing to do this anymore?

Mike




--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux