From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] [RFC] xfs: increase inode cluster size for v5 filesystems
Date: Mon, 09 Sep 2013 08:54:41 -0500 [thread overview]
Message-ID: <522DD321.1010201@sandeen.net> (raw)
In-Reply-To: <20130909133254.GA14778@infradead.org>
On 9/9/13 8:32 AM, Christoph Hellwig wrote:
> I can't see anything v5 format specific here, as 512 byte inodes can be
> created with v4 filesystems as well.
Good point - why is this uniquely needed for V5 filesystems?
If it wasn't a problem w/ larger inodes before, why is it now?
This makes the dreaded test matrix go a bit more wonky...
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-09-09 13:54 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 [this message]
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
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=522DD321.1010201@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hch@infradead.org \
--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