1. fsck fsck fsck say I
How do I persuade fsck to run again?
From my second fsck, I falsely get told "/: clean" almost instantly
without much happening unless I resort to the kluges I see Google
/sbin/tune2fs -c 5 -C 5 /dev/hd$v$n
That works, but I see tune2fs -c -C have side effects (that as yet I'm
too ignorant to understand or confidently undo) in:
/sbin/tune2fs -l /dev/hd$v$n
Is there actually no more direct way to tell fsck that I typed the
verb fsck because I actually do mean for fsck to run again, not just
echo the stale cached results of its last run?
I care because often when I force fsck to run again I find and fix
more trouble. Running again on demand saves me the time - and more
importantly the interaction - of rebooting.
Via Google I hear there is a tradition of fsck -y means yes I said
fsck because I meant fsck. But fsck -y doesn't work here.
Anybody know? How do I persuade fsck to run again? Here in
comp.unix.shell do I find people interested in this question, besides
me? Or is there a better place nearby?
Thanks in advance, Pat LaVarre
P.S. The exercise of writing this post suggest to me I could try
mounting and unmounting after fsck. While that writes who knows what
to my disk, it might often write nothing very harmful and yet still
persuade fsck to run again. Even so, I'd like to learn how to tell
fsck to run when I want it to run, for example so I can observe,
without actually asking to write anything, whether or not I do get the
same results twice in a row.
2. Copy/paste bug on Solaris 8?
3. fsck fsck say I
4. Apache 1.2.6--error opening logs
5. help pls - fsck fail on boot; fixed, fsck still fails on boot
6. kazaa for linux ?
7. Problem: On bootup always says to run fsck
8. passerelle prologue -> linux
9. Disk clean on bootup, fsck says it's not clean
10. fsck exit with signal 11. 60 GB maxtor disk. fsck hangs
11. Help, FSCK: Redhat 5.0: FSCK runs on first bootup EACH DAY? Can't find the configuration file
12. Have to run fsck on /home every reboot
13. Elite 9 v fsck