From: pg_xf2@xf2.for.sabi.co.UK (Peter Grandi)
To: Linux fs XFS <xfs@oss.sgi.com>
Subject: Re: Optimal XFS formatting options?
Date: Fri, 20 Jan 2012 12:06:31 +0000 [thread overview]
Message-ID: <20249.22727.359884.733592@tree.ty.sabi.co.UK> (raw)
In-Reply-To: <4F192DEC.4030400@tlinx.org>
[ ... ]
>> * XFS has several limitations on 32b kernels. Just make sure
>> you have a 64b kernel.
[ ... ]
> I was unaware that the block size was larger on 64b kernels.
> Is that what you are referring to ? (would be nice)...
Not as such, the maximum block size is limited by the Linux page
cache, that is hw page size, which is for IA32 and AMD64
architectures the same at 4KiB. However other architectures
which are natively 64b allow bigger page sizes (notably IA64
[aka Itanium]), so the page cache and thus XFS can do larger
blocks sizes.
The limitations of XFS on 32b kernels come from limitations of
XFS itself in 32b mode, limitations of Linux in 32b mode, and
combined limitations. For example:
* There be 32b inode numbers, which limit inodes to the first
1TB of a filetree if sector size is 512B.
* The 32b block IO subsystems limits partition sizes to 16TiB.
* XFS tools scanning a large filesystem, usually for repair,
can run out of the available 32b address space (by default
around 2GiB).
Page 5 and 6 here list some limits:
http://oss.sgi.com/projects/xfs/training/xfs_slides_02_overview.pdf
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-01-20 12:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 17:44 Optimal XFS formatting options? MikeJeezy
2012-01-14 22:23 ` Stan Hoeppner
2012-01-16 0:27 ` MikeJeezy
2012-01-16 4:56 ` Stan Hoeppner
2012-01-16 23:11 ` Dave Chinner
2012-01-17 3:31 ` Stan Hoeppner
2012-01-17 9:19 ` Michael Monnerie
2012-01-17 11:17 ` Emmanuel Florac
2012-01-17 11:34 ` Stan Hoeppner
2012-01-20 15:52 ` Michael Monnerie
2012-01-20 22:44 ` Stan Hoeppner
2012-01-24 10:31 ` Michael Monnerie
2012-01-15 1:14 ` Peter Grandi
2012-01-20 9:03 ` Linda Walsh
2012-01-20 12:06 ` Peter Grandi [this message]
2012-01-20 15:55 ` Michael Monnerie
2012-01-23 4:21 ` 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=20249.22727.359884.733592@tree.ty.sabi.co.UK \
--to=pg_xf2@xf2.for.sabi.co.uk \
--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