On 9/6/11 5:10 PM, John Reiser wrote: > On 09/02/2011 12:01 PM, David Lehman wrote: >> I should point out that this will have some other consequences. First, >> we will no longer offer to create new ext2 or ext3 filesystems. (In >> fact, specifying ext2 or 3 via kickstart will lead to us making you an >> ext4 fs.) > > For faster installs I specify ext2 because it has no journal. > (I convert later to ext3.) If ext2 and ext3 are going away, > then please add the option to create ext4 _with_ journal, > but turn off journalling for the rest of the install. > > As long as an install cannot be resumed "in the middle", then > the journal's advantage of easy recovery after an interruption > (failure of power, network, drive/media, etc.) does not pay off > in practice. The only real way to do this would be to tune2fs the journal off, and then tune2fs it on again when done. And I think you may not end up with an ideally-placed journal if you do that - and possibly even a fragmented one. So I'm not sure I'd really recommend it. I hesitate to even suggest this, but: Running the install with barriers off would speed things up too, for what it's worth, and that's just a mount option. As long as you're willing to accept damage if you lose power halfway through. IOW, it should only be for a fresh install, and never for an upgrade... -Eric _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
