From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: sunit/swidth for HP P4500 Lefthand Networks storage arrays
Date: Wed, 11 Jan 2012 22:15:47 -0600 [thread overview]
Message-ID: <4F0E5E73.9070308@hardwarefreak.com> (raw)
The Linux host will be Debian Squeeze with a very recent BPO kernel, but
running as a guest inside a VMware cluster. The storage platform is a
dozen clustered HP P4500/Lefthand Networks "self load balancing" iSCSI
arrays. The application is Dovecot IMAP using the mdbox mailbox storage
format, which is basically a hybrid mbox/maildir+dedup format. Files
will be 32-64MB or so, each containing multiple emails, with multiple
files per mailbox directory. Mail indexes are internal to the files.
What is the best mkfs.xfs configuration for this scenario?
I'm guessing it would be best to simply use mostly, if not completely,
the defaults, due to the way iSCSI packets are redirected on the fly to
any storage node depending on load, by the Lefthand special sauce.
What about mount options?
Should I use barriers with the P4500s or disable them?
TTBOMK the internal PCIe RAID controllers have BBWC, but the ~6GB of RAM
on the P4500 mobos isn't battery backed, but for the typical external
UPS. In this setup, from a physical hardware standpoint, iSCSI packets
will be making at least 2 ethernet switch hops between the ESX nodes and
the P4500s, with redundant links between everything, if that's a factor
at all.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-01-12 4:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 4:15 Stan Hoeppner [this message]
2012-01-12 7:30 ` sunit/swidth for HP P4500 Lefthand Networks storage arrays Michael Monnerie
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=4F0E5E73.9070308@hardwarefreak.com \
--to=stan@hardwarefreak.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