apfstests/tests/generic/348.out at 8cfd58a5dbb9bbf8924c68f4ca13bfe41eabce91 - apfstests - ProxGit

apfs/apfstests

mirror of https://github.com/linux-apfs/apfstests.git synced 2026-05-01 15:01:44 -07:00

Files

T

Filipe Manana 238397db22 generic: test creating a symlink and then fsync its parent directory

Test creating a symlink, fsync its parent directory, power fail and mount
again the filesystem. After these steps the symlink should exist and its
content must match what we specified when we created it (must not be
empty or point to something else).

This is motivated by an issue in btrfs where after the log replay happens
we get empty symlinks, which not only does not make much sense from a
user's point of view, it's also not valid to have empty links in linux
(wgich is explicitly forbidden by the symlink(2) system call).

The issue in btrfs is fixed by the following patch for the linux kernel:

  "Btrfs: fix empty symlink after creating symlink and fsync parent dir"

Tested against ext3, ext4, xfs, f2fs, reiserfs and nilfs2.

Signed-off-by: Filipe Manana <fdmanana@suse.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>

2016-05-09 10:57:39 +10:00

5 lines

94 B

Plaintext

Raw Blame History

 QA output created by 348
 Symlink contents after log replay:
 SCRATCH_MNT/foo1
 SCRATCH_MNT/foo2