From: Krzysztof Adamski <k@adamski.org>
To: linux-fsdevel@vger.kernel.org
Subject: Looking for advice on creating XFS on a large (to me) RAID
Date: Thu, 03 Nov 2011 12:29:58 -0400 [thread overview]
Message-ID: <1320337798.6471.89.camel@oxygen.netxsys.com> (raw)
Hi All,
I'm about to create a XFS file system on a MD RAID6 made up of 12 3T
drives.
This is the command line that I was planning to use:
# mkfs.xfs -l lazy-count=1 -s size=4096 -N /dev/md7
= sectsz=4096 attr=2, projid32bit=0
data = bsize=4096 blocks=7320776704,imaxpct=5
= sunit=128 swidth=1280 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal log bsize=4096 blocks=521728, version=2
= sectsz=4096 sunit=1 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
This is the MD examine for one of the drives:
Nitrogen:~# mdadm -E /dev/sda2
/dev/sda2:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : ee8cb70e:2f40f34f:79d46ade:4b12c78b
Creation Time : Tue Nov 1 17:03:38 2011
Raid Level : raid6
Raid Devices : 12
Avail Dev Size : 5856624640 (2792.66 GiB 2998.59 GB)
Array Size : 58566236160 (27926.56 GiB 29985.91 GB)
Used Dev Size : 5856623616 (2792.66 GiB 2998.59 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 72fa45ca:775f244d:15b030fe:f569fe8c
Internal Bitmap : 8 sectors from superblock
Update Time : Thu Nov 3 11:07:39 2011
Checksum : 4c72bfd4 - correct
Events : 11029
Layout : left-symmetric
Chunk Size : 512K
Device Role : Active device 0
Array State : AAAAAAAAAAAA ('A' == active, '.' == missing)
# mkfs.xfs -V
mkfs.xfs version 3.1.4
System is Debian Squeeze with self compiled 3.0.8 kernel (64bit)
Should I change any default parameters to mkfs.xfs
If I didn't provide any important info let me know.
Thanks in advance,
K
next reply other threads:[~2011-11-03 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 16:29 Krzysztof Adamski [this message]
2011-11-03 17:14 ` Looking for advice on creating XFS on a large (to me) RAID Christoph Hellwig
2011-11-03 17:45 ` Krzysztof Adamski
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=1320337798.6471.89.camel@oxygen.netxsys.com \
--to=k@adamski.org \
--cc=linux-fsdevel@vger.kernel.org \
/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.