Theodore Ts'o a3efe48420 e2fsck: fix mysterious "FILE SYSTEM WAS MODIFIED" with no changes ... Commit 2a77a784a3 (firest released in e2fsprogs 1.33) compared superblock summary free blocks and inode counts with the allocation bitmap counts before starting the file system check proper, and if they differed, set the superblock and marked it as dirty. If no other file systme changes were required, this would cause a "*** FILE SYSTEM WAS MODIFIED ***" message without any explanation of what e2fsck had changed. We fix this by only setting the superblock summary free block/inodes counts if we are skipping a full check, and in non-preen mode, e2fsck will now print an explicit message stating how the superblock had been updated. In a full check, any updates to the superblock free blocks/inodes fields will be noted in pass5. This change requires changing a few test results (essentially reversing the changes made in commit 2a77a784a3). Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>		2011-06-16 01:22:02 -04:00
..
expect.1	e2fsck: fix mysterious "FILE SYSTEM WAS MODIFIED" with no changes	2011-06-16 01:22:02 -04:00
expect.2	Many files:	1997-04-29 16:17:09 +00:00
image.gz	Many files:	1997-04-29 16:17:09 +00:00
name	Many files:	1997-04-29 16:17:09 +00:00