Re: [PATCH 2/2] Find and format any unformatted DASD devices (#528386).

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

 



> >Would this kill all potential partitions on DASDs that were already both
> >low-level formatted as well as already having partitions?
> >That would mean whenever the user had one or more DASDs yet to be
> >low-level formatted, he would have to recreate all existing partitioning
> >on other DASDs which had been in use and thus prepared before.
> >How was this handled with RHEL5 in order not to introduce regressions?
> 
> Hmm, yeah that could be a problem.  I'm going to save the kickstart handling
> for another patch.  I want to talk to clumens and see what, if anything,
> exists in kickstart that we could define/use for unformatted DASDs.

Actually, what I meant to suggest was the zerombr command, which
reinitializes any invalid partition tables it finds.  We overload this
to do the same with LVM metadata.  I suggest we further overload it to
do the same for unformatted DASDs.

I can't overstate my opposition to adding any new options or commands to
the clearpart/zerombr disaster, as that can only make things even more
complicated and introduce even more corner cases we don't test for.

- Chris

_______________________________________________
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