On Mon, Dec 01, 2003 at 11:17:42AM -0700, Monique Y. Herman wrote: > On Mon, 01 Dec 2003 at 16:55 GMT, Alan Shutko penned: > > Nick Welch <mack@incise.org> writes: > > > >> I suppose mke2fs(8) is where that comes from specifically. Easy to > >> disable the periodic checks, though: > >> > >> tune2fs -i 0 -c 0 /dev/hda6 > > > > That's a very bad idea. As the manpage says: > > > > You should strongly consider the consequences of disabling > > mount-count-dependent checking entirely. Bad disk drives, cables, > > memory, and kernel bugs could all corrupt a filesystem without > > marking the filesystem dirty or in error. If you are using > > journaling on your filesystem, your filesystem will never be > > marked dirty, so it will not normally be checked. A filesystem > > error detected by the kernel will still force an fsck on the next > > reboot, but it may already be too late to prevent data loss at > > that point. > > > > Wait, wait; I'm confused. I thought one of the perks of running a > journalling file system was that you can speed up the boot process by > disabling boot-time fsck? > I guess there's no free lunch. But is there some way to schedule fsck at some regular time when you know you won't be needing the mounted file system? e.g. at 3am local time, or maybe 3pm for night owls? -- Paul E Condon pecondon@peakpeak.com
Attachment:
pgpLI46WxdK54.pgp
Description: PGP signature