Subject: Re: bin/1219: [dM] fsck is too aggressive about clean flags
To: der Mouse <mouse@Collatz.McRCIM.McGill.EDU>
From: Chris G Demetriou <Chris_G_Demetriou@BALVENIE.PDL.CS.CMU.EDU>
List: netbsd-bugs
Date: 07/13/1995 08:05:04
[ this is my last message about on this topic. ]
> To my mind, it's not so much a question of interpreting the clean flag
> as doing what I tell it to. To my mind, "fsck /dev/foo" means "check
> /dev/foo", and if it doesn't check it, it's not doing what I told it.
What does "to check a file system" mean?
both "fsck -p", and "fsck" interpret as "make it clean, if it's not
already clean, and don't touch it if it is."
by your statment above, saying:
fsck
means "check all file systems." how many ways should "check a file
system" be defined?
and now for a "personal use" question...
> At the moment, perhaps, because I mistrust clean bits enough that I
> want -f even with -p. But if they get done right, then that alias is
> too much, because then if I type fsck -p I don't get the not-if-clean
> behavior.
how often do you 'fsck -p'?
i don't do it often, because if i'm rebooting to single-user mode,
then i know the file systems are as clean as fsck -p would make them,
so i don't bother. if i'm booting multi-user, i don't type it at all.
just about the only time _i_ type fsck -p is if i'm being paranoid, or
if i boot to single-user after a crash (which tends to be infrequent).
cgd