[PATCH] xfstests: 311: fsck the dmflakey device instead of the real device V2

Rich Johnston rjohnston at sgi.com
Fri May 17 07:00:32 CDT 2013


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 at 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 at sgi.com>



More information about the xfs mailing list