From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: stan@hardwarefreak.com
Cc: xfs@oss.sgi.com
Subject: Re: sunit/swidth for HP P4500 Lefthand Networks storage arrays
Date: Thu, 12 Jan 2012 08:30:56 +0100 [thread overview]
Message-ID: <201201120830.56858@zmi.at> (raw)
In-Reply-To: <4F0E5E73.9070308@hardwarefreak.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 1478 bytes --]
On Donnerstag, 12. Januar 2012 Stan Hoeppner wrote:
> 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.
I'd use defaults. We've recently switched to a NetApp storage, and with
all the specialities it has also use the defaults.
> 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.
Turn off barriers, I'd say. We use the NetApp over NFS (to VMware
stores), and turned them off. I guess that's also correct to do.
As I understand them, barriers help to not loose blocks which the
storage already received, so it doesn't matter how it's connected
because the packets must have arrived there already. Can someone
confirm?
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services: Protéger
http://proteger.at [gesprochen: Prot-e-schee]
Tel: +43 660 / 415 6531
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-01-12 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 4:15 sunit/swidth for HP P4500 Lefthand Networks storage arrays Stan Hoeppner
2012-01-12 7:30 ` Michael Monnerie [this message]
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=201201120830.56858@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=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