From: Stan Hoeppner <stan@hardwarefreak.com>
To: Paul Anderson <pha@umich.edu>
Cc: linux-xfs@oss.sgi.com, Marcus Pereira <marcus@task.com.br>,
Eric Sandeen <sandeen@sandeen.net>
Subject: Re: mkfs.xfs error creating large agcount an raid
Date: Mon, 27 Jun 2011 15:55:26 -0500 [thread overview]
Message-ID: <4E08EE3E.1090604@hardwarefreak.com> (raw)
In-Reply-To: <BANLkTikJe7ayzwD2Yqc7BHePfZ4x-M_SyQ@mail.gmail.com>
On 6/27/2011 10:27 AM, Paul Anderson wrote:
> There is nothing in the man page I see indicating what is good or bad
> regarding allocation groups - either document it there or warn in the
> software. If allocation algorithms are linear with respect to
> allocation groups, the something like this should be stated in the man
> pages.
It is. From the 2nd paragraph of 'man 5 xfs':
...The data section is divided into a number of allocation groups. The
number and size of the allocation groups are chosen by mkfs.xfs(8) so
that there is normally a small number of equal-sized groups. The number
of allocation groups controls the amount of parallelism available in
file and block allocation. It should be increased from the default if
there is sufficient memory and a lot of allocation activity. The number
of allocation groups should not be set very high, since this can cause
large amounts of CPU time to be used by the filesystem, especially when
the filesystem is nearly full. More allocation groups are added (of the
original size) when xfs_growfs(8) is run.
Maybe some of this information could/should be moved to the agcount
section of 'man mkfs.xfs'. I'll concede that "should not be set very
high" is subjective for novice XFS users. To Marcus 20,000 may not be
"very high". :)
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-06-27 20:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-25 19:49 mkfs.xfs error creating large agcount an raid Marcus Pereira
2011-06-26 2:09 ` Stan Hoeppner
2011-06-26 5:53 ` Marcus Pereira
2011-06-26 21:26 ` Stan Hoeppner
2011-06-26 23:29 ` Stan Hoeppner
2011-06-26 23:59 ` Dave Chinner
2011-06-27 3:33 ` Stan Hoeppner
2011-06-27 4:14 ` Marcus Pereira
2011-06-27 8:55 ` Stan Hoeppner
2011-06-27 13:04 ` Paul Anderson
2011-06-27 15:10 ` Eric Sandeen
2011-06-27 15:27 ` Paul Anderson
2011-06-27 15:37 ` Eric Sandeen
2011-06-27 20:55 ` Stan Hoeppner [this message]
2011-06-28 1:22 ` 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=4E08EE3E.1090604@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-xfs@oss.sgi.com \
--cc=marcus@task.com.br \
--cc=pha@umich.edu \
--cc=sandeen@sandeen.net \
/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