public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] xfs/132: unmount scratch fs after test
@ 2018-05-21 16:06 Darrick J. Wong
  2018-05-21 22:51 ` Dave Chinner
  0 siblings, 1 reply; 2+ messages in thread
From: Darrick J. Wong @ 2018-05-21 16:06 UTC (permalink / raw)
  To: Eryu Guan; +Cc: fstests

From: Darrick J. Wong <darrick.wong@oracle.com>

If this test runs successfully, it'll leave a shutdown scratch fs
behind.  The test framework doesn't unmount the fs for us (because we
told it not to check the fs) so the test framework tries to "test -d
$SCRATCH_MNT" and blows up on the IO error it receives from the dead fs.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
---
 tests/xfs/132 |    1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/xfs/132 b/tests/xfs/132
index 6bb03e79..3fa695a7 100755
--- a/tests/xfs/132
+++ b/tests/xfs/132
@@ -67,6 +67,7 @@ _scratch_mount
 
 # The corrupt inode should be tripped over during these initial file creates.
 touch $SCRATCH_MNT/file{0,1,2,3,4,5}{0,1,2,3,4,5} 2>&1 | _filter_scratch
+_scratch_unmount
 
 # success, all done
 status=0

^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] xfs/132: unmount scratch fs after test
  2018-05-21 16:06 [PATCH] xfs/132: unmount scratch fs after test Darrick J. Wong
@ 2018-05-21 22:51 ` Dave Chinner
  0 siblings, 0 replies; 2+ messages in thread
From: Dave Chinner @ 2018-05-21 22:51 UTC (permalink / raw)
  To: Darrick J. Wong; +Cc: Eryu Guan, fstests

On Mon, May 21, 2018 at 09:06:48AM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
> 
> If this test runs successfully, it'll leave a shutdown scratch fs
> behind.  The test framework doesn't unmount the fs for us (because we
> told it not to check the fs) so the test framework tries to "test -d
> $SCRATCH_MNT" and blows up on the IO error it receives from the dead fs.
> 
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
>  tests/xfs/132 |    1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/tests/xfs/132 b/tests/xfs/132
> index 6bb03e79..3fa695a7 100755
> --- a/tests/xfs/132
> +++ b/tests/xfs/132
> @@ -67,6 +67,7 @@ _scratch_mount
>  
>  # The corrupt inode should be tripped over during these initial file creates.
>  touch $SCRATCH_MNT/file{0,1,2,3,4,5}{0,1,2,3,4,5} 2>&1 | _filter_scratch
> +_scratch_unmount

I've already NAK'd that patch - the test harness should be
unmounting scratch in all situations and returning the test harness
to a known initial state before the next test runs...

Cheers,

Dave.

-- 
Dave Chinner
david@fromorbit.com

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-05-21 22:51 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-05-21 16:06 [PATCH] xfs/132: unmount scratch fs after test Darrick J. Wong
2018-05-21 22:51 ` Dave Chinner

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox