On Tue, Sep 17, 2013 at 08:51:09AM -0500, Mark Tinguely wrote:
> On 09/16/13 20:04, Dave Chinner wrote:
> >On Wed, Sep 11, 2013 at 09:21:59AM -0700, Christoph Hellwig wrote:
> >>On Tue, Sep 10, 2013 at 01:35:47AM +1000, Dave Chinner wrote:
> >>>The test matrix of having to test everything on v4 and v5 is just
> >>>nasty, especially if we are talking about prototyping code. I'd much
> >>>prefer to bring things to v5 filesytsems where we have much lower
> >>>exposure and risk of corruption problems, and then when we know it's
> >>>solid because of the QA we've done on it, then we can expose the
> >>>majority of the XFS userbase to it by bringing it back to v4
> >>I think the test matrix is a reason for not enabling this only on v5
> We are *not* screaming for this on v4. Not screaming for this to be
> mandatory on v5.
> It will make inode allocation more difficult as the drive fragments.
Yes. But we have a plan to solve that:
And this work follows directly after Brian's free inode btree
patches. i.e. you need to consider this patch in the context of the
architectural modifications to inode allocation that have been
posted for discussion, not as an isolated, random change.
As I've mentioned in the past, I publish design documentation so
that everyone knows what goals we're working towards and the steps
being taking to get there. This is just a small piece in that