On 24 Apr 2018, at 20:35, Jayashree Mohan wrote:
Hi,
While investigating crash consistency bugs on btrfs, we came across
workloads that demonstrate inconsistent behavior of fsync.
Consider the following workload where fsync on the directory did not
persist it.
Only file B/foo gets persisted, and both A/foo and C/foo are missing.
This seems like inconsistent behavior as only the first fsync persists
the file, while all others don't seem to. Do you agree if this is
indeed incorrect and needs fixing?
All the above tests pass on ext4 and xfs.
Please let us know what you feel about such inconsistency.
The btrfs fsync log is more fine grained than xfs/ext, but fsync(any
file) should be enough to persist that file in its current directory.
I'll get these reproduced and see if we can nail down why we're not
logging the location properly.
-chris
--
To unsubscribe from this list: send the line "unsubscribe fstests" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
