Robert S Peterson wrote: > On Thu, 2006-06-08 at 16:17 -0400, Vernard C. Martin wrote: >> The first node came up fine but the 2nd node is giving me a strange >> error when trying to start up "clvmd". The error is:[root@node001 ~]# clvmd >> clvmd could not connect to cluster manager >> Consult syslog for more information >> [root@node001 ~]# >> >> the syslog has: >> Jun 8 16:04:16 node001 clvmd: Unable to create lockspace for CLVM: No >> such file or directory > > Hi Vernard, > > I'm not very knowledgeable in the ways of lvm, however, you may want to > check to make sure that lock_dlm.ko is loaded (by using lsmod). > I don't know the code, but I'm guessing it's trying to create a lock > space by opening one of the dlm kernel devices (/dev/dlm*) which should > be controlled by the lock_dlm device driver. If that's not loaded, it > will fail. Bob's right, it sounds like the DLM isn't loaded. The module name is just "dlm" BTW and the device should show up in /proc/misc and (if udev is running) /dev/misc/dlm-control. lock_dlm is the GFS interface to the DLM...yes, I know it's confusing. -- patrick -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
