Bug 161227 - Specifying root filesystem in grub via UUID
Specifying root filesystem in grub via UUID
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: mkinitrd (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Peter Jones
David Lawrence
: Reopened
Depends On:
  Show dependency treegraph
Reported: 2005-06-21 11:34 EDT by Wendy Cheng
Modified: 2010-10-21 23:05 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 14:59:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Wendy Cheng 2005-06-21 11:34:24 EDT
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):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Jeremy Katz 2005-06-21 13:41:17 EDT
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.
Comment 10 Red Hat Bugzilla 2007-02-05 14:16:05 EST
REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred.
Comment 11 RHEL Product and Program Management 2007-10-19 14:59:42 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.