Darrick J. Wong ab2cd4a4d2 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 14:19:42 -04:00
..
expect	e2fsck: don't flush the FS unless it's actually dirty	2014-08-12 14:19:42 -04:00
image.gz	e2fsck: don't flush the FS unless it's actually dirty	2014-08-12 14:19:42 -04:00
name	e2fsck: don't flush the FS unless it's actually dirty	2014-08-12 14:19:42 -04:00
script	e2fsck: don't flush the FS unless it's actually dirty	2014-08-12 14:19:42 -04:00