diff mbox series

[v2,1/2] xfs/288: use -d option of xfs_db write command for v5 XFS

Message ID 20180731054119.13539-1-zlang@redhat.com (mailing list archive)
State Accepted
Headers show
Series [v2,1/2] xfs/288: use -d option of xfs_db write command for v5 XFS | expand

Commit Message

Zorro Lang July 31, 2018, 5:41 a.m. UTC
The commit b3cf8b72334fd35ef961869506e5a72ab398bc82 update xfs/288
to support v5 filesystem testing. That commit thought xfs_db write
command can work well with -d option on V5 XFS. But the truth is
the case doesn't use that option.

So turn to use _scratch_xfs_set_metadata_field, it will help to use
proper options for xfs_db write command.

Signed-off-by: Zorro Lang <zlang@redhat.com>


This patch has been reviewed by Darrick J. Wong:

I sent this patch again only because it's related with next [2/2] patch.


 tests/xfs/288 | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)
diff mbox series


diff --git a/tests/xfs/288 b/tests/xfs/288
index bccdb6fc..f4165b6c 100755
--- a/tests/xfs/288
+++ b/tests/xfs/288
@@ -56,9 +56,8 @@  $SETFATTR_PROG -n "user.testattr${seq}" \
 # manually corrupt the XFS, by set the header count of attr to 0
-_scratch_xfs_db -x -c "inode $inum" \
-		   -c "ablock 0" \
-		   -c "write hdr.count 0" >> $seqres.full
+_scratch_xfs_set_metadata_field "hdr.count" "0" \
+				"inode $inum" "ablock 0" >> $seqres.full
 # make sure xfs_repair can find above corruption. If it can't, that
 # means we need to fix this bug on current xfs_repair