public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Ems <richard.ems@cape-horn-eng.com>
To: Richard Ems <richard.ems@cape-horn-eng.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: creating a new 80 TB XFS
Date: Mon, 01 Oct 2012 16:36:23 +0200	[thread overview]
Message-ID: <5069AA67.5040303@cape-horn-eng.com> (raw)
In-Reply-To: <5069A8A1.4080404@cape-horn-eng.com>

On 10/01/2012 04:28 PM, Richard Ems wrote:
> On 02/24/2012 04:17 PM, Eric Sandeen wrote:
>>> *MKFS*
>>>> We also heavily use ACLs for almost all of our files. Christoph Hellwig
>>>> suggested in a previous mail to use "-i size=512" on XFS creation, so my
>>>> mkfs.xfs would look something like:
>>>>
>>>> mkfs.xfs -i size=512 -d su=stripe_size,sw=28 -L Backup_2 /dev/sdX1
>> Be sure the stripe geometry matches the way the raid controller is
>> set up.
>>
>> You know the size of your acls, so you can probably do some testing
>> to find out how well 512-byte inodes keep ACLs in-line.
> 
> 
> Hi Eric,
> 
> This is a reply to an email from you sent 7 months ago ...
> 
> How could I do the testing you were proposing? How can I find out if my
> 512-byte inodes keep our ACLs in-line?
> 
> I am going to create a similar new RAID set, and wanted to check this
> before on the one already in production.
> 
> Thanks,
> Richard
> 

Hi again,

If the "method" is to use "xfs_bmap -a ..." and check for "no extents",
then I found it !

Thanks, sorry for the noise,
Richard

-- 
Richard Ems       mail: Richard.Ems@Cape-Horn-Eng.com

Cape Horn Engineering S.L.
C/ Dr. J.J. Dómine 1, 5º piso
46011 Valencia
Tel : +34 96 3242923 / Fax 924
http://www.cape-horn-eng.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-10-01 14:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 12:52 creating a new 80 TB XFS Richard Ems
2012-02-24 14:08 ` Emmanuel Florac
2012-02-24 15:43   ` Richard Ems
2012-02-24 16:20     ` Martin Steigerwald
2012-02-24 16:51       ` Stan Hoeppner
2012-02-25 10:59         ` Martin Steigerwald
2012-02-24 16:58     ` Roger Willcocks
2012-02-25 21:57     ` Peter Grandi
2012-02-26  2:57       ` Stan Hoeppner
2012-02-26 16:08         ` Emmanuel Florac
2012-02-26 16:55           ` Joe Landman
2012-02-24 14:52 ` Peter Grandi
2012-02-24 14:57 ` Michael Weissenbacher
2012-02-24 16:05   ` Richard Ems
2012-02-24 15:17 ` Eric Sandeen
2012-10-01 14:28   ` Richard Ems
2012-10-01 14:36     ` Richard Ems [this message]
2012-10-01 14:39     ` Eric Sandeen
2012-10-01 14:45       ` Richard Ems
2012-02-27 11:56 ` Michael Monnerie
2012-02-27 12:20   ` Richard Ems

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=5069AA67.5040303@cape-horn-eng.com \
    --to=richard.ems@cape-horn-eng.com \
    --cc=sandeen@sandeen.net \
    --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