apfstests/tests/btrfs/209.out at 6df280a684763501ce65bb2df5fc7742809f7600 - 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 74278dc293 btrfs: test power fail after a ranged fsync when not using the no-holes feature

Test a scenario were we fsync a range of a file and have a power
failure.  We want to check that after a power failure and mounting
the filesystem, we do not end up with a missing file extent
representing a hole. This applies only when not using the NO_HOLES
feature.

This currently fails on btrfs but it is fixed by a patch for the kernel
that has the following subject:

  "Btrfs: fix missing file extent item for hole after ranged fsync"

Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>

2020-03-22 22:16:55 +08:00

8 lines

357 B

Plaintext

Raw Blame History

 QA output created by 209
 wrote 262144/262144 bytes at offset 0
 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
 wrote 786432/786432 bytes at offset 262144
 XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
 File digest before power failure: c0bf141ef2500fcc894f754ead04f02d
 File digest after power failure: c0bf141ef2500fcc894f754ead04f02d