Bug 683426 - When creating MD RAID1 for a root fs and having no separate /boot, metadata 1.2 are used
Summary: When creating MD RAID1 for a root fs and having no separate /boot, metadata 1...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: David Lehman
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-09 12:00 UTC by Pavel Snajdr
Modified: 2011-03-16 19:26 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-16 19:26:45 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Pavel Snajdr 2011-03-09 12:00:14 UTC 
When creating MD RAID1 for a root fs and having no separate /boot, metadata 1.2 are used.
But when having a separate RAID1 for /boot, anaconda automatically does it with older metadata.

This is a particular problem for GRUB, because it can't boot from RAID1 with new metadata (v 0.9 metadata are the last that work I think).

I filed a bug for GRUB, but I don't think they'll fix it (683421), so please take the need for older metadata in account even when having only one RAID1 with rootfs and no dedicated boot partition.
Comment 2 Chris Lumens 2011-03-09 15:15:19 UTC 
anaconda really, really should not care about MD metadata version.
Comment 3 David Lehman 2011-03-09 16:47:55 UTC 
Please attach /tmp/storage.log and /tmp/anaconda.log from the install. Post-install, they will be /var/log/anaconda.storage.log and /var/log/anaconda.log. Thanks.
Comment 4 David Lehman 2011-03-09 21:12:20 UTC 
I tested this scenario with anaconda-13.21.100-1 and was unable to reproduce. My tests showed that anaconda correctly recognized the situation and created the array with version 1.0 metadata, which is what we are supposed to do. We use version 1.1 for all other new arrays.
Note You need to log in before you can comment on or make changes to this bug.