linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: linux-fsdevel@vger.kernel.org
Subject: Default ext inode size
Date: Thu, 13 Nov 2008 14:56:38 -0500	[thread overview]
Message-ID: <491C8676.8000209@cfl.rr.com> (raw)

I noticed that the default inode size for mkfs in e2fsprogs has been 
changed to 256 bytes.  I noticed this because I am seeing users complain 
that they can no longer access their ext partitions using the windows 
driver, which only supports normal 128 byte inodes.  I'd like to know 
why this default was changed.

As I understand it, the larger inode size means that ea/acl can be 
stored directly in the inode.  Are there any other benefits?  It seems 
that using extended attributes is rather uncommon in the first place, 
and that when they are used, many files often share them so it would be 
better to leave them in the shared data block rather than duplicate them 
in every inode.  This leaves me wondering where is the common case that 
benefits from a larger default inode?

             reply	other threads:[~2008-11-13 20:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13 19:56 Phillip Susi [this message]
2008-11-13 20:14 ` Default ext inode size Kalpak Shah
2008-11-13 20:21 ` Theodore Tso
2008-11-13 20:50   ` Phillip Susi
2008-11-13 21:35     ` Theodore Tso

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=491C8676.8000209@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=linux-fsdevel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).