apfs/apfstests
0
0
Fork 0
mirror of https://github.com/linux-apfs/apfstests.git synced 2026-05-01 15:01:44 -07:00
Code Issues Packages Projects Releases Wiki Activity

generic/459: use xfs_freeze instead of fsfreeze

Browse Source 
This is what all other tests use as well as _require_freeze

Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Reviewed-by: Eryu Guan <guaneryu@gmail.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
This commit is contained in:
Amir Goldstein
2018-05-14 08:49:49 +03:00
committed by Eryu Guan
parent 287b2e05b5
commit 60300eb6e1
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/generic/459
+3 -3
View File
@@ -113,7 +113,7 @@ $XFS_IO_PROG -f -d -c 'pwrite -b 1m 0 120m' $SCRATCH_MNT/f1 >>$seqres.full 2>&1
# extended. It is expected, and is only used so xfsaild is triggered to
# flush AIL items, other filesystems usually get remounted as read-only during
# the above write process.
fsfreeze -f $SCRATCH_MNT >>$seqres.full 2>&1 &
xfs_freeze -f $SCRATCH_MNT >>$seqres.full 2>&1 &
freezeid=$!
# Wait enough so xfsaild can run
@@ -132,7 +132,7 @@ ret=$?
# - The filesystem stays in Read-Write mode, but can be frozen/thawed
# without getting stuck.
if [ $ret -ne 0 ]; then
# fsfreeze failed, filesystem should reject further writes and remount
# freeze failed, filesystem should reject further writes and remount
# as readonly. Sometimes the previous write process won't trigger
# ro-remount, e.g. on ext3/4, do additional touch here to make sure
# filesystems see the metadata I/O error.
@@ -148,7 +148,7 @@ if [ $ret -ne 0 ]; then
else
# Try to thaw the filesystem, and complete test if if succeed.
# NOTE: This will hang on affected XFS filesystems.
fsfreeze -u $SCRATCH_MNT >>$seqres.full 2>&1
xfs_freeze -u $SCRATCH_MNT >>$seqres.full 2>&1
echo "Test OK"
fi