Bug ID 4346123

Problem Summary: When booting a cluster node after multiple failures, a cluster file system might fail to mount automatically from its /etc/vfstab entry, and the boot process will place the node in an administrative shell. Running the fsck command on the device might yield the following error.

# fsck -y /dev/global/rdsk/d1s7
** /dev/global/rdsk/d1s7
Can't roll the log for /dev/global/rdsk/d1s7

Workaround: This problem might occur when the global device is associated with a stale cluster file system mount. Run the following command, and check if the file system shows up in an error state to confirm a stale mount.

# /usr/bin/df -k

If the global device is associated with a stale cluster file system mount, unmount the global device. Note that if any users of the file system exist on any of the cluster nodes, the unmount cannot succeed. Run the following command on each node to identify current users of the file system.

# /usr/sbin/fuser -c mountpoint

Also, run the share(1M) command to confirm that the file system is not NFS shared on any of the cluster nodes.