> > If you boot single-user and run "/sbin/fsck -pw", what happens? > I have made 10 times a single-user boot followed by the command : > /sbin/fsck -pw --debug > It hangs 3 times with the same debug infos I got when I tried a > multi-user boot : > [main: Reading /etc/fstab...] > [main: Fscking...] > [fsck: Pass 1] > [fsck: /: Fsckable; free_slots = 100] > [fscks_start_fsck: /: Checking mounted state] > [fscks_start_fsck: /: Checking readonly state] > [fscks_start_fsck: /: Making readonly] > [fscks_start_fsck: /: Will make writable after fscking if possible] > > The rest of the times, it works all right and said that my root > partition is clean : > [main: Reading /etc/fstab...] > [main: Fscking...] > [fsck: Pass 1] > [fsck: /: Fsckable; free_slots = 100] > [fscks_start_fsck: /: Checking mounted state] > [fscks_start_fsck: /: Checking readonly state] > [fscks_start_fsck: /: Making readonly] > [fscks_start_fsck: /: Will make writable after fscking if possible] > [fs_start_fsck: /: Spawned pid 18: /sbin/fsck.ext2 -p /dev/hd2s2] > [fscks_wait: Waiting...] > /dev/hd2s2: clean, .../... files, .../...1 blocks > [fscks_wait: /: Fsck finished (status = 0)] > [fsck_cleanup: /: Cleaning up after fsck (remount = 0, make_writable = > 1)] > [fsck_cleanup: /: Making writable]
Please notice the messages right at boot, just before `Hurd server bootstrap'. There should be a message there about the filesystem not being clean if it was not clean at boot-time. Was there ever a time you did not see this message and then had a problem? Was there ever a time you did see this message and then did not have a problem? > > If you boot single-user and run "e2fsck -p /dev/your-root-device"? > It never crashed. It always told that my root partition was not > cleanly unmounted. Note that if you did not do `fsysopts / --readonly', then your filesystem is still mounted read/write (and therefore has had its clean flag dirtied) while you run e2fsck. It is always a bad idea to run e2fsck while the filesystem is mounted read/write. The fsck wrapper program changes the filesystem to read-only for you before it runs e2fsck. > After a single-user boot, I tried : > /sbin/fsck -pw --debug > followed by the command : > e2fsck -p /dev/hd2s2 > > The first one said that my disk is clean, but the second one found > that the partition was not cleanly unmounted ! Clearly there is a > problem here. No, that does not indicate a problem. The fsck wrapper program (/sbin/fsck) made the filesystem writable again after it ran e2fsck (just like its debugging messages say it's doing); that is the meaning of the -w flag. Then, you ran e2fsck again yourself without making the filesystem read-only first.
