On Jul 14, 2009, at 12:00, Jordi Soucheiron wrote:
I'm working on afew alix based devices working under voyage 0.6 with a
custom kernel. I found that one of this devices had the file system
corrupt (I'm using ext2 in some devices and ext3 in some other devices
I don't remember if it was one or the other, but I don't think this is
relevant to the problem). When I looked at the mount count it almost
doubled the amount that should trigger the automatic fsck on boot. I
been trying to find why fsck hasn't run at boot time even with that
mount count and with a filesystem state of not clean (the only reason
I can think of is that due some packages installed the filesystem is
always in rw mode once set that way). I'd like to have fsck up and
running again on boot time. Any ideas?
I believe voyage uses the standard debian scripts regarding fsck at
boot time:
/etc/init.d/checkroot.sh
/etc/init.d/checkfs.sh
These assume you have access to the console on boot up and may prompt
you either to confirm repairs or even to run fsck manually from a
shell. There's a setting FSCKFIX=yes/no in /etc/default/rcS that has
some effect (see rcS(5) or http://da2i.univ-lille1.fr/cgi-bin/man/man2html?rcS+5)
. Finally, there's a field in /etc/fstab that affects whether "fsck -
a" checks a given filesystem -- not sure if it applies to the root
filesystem.
Cheers
Robert
_______________________________________________
Voyage-linux mailing list
[email protected]
http://list.voyage.hk/mailman/listinfo/voyage-linux
