From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: fsck scratch device if it got used
Date: Fri, 30 Nov 2012 11:06:16 -0500 [thread overview]
Message-ID: <20121130160616.GD5667@infradead.org> (raw)
In-Reply-To: <50B7B0AB.6040406@redhat.com>
On Thu, Nov 29, 2012 at 12:59:55PM -0600, Eric Sandeen wrote:
> 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.
This one looks good.
> Also recreate lost+found/ in one test so that e2fsck
> doesn't complain.
This one I can't make any sense of. Care to send it separately with a
good explanation?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-11-30 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 18:59 [PATCH] xfstests: fsck scratch device if it got used Eric Sandeen
2012-11-30 16:06 ` Christoph Hellwig [this message]
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=20121130160616.GD5667@infradead.org \
--to=hch@infradead.org \
--cc=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