isplist@xxxxxxxxxxxx wrote: > 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? > The locking is only really needed when you change LV metadata (lvcreate, lvextend etc). so if all you are doing is activating existing LVs then the missing locking will make little difference. If you make any changes to LVs on a mode with the locking_type set incorrectly then those changes will not be visible on the other nodes. However, lvm2 is smart enough not to let you change clustered VGs when clvmd isn't available so it's unlikely to have caused any harm. you would have noticed something was wrong the first time you needed to change anything/ -- Patrick Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 ITE, UK. Registered in England and Wales under Company Registration No. 3798903 -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
