generic: test for fsync after adding hard link to a file

This test is motivated by an issue found in btrfs.

It tests that after syncing the filesystem, adding a hard link to a file,
syncing the filesystem again, doing a write to the file that increases
its size and then doing a fsync against that file, durably persists the
data written to the file. That is, after log/journal replay, the data
is available.

The btrfs issue is fixed by the commit titled:

  "Btrfs: fix fsync data loss after append write"

Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Eryu Guan <eguan@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
This commit is contained in:
Filipe Manana
2015-08-04 14:10:48 +10:00
committed by Dave Chinner
parent d48469086a
commit 3cc93641da
3 changed files with 126 additions and 0 deletions
+1
View File
@@ -92,6 +92,7 @@
087 perms auto quick
088 perms auto quick
089 metadata auto
090 metadata auto quick
091 rw auto quick
092 auto quick prealloc
093 attr cap udf auto