From: Richard Ems <richard.ems@cape-horn-eng.com>
To: xfs@oss.sgi.com
Subject: creating a new 80 TB XFS
Date: Fri, 24 Feb 2012 13:52:40 +0100 [thread overview]
Message-ID: <4F478818.4050803@cape-horn-eng.com> (raw)
Hi list,
I am not a storage expert, so sorry in advance for probably some *naive*
questions or proposals from me. 8)
*INTRO*
We are getting new hardware soon and I wanted to check with you my plans
for creating and mounting this XFS.
The storage system is from EUROstor,
http://eurostor.com/en/products/raid-sas-host/es-6600-sassas-toploader.html
.
We are getting now 32 x 3 TB Hitachi SATA HDDs.
I plan to configure them in a single RAID 6 set with one or two
hot-standby discs. The raw storage space will then be 28 x 3 TB = 84 TB.
On this one RAID set I will create only one volume.
Any thoughts on this?
This storage will be used as secondary storage for backups. We use
dirvish (www.dirvish.org, which uses rsync) to run our daily backups.
dirvish heavily uses hard links. It compares all files, one by one, and
synchronizes all new or changed files with rsync to the current daily
dir YYYY-MM-DD, and creates hard links for all not changed files from
the last previous backup on YYYY-MM-(DD-1) to the current YYYY-MM-DD
directory.
*MKFS*
We also heavily use ACLs for almost all of our files. Christoph Hellwig
suggested in a previous mail to use "-i size=512" on XFS creation, so my
mkfs.xfs would look something like:
mkfs.xfs -i size=512 -d su=stripe_size,sw=28 -L Backup_2 /dev/sdX1
*MOUNT*
On mount I will use the options
mount -o noatime,nobarrier,nofail,logbufs=8,logbsize=256k,inode64
/dev/sdX1 /mount_point
What about the largeio mount option? In which cases would it be useful?
Do you have any other/better suggestions or comments?
Many thanks,
Richard
--
Richard Ems mail: Richard.Ems@Cape-Horn-Eng.com
Cape Horn Engineering S.L.
C/ Dr. J.J. Dómine 1, 5º piso
46011 Valencia
Tel : +34 96 3242923 / Fax 924
http://www.cape-horn-eng.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-02-24 12:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 12:52 Richard Ems [this message]
2012-02-24 14:08 ` creating a new 80 TB XFS Emmanuel Florac
2012-02-24 15:43 ` Richard Ems
2012-02-24 16:20 ` Martin Steigerwald
2012-02-24 16:51 ` Stan Hoeppner
2012-02-25 10:59 ` Martin Steigerwald
2012-02-24 16:58 ` Roger Willcocks
2012-02-25 21:57 ` Peter Grandi
2012-02-26 2:57 ` Stan Hoeppner
2012-02-26 16:08 ` Emmanuel Florac
2012-02-26 16:55 ` Joe Landman
2012-02-24 14:52 ` Peter Grandi
2012-02-24 14:57 ` Michael Weissenbacher
2012-02-24 16:05 ` Richard Ems
2012-02-24 15:17 ` Eric Sandeen
2012-10-01 14:28 ` Richard Ems
2012-10-01 14:36 ` Richard Ems
2012-10-01 14:39 ` Eric Sandeen
2012-10-01 14:45 ` Richard Ems
2012-02-27 11:56 ` Michael Monnerie
2012-02-27 12:20 ` Richard Ems
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=4F478818.4050803@cape-horn-eng.com \
--to=richard.ems@cape-horn-eng.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox