http://bugzilla.novell.com/show_bug.cgi?id=585742 http://bugzilla.novell.com/show_bug.cgi?id=585742#c0 Summary: fsck reports errors when run with -n on mounted ext4 fs, but no errors when remounted readonly Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: HP OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ramon.casha@linux.org.mt QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 I ran the command "fsck -n" on the mounted root filesystem and got a list of errors. I rebooted to single-user mode, remounted the filesystem readonly and ran "fsck -f" but this gave no errors. I remounted it read-write and ran fsck and got the same errors again. Reproducible: Always Steps to Reproduce: fsck -n -f mount -o remount,ro /dev/sda1 / fsck -f Actual Results: First fsck: fsck from util-linux-ng 2.16 e2fsck 1.41.9 (22-Aug-2009) Warning! /dev/sda1 is mounted. Warning: skipping journal recovery because doing a read-only filesystem check. /dev/sda1 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Inodes that were part of a corrupted orphan linked list found. Fix? no Inode 1239 was part of the orphaned inode list. IGNORED. Inode 1354 was part of the orphaned inode list. IGNORED. Inode 917831 was part of the orphaned inode list. IGNORED. Inode 917836 was part of the orphaned inode list. IGNORED. Inode 917839 was part of the orphaned inode list. IGNORED. Inode 917840 was part of the orphaned inode list. IGNORED. Deleted inode 917848 has zero dtime. Fix? no Inode 917849 was part of the orphaned inode list. IGNORED. Inode 917857 was part of the orphaned inode list. IGNORED. Inode 917860 was part of the orphaned inode list. IGNORED. Inode 917862 was part of the orphaned inode list. IGNORED. Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Block bitmap differences: +(15136855--15136864) -(15136865--15136868) -(15182336--15182341) -15499414 -(15505408--15505418) -(15509530--15509544) -(15515648--15515726) Fix? no Free blocks count wrong for group #461 (18066, counted=18072). Fix? no Free blocks count wrong for group #463 (22515, counted=22509). Fix? no Free blocks count wrong for group #473 (27175, counted=27159). Fix? no Free blocks count wrong (8076210, counted=8074199). Fix? no Inode bitmap differences: -1239 -1354 -917831 -917836 -(917839--917840) -(917848--917849) -917857 -917860 -917862 Fix? no Free inodes count wrong (7911248, counted=7911111). Fix? no /dev/sda1: ********** WARNING: Filesystem still has errors ********** /dev/sda1: 1599664/9510912 files (0.3% non-contiguous), 29947629/38023839 blocks ===================================================== Second fsck produced no errors at all I don't know yet whether this is a problem with fsck reporting inexistent errors on mounted filesystems, or whether there really are errors which are not being reported when the fs is mounted readonly - so I have marked this as critical in case it is the latter. On one occasion I ran "fsck -n" and got a number of files that contained errors, but on running the same command immediately after, these were no longer among the errors. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.