Re: [PATCH 1/3] Limit grub stage2 md members' device type and metadata version.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 09/01/2011 12:10 AM, Clyde E. Kunkel wrote:
On 08/25/2011 03:35 PM, David Lehman wrote:
MD array members can only be partitions and arrays must use
v1.0 or older metadata.
---
pyanaconda/bootloader.py | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/pyanaconda/bootloader.py b/pyanaconda/bootloader.py
index eae37a3..d62fb91 100644
--- a/pyanaconda/bootloader.py
+++ b/pyanaconda/bootloader.py
@@ -1011,6 +1011,8 @@ class GRUB(BootLoader):
# list of strings representing options for boot device types
stage2_device_types = ["partition", "mdarray"]
stage2_raid_levels = [mdraid.RAID1]
+ stage2_raid_member_types = ["partition"]
+ stage2_raid_metadata = ["0", "0.90", "1.0"]

packages = ["grub"]



What happens if you do not intend to have stage2 on an array with newer
metadata type? If such an array is present, will this fail a la bz 734978?

TIA


Partial answer to my own question-- I deleted the array that had metadata type 1.1 and the same error ('MDRaidArrayDevice' object has no attribute 'metadataVersion') occurred. mdadm --examine of the former members showed no raid superblocks.


--
Regards,
OldFart

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list


[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux