From: Stan Hoeppner <stan@hardwarefreak.com>
To: Roberto Spadim <roberto@spadim.com.br>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Help creating filesystem (xfs) and partitioning
Date: Wed, 24 Jul 2013 01:56:34 -0500 [thread overview]
Message-ID: <51EF7AA2.9000604@hardwarefreak.com> (raw)
In-Reply-To: <CAH3kUhFqX5fB0=eYbECxrR_52Yv3_v5oodG=6Z-8L_gcTwiC4Q@mail.gmail.com>
On 7/23/2013 7:06 PM, Roberto Spadim wrote:
> /boot with 200mb, xfs filesystem and raid1
Using a journaling filesystem for /boot is pointless. Use EXT2 instead.
> swap with 20gb (or 10gb),
> / with 100gb, xfs filesystem and raid1
> /home with all disk left (near to 400gb), xfs filesystem and raid1
It is ill advised to put more than one XFS filesystem on a single
(effective) spindle which is what RAID1 is. Doing so results in too
many allocation groups, which results in head thrashing, which results
in decreased performance. Use a single XFS for rootfs and home, manage
space by enabling and setting quotas.
...
> Now the point is, what's the best fdisk, mdadm, mkfs_xfs, tunefs,
> smartctl and others tune tools and /sys /proc parameters?
> I want a good align and performace
None of these will increase your performance with a RAID1 pair.
Switching your elevator from CFQ to deadline, and making sure NCQ is
enabled and working properly, is about the best you can do to maximize
md RAID1 performance. And using a single XFS as I described above,
instead of 2 or 3.
If your workload(s) involve heavy mixed metadata and data changes, i.e.
untar a kernel tarball then delete the directory tree, then mounting
with inode64 will improve performance a bit. inode64 has been made the
default XFS allocator but I'm not sure with which kernel version that
took affect. To find out simply do "cat /proc/mounts".
See mkfs.xfs(8), mount(8)
http://xfs.org/index.php/XFS_FAQ
http://xfs.org/docs/xfsdocs-xml-dev/XFS_Labs/tmp/en-US/html/xfs-quotas-lab.html
--
Stan
next prev parent reply other threads:[~2013-07-24 6:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 0:06 Help creating filesystem (xfs) and partitioning Roberto Spadim
2013-07-24 6:56 ` Stan Hoeppner [this message]
[not found] ` <CAH3kUhHoQiyhVotNpNDq-rcQ36vZbRrZvoEsUzyo0=9mz8=+3w@mail.gmail.com>
2013-07-24 17:28 ` Stan Hoeppner
[not found] ` <CAH3kUhEZLBZD79WW75gWF4a5dvhQas=1+oR6vaTbuNtTBRfayg@mail.gmail.com>
2013-07-24 19:35 ` Stan Hoeppner
2013-07-24 19:41 ` Mark Knecht
2013-07-25 2:34 ` Roberto Spadim
2013-07-25 21:52 ` Bill Davidsen
2013-07-25 22:36 ` Roberto Spadim
2013-07-25 23:27 ` Stan Hoeppner
2013-07-26 0:36 ` Roberto Spadim
2013-07-26 1:30 ` Stan Hoeppner
2013-07-26 1:47 ` Roberto Spadim
2013-07-26 16:15 ` Stan Hoeppner
2013-07-26 16:47 ` Roberto Spadim
2013-07-28 22:46 ` Bill Davidsen
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=51EF7AA2.9000604@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@vger.kernel.org \
--cc=roberto@spadim.com.br \
/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;
as well as URLs for NNTP newsgroup(s).