Long time ago I noticed that forced reboot from multiuser (/ mounted
rw long time ago) sometimes does not force filesystem check. It
happened again today...
So I remounted r/o and fsck-ed. And hey, they are errors: [zero dtimes
are ok, but bitmap differences really are not].
I *think* that we do not force ordering of "mark filesystem unclean"
and writes to filesystem. And we really *should* force that
ordering... Quick and dirty solution would be to sync just after we
mark filesystem dirty...
Pavel
root@bug:~# fsck -f /dev/hda1
Parallelizing fsck version 1.18 (11-Nov-1999)
e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 480986 has zero dtime. Fix<y>? yes
Deleted inode 481006 has zero dtime. Fix<y>? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong for group #2 (37, counted=42).
Fix<y>? yes
Free blocks count wrong (14705, counted=14710).
Fix<y>? yes
Inode bitmap differences: -480986 -481006
Fix<y>? yes
Free inodes count wrong for group #15 (24936, counted=24938).
Fix<y>? yes
Free inodes count wrong (755991, counted=755993).
Fix<y>? yes
/dev/hda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/hda1: 173863/929856 files (10.6% non-contiguous), 915044/929754
blocks
root@bug:~#
-- I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care." Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/