Reiser4 fsck in Slackware Current
How does Slackware control whether fsck is activated?
My fstab is very simple, using Reiser4 with 220.127.116.11 kernel:
/dev/hda5 / reiser4 noatime,nodiratime 0 0
/dev/hda6 swap swap defaults 0 0
Whether I have passno set for O or 1, on startup I see fsck /dev/hda5
If I add a non-root partition to my fstab and vary the passno from 0 to 1, it does control whether that reiser3.6 partition is fsck.
I have two other linux OS installed, Gentoo and Arch, both with Reiser4 and identical fstab and kernel configurations.
Those systems will fsck R4 if the passno is set to 1, but will skip fsck if passno is set to 0.
Is the fsck really running, or what's going on? I can't decipher the script well enough in rc.S to tell what I need to change to make Slackware look at fstab for my fsck wishes.
Most distributions will check for the prescence of a forcefsck file upon bootup. If found, it will force a filesystem check irregardless of the fstab entry. Run a find / -name forcefsck as root on your system (I think it is /etc/forcefsck on Slackware) and remove it. Then reboot and see what happens. If you still have problems, tell me which script it is being called by and I can decipher it for you.
|All times are GMT -5. The time now is 08:51 PM.|