From: Tydus Ken <Tydus@Tydus.org>
To: xfs@oss.sgi.com
Subject: XFS on RAID5+LVM with scheduled capacity grow
Date: Thu, 07 Feb 2013 23:42:21 +0800 [thread overview]
Message-ID: <5113CB5D.40007@Tydus.org> (raw)
Hi list,
I'm new here, and also new to RAID.
I just bought a LSI RAID card and 3 new 2TB HDDs (together with 2 old
ones), and trying to build a RAID5 volume.
Because I don't have spare drives, I'm doing like this: use the 3 new
ones to build RAID5, then create a LVM VG on it as partition table, make
an XFS (as well as a BTRFS for profile and personal data) on it. Then
grow it to 5 drives use MegaCLi, do a vgextend, then xfs_growfs.
Now the question is, I cannot deside sw of XFS
(https://raid.wiki.kernel.org/index.php/RAID_setup#XFS). I think I
should use 4(5-1), but it has poor performance (~140MB/s while raw disk
write is ~250M). Is this all right? Or should I specify sunit and swidth
in the mount options? I don't really know the mechanic of XFS on this,
does this have effect on read?
Additionally, I want to know if this is the optimal method for me or
just use GPT? Maybe I will grow the array to more disks later.
Any help is appreciated.
Tydus Ken
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2013-02-07 15:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5113CB5D.40007@Tydus.org \
--to=tydus@tydus.org \
--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