Re: [PATCH 5/5] booty changes for iswmd

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

 





On 06/11/2009 06:54 PM, Dan Williams wrote:

<snip>


We also need to consider the case where the user has disabled raid
support in the bios, but the metadata and the 'iswmd' command line
parameter still exist. I would expect that the OS ignores raid arrays in
that case. Currently the bios-raid-enabled state can be determined by
"mdadm --detail-platform -e imsm" returning 'true'.


Hmm,

Currently with dmraid we're not handling this, and I'm not sure we should,
what if the user does:
* reset bios to defaults
* boot
* remember oh, darn I needed to durn on raid in the bios
* reboot

Now we have a fscked up raidset, because if for example it was a mirror,
we will have used the partitions from the first disk (most likely) without
updating the second, and without marking things dirty in the metadata.

To me, if someone wants disks to stop being seen as raid, they should first
mark them as not part of a raidset in the orom, and then after that if
they have no other raidsets they can disable the orom.

Regards,

Hans

_______________________________________________
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