public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Rich Johnston <rjohnston@sgi.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: 311: fsck the dmflakey device instead of the real device V2
Date: Fri, 17 May 2013 07:00:32 -0500	[thread overview]
Message-ID: <51961BE0.2080708@sgi.com> (raw)
In-Reply-To: <20130516203035.GE1765@localhost.localdomain>

On 05/16/2013 03:30 PM, Josef Bacik wrote:
> On Thu, May 16, 2013 at 08:04:20AM -0600, Rich Johnston wrote:
>> On 05/15/2013 10:20 AM, Josef Bacik wrote:
>>> 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.  Make _check_scratch_fs take an optional argument to use as the device
>>> to fsck.  Thanks,
>>>
>>> Signed-off-by: Josef Bacik <jbacik@fusionio.com>
>>> ---
>> Hi Josef,
>>
>> Looks like it fails test 19 , are we supposed to see failures for ext4
>> and xfs?
>>
>
> Yeah that's what I was seeing, if you run the fsync tester without the reboot
> option and look at the file itself it should match the md5sum thats in the good
> output.  Thanks,
>
> Josef
>
Looks good.

Reviewed-by: Rich Johnston <rjohnston@sgi.com>

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

  reply	other threads:[~2013-05-17 11:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 15:20 [PATCH] xfstests: 311: fsck the dmflakey device instead of the real device V2 Josef Bacik
2013-05-15 21:32 ` Dave Chinner
2013-05-16 14:04 ` Rich Johnston
2013-05-16 20:30   ` Josef Bacik
2013-05-17 12:00     ` Rich Johnston [this message]
2013-05-17 12:02 ` Rich Johnston

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=51961BE0.2080708@sgi.com \
    --to=rjohnston@sgi.com \
    --cc=jbacik@fusionio.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