2 # SPDX-License-Identifier: GPL-2.0
3 # Copyright (C) 2014 SUSE Linux Products GmbH. All Rights Reserved.
7 # Regression test for a btrfs issue where if right after the snapshot creation
8 # ioctl started, a file write followed by a file truncate happened, with both
9 # operations increasing the file's size, the created snapshot would capture an
10 # inconsistent state of the file system tree. That state reflected the file
11 # truncation but it didn't reflect the write operation, and left a gap between
12 # two file extent items (and that gap corresponded to the total or a partial
13 # area of the write operation's range).
15 # This issue was fixed by the following linux kernel patch:
17 # Btrfs: fix snapshot inconsistency after a file write followed by truncate
20 seqres=$RESULT_DIR/$seq
21 echo "QA output created by $seq"
23 status=1 # failure is the default!
24 trap "_cleanup; exit \$status" 0 1 2 3 15
28 for p in ${cpu_stress_pids[*]}; do
34 # get standard environment, filters and checks
38 # real QA test starts here
40 _require_scratch_nocheck
46 local ts=`date +'%H_%M_%S_%N'`
48 _run_btrfs_util_prog subvolume snapshot -r \
49 $SCRATCH_MNT $SCRATCH_MNT/"${ts}_snap"
56 run_check $XFS_IO_PROG -f \
57 -c "pwrite -S 0xaa -b 32K 0 32K" \
59 -c "pwrite -S 0xbb -b 32770 16K 32770" \
76 if [ $create_ret != 0 -o $snap_ret != 0 ]; then
77 _fail "Failure creating file or snapshot, check $seqres.full for details"
81 # If the installed btrfs mkfs supports the no-holes feature, make sure the
82 # created fs doesn't get that feature enabled. With it enabled, the below fsck
83 # call wouldn't fail. This feature hasn't been enabled by default since it was
84 # introduced, but be safe and explicitly disable it.
85 _scratch_mkfs -O list-all 2>&1 | grep -q '\bno\-holes\b'
87 mkfs_options="-O ^no-holes"
89 _scratch_mkfs "$mkfs_options" >>$seqres.full 2>&1
93 # Run some background load in order to make the issue easier to trigger.
94 # Specially needed when testing with non-debug kernels and there isn't
95 # any other significant load on the test machine other than this test.
96 num_cpus=`$here/src/feature -o`
97 num_procs=$(($num_cpus * 20))
98 for ((i = 0; i < $num_procs; i++)); do
102 cpu_stress_pids[$i]=$!
105 for ((i = 1; i <= 100; i++)); do
109 for ((i = 0; i < $num_procs; i++)); do
110 kill ${cpu_stress_pids[$i]} &> /dev/null
111 unset cpu_stress_pids[$i]
114 for f in $(find $SCRATCH_MNT -type f -name 'foobar_*'); do
115 digest=`md5sum $f | cut -d ' ' -f 1`
117 "d41d8cd98f00b204e9800998ecf8427e")
120 "c28418534a020122aca59fd3ff9581b5")
121 # ok, only first write captured
123 "cd0032da89254cdc498fda396e6a9b54")
124 # ok, only 2 first writes captured
126 "a1963f914baf4d2579d643425f4e54bc")
127 # ok, the 2 writes and the truncate were captured
130 # not ok, truncate captured but not one or both writes
131 _fail "Unexpected digest for file $f"
135 # Check the filesystem for inconsistencies.
136 # Before the btrfs kernel fix mentioned above, we would very often get fsck
137 # error messages like: "root 306 inode 338 errors 100, file extent discount".
139 # This was because if right after the snapshot creation ioctl started, a file
140 # write followed by a file truncate, with both operations increasing the file's
141 # size, we would get a snapshot that reflected a state where the file truncation
142 # was visible but the previous file write was not visible, breaking expected
143 # total ordering of operations and causing a gap between 2 file extents, where a
144 # file extent item representing the range [32K .. ALIGN(16K + 32770, 4096)] was
145 # missing in the snapshot's btree.
148 echo "Silence is golden"