Files
apfstests/tests/generic/341.out
T
Filipe Manana 5b13255306 generic: add test for fsync after renaming directory
Test that if we rename a directory, create a new file or directory that
has the old name of our former directory and is a child of the same
parent directory, fsync the new inode, power fail and mount the
filesystem, we see our first directory with the new name and no files
under it were lost.

This test is motivated by an issue found in btrfs which is fixed by the
following patch for the linux kernel:

  "Btrfs: fix file loss caused by fsync after rename and new inode"

Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Eryu Guan <eguan@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
2016-04-05 11:47:31 +10:00

22 lines
600 B
Plaintext

QA output created by 341
wrote 32768/32768 bytes at offset 0
XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
wrote 32768/32768 bytes at offset 0
XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
File digests before power failure:
b6ef98c3df97dfc5ff17266311c2fb9e SCRATCH_MNT/a/x/foo
41107c24d306bdc4fecac4007e9aa214 SCRATCH_MNT/a/x/bar
Directory a/ contents after log replay:
SCRATCH_MNT/a:
x
y
SCRATCH_MNT/a/x:
SCRATCH_MNT/a/y:
bar
foo
File digests after log replay:
b6ef98c3df97dfc5ff17266311c2fb9e SCRATCH_MNT/a/y/foo
41107c24d306bdc4fecac4007e9aa214 SCRATCH_MNT/a/y/bar