Description of problem:
There are merits of specifying root filesystem in grub using UUID since disk
label doesn't fit the need. For example, in a real world case, when a panic
system got rebooted, it picked up the wrong lun (root partition) from the shared
SAN since someone just newly created a new root partition (lun) for another host
using the very same disk label. It took a while to figure out what went wrong
because the system was panicked before that reboot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
UUID has the downside of being completely incomprehensible to a user :)
LABEL is the best compromise between something that can be understood and
something that is relatively resilient to disks moving around.
REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred.
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.