On 9/16/14 8:41 PM, Dave Chinner wrote: > From: Dave Chinner <dchinner@xxxxxxxxxx> > > xfs/200 leaves a dirty log as readonly filesystems don't write > unmount records to mark the log clean. I wonder if it'd be better to just add a case that sets it RW again and mounts/unmounts it, so we *can* check it after these gyrations? But if for some reason you don't want to change the existing test, this is probably ok too; if so, Reviewed-by: Eric Sandeen <sandeen@xxxxxxxxxx> > Signed-off-by: Dave Chinner <dchinner@xxxxxxxxxx> > --- > tests/xfs/200 | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/tests/xfs/200 b/tests/xfs/200 > index f4db64f..f0c4337 100755 > --- a/tests/xfs/200 > +++ b/tests/xfs/200 > @@ -44,7 +44,7 @@ trap "_cleanup; exit \$status" 0 1 2 3 15 > _supported_fs xfs > _supported_os Linux > > -_require_scratch > +_require_scratch_nocheck > > _scratch_mkfs_xfs >/dev/null 2>&1 > > -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
