xfs
[Top] [All Lists]

[PATCH] xfstests: 311: fsck the dmflakey device instead of the real devi

To: <xfs@xxxxxxxxxxx>
Subject: [PATCH] xfstests: 311: fsck the dmflakey device instead of the real device
From: Josef Bacik <jbacik@xxxxxxxxxxxx>
Date: Tue, 14 May 2013 16:35:22 -0400
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fusionio.com; s=default; t=1368563725; bh=OIho6nzzxYKxP3TE+mVgjtItm80cSRN4Ni5FD25f4vY=; h=From:To:Subject:Date; b=IfjD/rmS+YEF5Dp9Fyjnv4KEVbl1ejYx5A0K/S7ZwIORhBe7dXFKwZvBLxl4FRCUg QMfWlbUkNKhtKUHWxsB/AZZ894UDl9yzsh2tBNEGcroVIfdR83jzE0WvmIsqevzevm JiU10c4aYrmk2+LFZt/HtsUNDb3kdehz1/NAsjcA=
Dave pointed out that xfs was having issues with 311 because of caching issues.
He suggested that I fsck the dm-flakey device to make sure we don't have this
problem.  This is the easiest way I could think to accomplish this, please let
me know if this is a bad idea.  Thanks,

Signed-off-by: Josef Bacik <jbacik@xxxxxxxxxxxx>
---
 tests/generic/311 |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/tests/generic/311 b/tests/generic/311
index 2b3b569..f11119b 100644
--- a/tests/generic/311
+++ b/tests/generic/311
@@ -125,7 +125,10 @@ _run_test()
 
        #Unmount and fsck to make sure we got a valid fs after replay
        _unmount_flakey
+       tmp=$SCRATCH_DEV
+       SCRATCH_DEV=$FLAKEY_DEV
        _check_scratch_fs
+       SCRATCH_DEV=$tmp
        [ $? -ne 0 ] && _fatal "fsck failed"
 
        _mount_flakey
-- 
1.7.7.6

<Prev in Thread] Current Thread [Next in Thread>