Inconsistent Device Names Across Reboot Cause Mount Failure Or Incorrect Mount
(Doc ID 563711.1)
Last updated on AUGUST 04, 2018
Applies to:Linux OS - Version 1.2.0-1 to 1.2.8-2 [Release OCFS2]
Linux OS - Version Oracle Linux 4.6 to Oracle Linux 5.1 [Release OL4U6 to OL5U1]
Linux Kernel - Version: 1.2 to 1.2.8
*** 2018-01-11 Checked for currency ***
A disk partition does not mount after a system boot, whether the reboot was planned or unplanned. Before the reboot, the disk partition was mounted and working properly. The disk has mounted correctly after other system reboots, but no longer works.
This behavior can happen regardless of the type of file system on the partition and is unrelated to the file system type. Failures of disks with EXT3 or OCFS2 file systems have been reported, but can happen with any file system type.
A typical entry in the /etc/fstab file could be similar to:
/dev/mapper/mpath2 /otherdir ocfs2 _netdev 0 0
or various combinations of these.
Reboot of either the SAN or the client machine. Note that both planned and unplanned reboots are susceptible to this issue.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Mounting By Label|
|Mounting By UUID|
|Using UDEV Rulesets|