Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
f2fs-tools: don't call fsync on a clean image
generic/019 50s ... _check_generic_filesystem: filesystem on /dev/vdc is inconsistent (see /media/fstests/results//generic/019.full for details) [FSCK] Max image size: 16196 MB, Free space: 188 MB [FSCK] Unreachable nat entries [Ok..] [0x0] [FSCK] SIT valid block bitmap checking [Ok..] [FSCK] Hard link checking for regular file [Ok..] [0x166] [FSCK] valid_block_count matching with CP [Ok..] [0x3ecfe7] [FSCK] valid_node_count matching with CP (de lookup) [Ok..] [0x4c79] [FSCK] valid_node_count matching with CP (nat lookup) [Ok..] [0x4c79] [FSCK] valid_inode_count matched with CP [Ok..] [0xb46] [FSCK] free segment_count matched with CP [Ok..] [0x9d] [FSCK] next block offset is free [Ok..] [FSCK] fixing SIT types [FSCK] other corrupted bugs [Ok..] Error: Could not conduct fsync!!! Generic/019 will trigger fsync() on a clean image, but it will fail due to simulated failure on disk, result in testcase failure. Let's add c.need_fsync to record dirty status of image, and only trigger fsync() when there is dirty data in image. Signed-off-by: Chao Yu <chao@kernel.org> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
- Loading branch information