diff options
author | Eric Sandeen <sandeen@redhat.com> | 2017-01-09 10:49:21 -0600 |
---|---|---|
committer | Eryu Guan <eguan@redhat.com> | 2017-01-15 13:56:45 +0800 |
commit | 9ef7c4e3dcc06f93a38d8919c949ca3a1e201a48 (patch) | |
tree | 11f1c95b19e1473ce4796dd5ae708af3ea29ff34 | |
parent | 1abe96278d4a540acc9680fa37f8aaacbdd2bdec (diff) | |
download | xfstests-dev-9ef7c4e3dcc06f93a38d8919c949ca3a1e201a48.tar.gz |
xfs/010: explicitly allow corrupted write in xfs_db
xfs/010 wants to write corruption and test how xfs_repair
deals, but when:
xfs: forbid AG btrees with level == 0
is merged to userspace, this new test fails the write verifier
in xfs_db.
Add "-c" to allow the corrupted write, do the corruptions all
in one xfs_db command (so it doesn't have to re-read the
corrupted data on 2nd startup), and filter out the
"Allowing write of corrupted data and bad CRC"
output from the "write -c" command.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Reviewed-by: Brian Foster <bfoster@redhat.com>
Signed-off-by: Eryu Guan <eguan@redhat.com>
-rwxr-xr-x | tests/xfs/010 | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/tests/xfs/010 b/tests/xfs/010 index d350d64125..b9f28915dc 100755 --- a/tests/xfs/010 +++ b/tests/xfs/010 @@ -95,8 +95,11 @@ _corrupt_finobt_root() dev=$1 # nuke the agi finobt root fields - $XFS_DB_PROG -x -c "agi 0" -c "write free_root 0" $dev - $XFS_DB_PROG -x -c "agi 0" -c "write free_level 0" $dev + $XFS_DB_PROG -x \ + -c "agi 0" \ + -c "write -c free_root 0" \ + -c "write -c free_level 0" \ + $dev | grep -v "Allowing write of corrupted" } # real QA test starts here |