mirror of
https://github.com/linux-apfs/apfstests.git
synced 2026-05-01 15:01:44 -07:00
fstests: generic test for directory fsync after adding hard links
This test is motivated by an fsync issue discovered in btrfs. The issue was that after adding a new hard link to an existing file (one that was created in a past transaction) and fsync'ing the parent directory of the new hard link, after the fsync log replay the file's inode link count did not get its link count incremented, while the new directory entry was visible. Also, unlike xfs and ext4, new files under the directory we fsync were not being written to the fsync log, nor were any child directories and new files and links under the children directories. So this test verifies too that btrfs has the same behaviour as xfs and ext4. The btrfs issue was fixed by the following linux kernel patch: Btrfs: fix metadata inconsistencies after directory fsync Signed-off-by: Filipe Manana <fdmanana@suse.com> Reviewed-by: Eric Sandeen <sandeen@redhat.com> Signed-off-by: Dave Chinner <david@fromorbit.com>
This commit is contained in:
committed by
Dave Chinner
parent
cd210408a0
commit
036a163772
@@ -67,6 +67,7 @@
|
||||
062 attr udf auto quick
|
||||
063 auto quick prealloc
|
||||
064 auto quick prealloc
|
||||
065 metadata auto quick
|
||||
068 other auto freeze dangerous stress
|
||||
069 rw udf auto quick
|
||||
070 attr udf auto quick stress
|
||||
|
||||
Reference in New Issue
Block a user