Out of Sync: Maddy's Blog

One of the problems one could probably encounter  when adding a new node to a cluster is the failure of global devices to mount and you get a scary error message like this one:

...

...

Configuring DID devices

obtaining access to all attached disks



plift1 console login: _cladm: CL_GBLMNT_ENABLE: No such file or directory



WARNING - Unable to globally mount all filesystems.

Check logs for error messages and correct the problems.

After the problems are corrected, please clear the

maintenance flag on globaldevices by running the

following command:

/usr/sbin/svcadm clear svc:/system/cluster/globaldevices:default

While this appears very scary and one could think that there is a misconfiguration, it actually is a very simple problem.  The clue is verifying every single error message.  In this case, "_cladm: CL_GBLMNT_ENABLE: No such file or directory".

This problem occurs if there are global mounts in the cluster and the new node joining the cluster doesn't have the mount point present.  While HAStoragePlus creates a mount point if it is not already present when onlining a RG, in this case, the problem is mount of the file system at boot time. 

 Solution:

The solution is to create the mountpoint and clear the globaldevices service manifest! 

#mkdir  <global mountpoint> 

#/usr/sbin/svcadm clear svc:/system/cluster/globaldevices:default

Astalavista Baby!