On Mon, 2008-07-28 at 14:46 +0100, Bryn M. Reeves wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Patrick O'Callaghan wrote: > > On Mon, 2008-07-28 at 09:29 +0800, John Summerfield wrote: > >> For years, the default on RH (and successor) systems has been to only > >> do > >> filesystem checks if the filesystem is dirty. Checks based on > >> intervals > >> and mounts are not done. > > > > I'm not sure that's true. I've definitely seen boot-time messages along > > the lines of "mount count exceeded; performing fsck", and I never change > > the defaults. > > It is true for file systems that anaconda creates. The installer does > the equivalent of "tune2fs -c0 -i0" on the file systems that it creates. > If you are creating file systems post-install with mkfs/mke2fs then this > step needs to be done manually. This is usually the cause of "maximal > mount count reached.." and "/dev/blah has not been checked in XX days" > messages on Red Hat systems that I've come across. OK, that makes sense. poc -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list