Re: lock_nolock to lock_dlm trouble

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

 



> I had to remove a storage system from my cluster. It was formatted using
> lock_dlm before being removed. An then, it was plugged on a single
> server, using the "lockproto=lock_nolock" option.
>
> Now, I put it back in the cluster, but I can 't mount it with the
> standard lock_dlm (but it's ok with the lock_nolock option, but it of
> course prevents me to share it).  The error is
>
> GFS: Trying to join cluster "lock_dlm", "alpha_cluster:vol001"
> lock_dlm: new lockspace error -17
> GFS: can't mount proto = lock_dlm, table = alpha_cluster:vol001, hostdata =

-17 is EEXIST, meaning a dlm lockspace with the name "vol001" already
exists.  "cman_tool services" should display it.  Do you have another fs
with the same name?  You may need to reboot the system to get it back in
shape.

Dave

PS. please send text instead of html mail

--
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