From: Christoph Hellwig <hch@infradead.org>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: 4K drives, sectsz=512, bsize=4096
Date: Wed, 1 Sep 2010 06:13:36 -0400 [thread overview]
Message-ID: <20100901101336.GA31648@infradead.org> (raw)
In-Reply-To: <201009010938.51894@zmi.at>
On Wed, Sep 01, 2010 at 09:38:46AM +0200, Michael Monnerie wrote:
> On Mittwoch, 1. September 2010 Gim Leong Chin wrote:
> > Should we leave it at the default 256 bytes, or set it to the maximum
> > of 2 kB?
>
> An interesting question. Why are inodes sizes configurable at all? To
> store ACLs? How would one know when bigger Inodes should be used? And
> what is the implication when they would be needed but aren't used?
The XFS inode consists of three parts:
- the fixed format dinode
- the data fork
- the attribute fork
the fixed format inode is fixed size, so any change in the inode size
only applies to the data and attribute forks. For regular files we
generally don't use much space in the data fork as it just contains
the extent list, and most files have rather few of them. But we can
also store short smbolic links directly inside it, as well as the
content of directories. The attribute fork is used to store extent
attributes and if it's large enough we can store them inline instead
of using external blocks.
You want large inodes mostly if you store lots of extentded attributes,
either for ACLs, Selinux or posisbly DMAPI. It will also help if you
have enough directories that are just too big for the inline directory
format with smaller inode sizes.
>
> --
> mit freundlichen Gr?ssen,
> Michael Monnerie, Ing. BSc
>
> it-management Internet Services
> http://proteger.at [gesprochen: Prot-e-schee]
> Tel: 0660 / 415 65 31
>
> ****** Aktuelles Radiointerview! ******
> http://www.it-podcast.at/aktuelle-sendung.html
>
> // Wir haben im Moment zwei H?user zu verkaufen:
> // http://zmi.at/langegg/
> // http://zmi.at/haus2009/
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
---end quoted text---
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-01 10:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 7:56 4K drives, sectsz=512, bsize=4096 Michael Monnerie
2010-08-31 21:01 ` Michael Monnerie
2010-08-31 21:16 ` Eric Sandeen
2010-08-31 22:07 ` Michael Monnerie
2010-08-31 22:15 ` Eric Sandeen
2010-08-31 23:12 ` Michael Monnerie
2010-08-31 22:34 ` Nathan Scott
2010-09-01 5:35 ` Gim Leong Chin
2010-09-01 5:59 ` Nathan Scott
2010-09-01 7:38 ` Michael Monnerie
2010-09-01 10:13 ` Christoph Hellwig [this message]
2010-09-01 10:24 ` Christoph Hellwig
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=20100901101336.GA31648@infradead.org \
--to=hch@infradead.org \
--cc=michael.monnerie@is.it-management.at \
--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