From: Eric Sandeen <sandeen@sandeen.net>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>, xfs@oss.sgi.com
Subject: Re: Anyone using XFS in production on > 20TiB volumes?
Date: Wed, 22 Dec 2010 13:03:13 -0600 [thread overview]
Message-ID: <4D124B71.9030401@sandeen.net> (raw)
In-Reply-To: <20101222175611.1c7d5190@harpe.intellique.com>
On 12/22/10 10:56 AM, Emmanuel Florac wrote:
> Le Wed, 22 Dec 2010 11:30:05 -0500 (EST)
> Justin Piszcz <jpiszcz@lucidpixels.com> écrivait:
>
>> Is there anyone currently using this in production?
>
> Yup, lots of people do. Currently supporting 28 such systems (from 20
> to 76 TiB, most are 39.7 TiB).
>
>> How much ram is needed when you fsck with a many files on such a
>> volume? Dave Chinner reported 5.5g or so is needed for ~43TB with no
>> inodes. Any recent issues/bugs one needs to be aware of?
>
> I never had any trouble running xfs_repair on 39.7 TB+ systems with 8 GB
> of RAM.
>
>> Is inode64 recommended on a 64-bit system?
>
> Sure, however 32 bits clients may scoff sometimes, though it's limited
> to some weird programs.
>
>> Any specific 64-bit tweaks/etc for a large 43TiB FS?
>>
>
> Nothing unusual (inode64,noatime, mkfs with lazy-count enabled, etc). It
> should just works.
yes, inode64 is recommended for such a large filesystem; lazy-count
has been default in mkfs for quite some time. noatime if you really
need it, I guess.
See also
http://xfs.org/index.php/XFS_FAQ#Q:_I_want_to_tune_my_XFS_filesystems_for_.3Csomething.3E
which mentions getting your geometry right if it's hardware raid
that can't be detected automatically.
(maybe we should add inode64 usecases to that too...)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-12-22 19:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 16:30 Anyone using XFS in production on > 20TiB volumes? Justin Piszcz
2010-12-22 16:56 ` Emmanuel Florac
2010-12-22 19:03 ` Eric Sandeen [this message]
2010-12-23 0:26 ` Emmanuel Florac
2010-12-23 0:28 ` Justin Piszcz
2010-12-23 0:56 ` Dave Chinner
2010-12-23 9:43 ` Justin Piszcz
2010-12-23 12:03 ` Emmanuel Florac
2010-12-23 18:06 ` Justin Piszcz
2010-12-23 18:55 ` Emmanuel Florac
2010-12-23 19:07 ` Justin Piszcz
2010-12-23 19:54 ` Stan Hoeppner
2010-12-23 21:48 ` Emmanuel Florac
2010-12-23 23:21 ` Stan Hoeppner
2010-12-23 21:50 ` Emmanuel Florac
2010-12-23 22:04 ` Justin Piszcz
2010-12-23 19:29 ` Justin Piszcz
2010-12-23 19:58 ` Stan Hoeppner
2010-12-24 1:01 ` Stan Hoeppner
2010-12-23 21:12 ` Eric Sandeen
2010-12-23 1:10 ` Emmanuel Florac
2010-12-22 17:06 ` Chris Wedgwood
2010-12-22 17:10 ` Justin Piszcz
2010-12-22 17:32 ` Chris Wedgwood
2010-12-22 17:35 ` Justin Piszcz
2010-12-22 18:50 ` Chris Wedgwood
2010-12-22 19:24 ` Justin Piszcz
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=4D124B71.9030401@sandeen.net \
--to=sandeen@sandeen.net \
--cc=eflorac@intellique.com \
--cc=jpiszcz@lucidpixels.com \
--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