I didn't see Jeremy respond to this. Did you open a Bugzilla against anaconda? /Brian/ On Thu, 2004-08-12 at 10:34, Philip Molter wrote: > The anaconda code in fsset.py creates all raid5 arrays with the > '--dangerous-no-resync' flag. That flag is labeled like that for a > reason. If you initialize a RAID5 array, you MUST initialize parity on > the array. If you don't then when a drive fails out, you will encounter > corruption as the data rebuilt from parity won't match that of the disk > that failed out. The only exception to this is if the drive has been > zeroed out beforehand, but anaconda's not doing that either (and > shouldn't, I don't think). > > It's imperative that this flag be removed from raid5 array creation. > > Philip > > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/anaconda-devel-list -- Brian Long | | | IT Data Center Systems | .|||. .|||. Cisco Linux Developer | ..:|||||||:...:|||||||:.. Phone: (919) 392-7363 | C i s c o S y s t e m s
