From: Dave Chinner <david@fromorbit.com>
To: Mark Tinguely <tinguely@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH] [RFC] xfs: increase inode cluster size for v5 filesystems
Date: Wed, 18 Sep 2013 07:25:02 +1000 [thread overview]
Message-ID: <20130917212502.GJ19103@dastard> (raw)
In-Reply-To: <52385E4D.4040007@sgi.com>
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
> >>>filesystems.
> >>
> >>I think the test matrix is a reason for not enabling this only on v5
> >>filesystems.
....
> 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:
http://oss.sgi.com/archives/xfs/2013-08/msg00346.html
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
puzzle.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-09-17 21:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 8:34 [PATCH] [RFC] xfs: increase inode cluster size for v5 filesystems Dave Chinner
2013-09-09 13:32 ` Christoph Hellwig
2013-09-09 13:54 ` Eric Sandeen
2013-09-09 15:35 ` Dave Chinner
2013-09-11 16:21 ` Christoph Hellwig
2013-09-17 1:04 ` Dave Chinner
2013-09-17 13:51 ` Mark Tinguely
2013-09-17 21:25 ` Dave Chinner [this message]
2013-09-17 14:46 ` Eric Sandeen
2013-09-17 21:11 ` Dave Chinner
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=20130917212502.GJ19103@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=tinguely@sgi.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