On Fri, 13 Jun 2008, Douglas A. Tutty wrote: > On Fri, Jun 13, 2008 at 02:32:29PM -0300, Henrique de Moraes Holschuh wrote: > > Your / should be small, fsck-friendly, and resilient as all heck. If > > running fsck in your / takes enough time that you wouldn't afford to do it > > at every boot (in a recent system), then your / is too large in my book. > > > > The same holds for any other partition you can't easily umount to fsck in > > maintenance mode. > > Agreed. / only needs to be 300 MB or so with a separate /boot (if > needed for the hardware). / with /boot easily fits in 512 MB and takes > only a few seconds to fsck with ext3 and with data=journal still runs > pleanty fast.
Watch out that data=journal. It is far more kernel-bug prone than data=ordered, for the simple fact that almost everyone uses data=ordered, including those who mess with the ext3 code, so bugs can hide in the data=journal code paths a lot more easily. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
