From: Eric Sandeen <sandeen@sandeen.net>
To: aurfalien <aurfalien@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: specify agsize?
Date: Sat, 13 Jul 2013 21:13:01 -0500 [thread overview]
Message-ID: <51E2092D.7090409@sandeen.net> (raw)
In-Reply-To: <6A14EB72-A699-47AF-937D-D6DA1CF12ACB@gmail.com>
On 7/13/13 7:11 PM, aurfalien wrote:
> Hello again,
>
> I have a Raid 6 x16 disk array with 128k stripe size and a 512 byte block size.
>
> So I do;
>
> mkfs.xfs -f -l size=512m -d su=128k,sw=14 /dev/mapper/vg_doofus_data-lv_data
>
> And I get;
>
> meta-data=/dev/mapper/vg_doofus_data-lv_data isize=256 agcount=32, agsize=209428640 blks
> = sectsz=512 attr=2, projid32bit=0
> data = bsize=4096 blocks=6701716480, imaxpct=5
> = sunit=32 swidth=448 blks
> naming =version 2 bsize=4096 ascii-ci=0
> log =internal log bsize=4096 blocks=131072, version=2
> = sectsz=512 sunit=32 blks, lazy-count=1
> realtime =none extsz=4096 blocks=0, rtextents=0
>
>
> All is fine but I was recently made aware of tweaking agsize.
Made aware by what? For what reason?
> So I would like to mess around and iozone any diffs between the above
> agcount of 32 and whatever agcount changes I may do.
Unless iozone is your machine's normal workload, that will probably prove to be uninteresting.
> I didn't see any mention of agsize/agcount on the XFS FAQ and would
> like to know, based on the above, why does XFS think I have 32
> allocation groups with the corresponding size?
It doesn't think so, it _knows_ so, because it made them itself. ;)
> And are these optimal
> numbers?
How high is up?
Here's the appropriate faq entry:
http://xfs.org/index.php/XFS_FAQ#Q:_I_want_to_tune_my_XFS_filesystems_for_.3Csomething.3E
-Eric
> Thanks in advance,
>
> - aurf
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-07-14 2:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-14 0:11 specify agsize? aurfalien
2013-07-14 2:13 ` Eric Sandeen [this message]
2013-07-14 4:20 ` aurfalien
2013-07-14 7:06 ` Stan Hoeppner
2013-07-14 16:56 ` aurfalien
2013-07-15 1:07 ` Dave Chinner
2013-07-14 16:14 ` Eric Sandeen
2013-07-14 16:46 ` aurfalien
2013-07-14 17:14 ` aurfalien
2013-07-15 1:22 ` Dave Chinner
2013-07-14 22:08 ` Stan Hoeppner
2013-07-14 22:42 ` aurfalien
2013-07-14 23:43 ` Stan Hoeppner
-- strict thread matches above, loose matches on Subject: below --
2013-07-14 19:45 Richard Scobie
2013-07-14 22:18 ` aurfalien
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=51E2092D.7090409@sandeen.net \
--to=sandeen@sandeen.net \
--cc=aurfalien@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.