[Top] [All Lists]

Re: xfstest failures

To: Mark Tinguely <tinguely@xxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: xfstest failures
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Thu, 07 Nov 2013 07:58:24 -0600
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <527B94A5.20004@xxxxxxx>
References: <20131106105451.GA31283@xxxxxxxxxxxxx> <20131106194417.GF6188@dastard> <527A9F67.6000208@xxxxxxx> <20131107081634.GB25157@xxxxxxxxxxxxx> <527B94A5.20004@xxxxxxx>
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
On 11/7/13, 7:24 AM, Mark Tinguely wrote:
> On 11/07/13 02:16, Christoph Hellwig wrote:
>> On Wed, Nov 06, 2013 at 01:58:31PM -0600, Mark Tinguely wrote:
>>>>> xfs/206
>>>>>     Does not expect the ftype flag.  Didn't we change a generic
>>>>>     filter to take care of this?
>>>> xfs/206 has it's own mkfs filter:
>>>> http://oss.sgi.com/archives/xfs/2013-10/msg00777.html
>> And why is this patch not merged?
> It was never reviewed.

Nor was xfstests: filter projid32bit info out of growfs & info output
which I sent originally, before the ftype stuff went in.

Nor was xfstests: New _require_* tests for CRC enabled filesystems which
Dave sent back in June, which Dave alluded to as fixing this as well.
I circled back to it in October w/ a suggestion but haven't seen a

This lag is clearly causing headaches for all of us; let's just take
a deep breath & get these taken care of.

We had a really high rate of change there for a while, and keeping up on
all fronts was tough.

There's been a bit of defensiveness in the replies here; let's get past
that & take Christoph's list of failures and just get them taken care of.

I'll try to go through the failures and either pick up existing patches,
or get new ones written, and get a new series on the list to get this all
cleaned up.


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