From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: 4K drives, sectsz=512, bsize=4096
Date: Wed, 1 Sep 2010 09:38:46 +0200 [thread overview]
Message-ID: <201009010938.51894@zmi.at> (raw)
In-Reply-To: <881036.47658.qm@web76207.mail.sg1.yahoo.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 720 bytes --]
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?
--
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/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-01 7:38 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 [this message]
2010-09-01 10:13 ` Christoph Hellwig
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=201009010938.51894@zmi.at \
--to=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