Solved Re: [CentOS] Problem after last update

[Nicholas Anderson]

Bob Marcan wrote:

> Nicholas Anderson wrote:
>
>> Hi all,
>>
>> i've just updated CentOS4.3 .
>> After updating it i rebooted the machine (cause there was some kernel
>> pkg's) and it seems that centos lost my LVM config ....
>> I tried manually a vgscan and:
>> (root at backupsrv) boot # vgscan
>>   connect() failed on local socket: Connection refused
>>   Locking type 2 initialisation failed.
>>
>> and my /dev/VG0/LogVol00 dissapeared :-(
>>
>>
>>
>> Any tips ?
>>
>
> I'm running cluster and got the same error.
> Go back to 2.6.9-34.
>
> Or remove lvm2-cluster ?
>
>

Hi,

i've just solved the problem :-P
up2date has changed my lvm.conf ....
I'm new to Centos, and i didnt know that it saves a copy of the replaced
file ....
im my case it was the lvm.conf.

The new file (called "bad" :-)  ) uses type 2 of locking_type ....

below is a short version (cutting the comments and line numbers) of a
diff between both files ....

(root at backupsrv) lvm # diff -ru lvm.conf  lvm.conf.bad

+    library_dir = "/usr/lib"
+    locking_library = "liblvm2clusterlock.so"

-    locking_type = 1
+    locking_type = 2


Thanks anyway,

Nick


-- 
Nicholas Anderson
Administrador de Sistemas Unix
LPIC-1 Certified
Rede Fiocruz
e-mail: nicholas at fiocruz.br