public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: xfs-oss <xfs@oss.sgi.com>
Subject: [PATCH] xfstests: fsck scratch device if it got used
Date: Thu, 29 Nov 2012 12:59:55 -0600	[thread overview]
Message-ID: <50B7B0AB.6040406@redhat.com> (raw)

This will cause the $SCRATCH_DEV to be fscked if it
was used in the prior test.  Without this I don't
think it gets done unless specifically requested
by the test.

Also recreate lost+found/ in one test so that e2fsck
doesn't complain.

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---

diff --git a/check b/check
index a4af0f6..343735a 100755
--- a/check
+++ b/check
@@ -308,6 +308,9 @@ do
 	try="$try $seq"
 	n_try=`expr $n_try + 1`
         _check_test_fs
+	if grep -q require_scratch $seq; then
+		_check_scratch_fs
+	fi
     fi
     
     seq="after_$seq"


diff --git a/062 b/062
index 9800e33..b727243 100755
--- a/062
+++ b/062
@@ -216,6 +216,9 @@ if [ $? -ne 0 ]; then
 	exit
 fi
 
+# So e2fsck won't complain:
+[[ $FSTYP = ext* ]] && mkdir $SCRATCH_MNT/lost+found
+
 # success, all done
 status=0
 exit


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2012-11-29 18:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29 18:59 Eric Sandeen [this message]
2012-11-30 16:06 ` [PATCH] xfstests: fsck scratch device if it got used Christoph Hellwig
2012-11-30 16:08   ` Eric Sandeen
2012-11-30 22:27     ` Dave Chinner
2012-11-30 22:29       ` Eric Sandeen
2012-12-03 14:03         ` Carlos Maiolino
2012-12-03 18:56           ` Eric Sandeen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50B7B0AB.6040406@redhat.com \
    --to=sandeen@redhat.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox