e2fsprogs/tests/f_readonly_fsck/expect

Pass 1: Checking inodes, blocks, and sizes
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 (4294968254, counted=958).
Fix? no

test_filesys: 11/256 files (9.1% non-contiguous), 18446744069414585410/2048 blocks
Exit status is 0
crc did not change.  2466215161
e2fsck: don't flush the FS unless it's actually dirty ext2fs_flush2() unconditionally writes the block group descriptors to disk even if the underlying FS isn't marked dirty. This causes the following error message on a fsck -n run: e2fsck 1.43-WIP (09-Jul-2014) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Error writing block 2 (Attempt to write block to filesystem resulted in short write). Ignore error? no Error writing block 2 (Attempt to write block to filesystem resulted in short write). Ignore error? no Error writing file system info: Attempt to write block to filesystem resulted in short write Since ext2fs_close2() only calls flush if the dirty flag is set, modify e2fsck to exhibit the same behavior so that we don't spit out write errors for a read only check. Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu> 2014-08-12 22:19:37 +04:00			`Pass 1: Checking inodes, blocks, and sizes`
			`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 (4294968254, counted=958).`
			`Fix? no`

			`test_filesys: 11/256 files (9.1% non-contiguous), 18446744069414585410/2048 blocks`
			`Exit status is 0`
			`crc did not change. 2466215161`