From: Stan Hoeppner <stan@hardwarefreak.com>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: John Bokma <contact@johnbokma.com>, xfs@oss.sgi.com
Subject: Re: 30 TB RAID6 + XFS slow write performance
Date: Fri, 22 Jul 2011 13:05:14 -0500 [thread overview]
Message-ID: <4E29BBDA.3000603@hardwarefreak.com> (raw)
In-Reply-To: <201107220810.01889@zmi.at>
On 7/22/2011 1:10 AM, Michael Monnerie wrote:
> Yes, I just wanted to know about the corner cases, and how XFS behaves.
> Actually, we're changing over to using NetApps, and with their WAFL
> anyway I should drop all su/sw usage and just use 4KB blocks.
I've never used a NetApp filer myself. However, that said, I would
assume that WAFL is only in play for NFS/CIFS transactions since WAFL is
itself a filesystem.
When exposing LUNs from the same filer to FC and iSCSI hosts I would
assume the filer acts just as any other SAN controller would. In this
case I would think you'd probably still want to align your XFS
filesystem to the underlying RAID stripe from which the LUN was carved.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-07-22 18:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 19:58 30 TB RAID6 + XFS slow write performance John Bokma
2011-07-19 0:00 ` Eric Sandeen
2011-07-19 8:37 ` Emmanuel Florac
2011-07-19 22:37 ` Stan Hoeppner
2011-07-20 0:20 ` Dave Chinner
2011-07-20 5:16 ` Stan Hoeppner
2011-07-20 6:44 ` Dave Chinner
2011-07-20 12:10 ` Stan Hoeppner
2011-07-20 14:04 ` Michael Monnerie
2011-07-20 23:01 ` Dave Chinner
2011-07-21 6:19 ` Michael Monnerie
2011-07-21 6:48 ` Dave Chinner
2011-07-22 6:10 ` Michael Monnerie
2011-07-22 18:05 ` Stan Hoeppner [this message]
2011-07-22 23:10 ` Dave Chinner
2011-07-24 6:14 ` Stan Hoeppner
2011-07-24 8:47 ` 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=4E29BBDA.3000603@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=contact@johnbokma.com \
--cc=michael.monnerie@is.it-management.at \
--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 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.