xfs
[Top] [All Lists]

Re: [PATCH] xfs/030: link .out file according to reflink support status

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: [PATCH] xfs/030: link .out file according to reflink support status
From: Eryu Guan <eguan@xxxxxxxxxx>
Date: Thu, 31 Mar 2016 13:56:59 +0800
Cc: xfs@xxxxxxxxxxx, fstests@xxxxxxxxxxxxxxx, darrick.wong@xxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20160331042644.GK30721@dastard>
References: <1459331861-15025-1-git-send-email-eguan@xxxxxxxxxx> <20160331042644.GK30721@dastard>
User-agent: Mutt/1.5.24 (2015-08-30)
On Thu, Mar 31, 2016 at 03:26:44PM +1100, Dave Chinner wrote:
> On Wed, Mar 30, 2016 at 05:57:41PM +0800, Eryu Guan wrote:
> > Commit 31f48569c353 ("xfs/030: fix output on newer filesystems") added
> > more lines to .out file to match the output from XFS with reflink
> > support, but it broke test on older XFS.
> > 
> > Fix it by introducing new .out file 030.out.reflink.linux to match the
> > reflink case, so old XFS still compares .out file against 030.out.linux.
> > 
> > In order to do this, a new helper is introduced, _fs_has_reflink()
> > accepts mount point as argument and returns if the underlying fs
> > supports reflink or not.
> 
> Let's not go down this path. This is a filtering issue, not a
> problem we solve by playing "let's add a golden image file for every
> different filesystem format we can create".
> 
> The problem here is that reflink triggers a change in the initial
> population of the AGFL - from 4 blocks to 6 blocks, and so repair
> warns 6 times instead of 4. After filtering, that gives 6 indentical
> output lines instead of 4.
> 
> Doing something as simple as collapsing repeated identical lines
> (e.g filtering through uniq) will work for all filesystem formats
> and any future changes that modify the initial AGFL population...

I thought about filtering at first, but didn't find a way to filter out
the extra two lines easily. Collapsing repeaded lines into one will do.
I'll send out v2 shortly. Thanks for reviewing!

Eryu

<Prev in Thread] Current Thread [Next in Thread>