I complained about this 'hotplug' many month ago. We can't and we should not
going to partition SAN devices (because it is 100% waste of time, space,
disk aligments and complicated management) and so I just added module to
mount _netdev devices into the SLES10 instead of playing with dumb and
broken 'hotplug'.
To compare - in RHEL you are expected to assign the whole disk to LVM by
running pvgropup commands. In SLES, you are exp[ected to create a partition
and then assign it. It cause many problems and adds complexity.
----- Original Message -----
From: "Randy Ramsdell" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, August 24, 2007 10:34 AM
Subject: Re: [Ocfs2-users] OCFS2 mount problem at Linux reboot when
devicenames are non persistent.
Sunil Mushran wrote:
While mount-by-uuid will work, mount-by-label should also work.
The one gotcha in the latter is that it expects the device to be
partitioned. As in, it will not mount-by-label if the device is /dev/sda
but will if the device is /dev/sda1 or sda2, etc.
Agreed, but UUID is completely unique whereas label is not. To avoid
ever mounting the incorrect volume we use UUID. Also note that Suse will
not "mount on boot" any device not partitioned because Suse uses
"hotplug", which doesn't understand unpartitioned devices. Redhat uses
_netdev_, which will mount unpartitioned devices on boot.
Randy Ramsdell wrote:
Ricardo Fernandez wrote:
Hi,
I have the following problem when the servers accessing OCFS2
reboot: as the Linux device names are non persistent, at reboot they
usually change, and then OCFS2 can't mount the device because it is
expecting a different device name as stated in the fstab file. (it
is specified in the format /dev/sdx as the instructions of the OCFS2
installation manual say) If I change the device name to the "new"
name, it works fine. But this is not an acceptable solution, as each
node should be able to start in a fully automatic way. (without
human intervention)
I thought that the purpose of the disk LABEL that I added when
formatting the partition with OCFS2 was exactly this. (Am I right?)
I changed the fstab to use the LABEL option, and also try to mount
it from the command line using the LABEL option but it didn't work.
Is there any bug or known issue on this topic. I guess that if I
glue the device name with udev it will work, but I really would
expect OCF2 to solve this problem (because it is not a new one, and
most of the file systems I know can handle it)
I would appreciate any help on this topic.
Thanks a lot
Ricardo
I work with:
RHEL 4
Local SCSI devices
External devices locates in an EVA8000 SAN, accessed through a fibre
channel bus. The OCFS2 file system is on one of these.
_______________________________________________
Ocfs2-users mailing list
[email protected]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
Do not use label use UUID name and _netdev_ fstab option.
This is the UUID of a volume we have.
/dev/disk/by-uuid/be12775a-ec1c-4ed7-a06b-f30a081a0603
UUID's are unique and never change so they are ideal for what you are
describing.
Randy Ramsdell
_______________________________________________
Ocfs2-users mailing list
[email protected]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
_______________________________________________
Ocfs2-users mailing list
[email protected]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
_______________________________________________
Ocfs2-users mailing list
[email protected]
http://oss.oracle.com/mailman/listinfo/ocfs2-users
