| To: | Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: 30 TB RAID6 + XFS slow write performance |
| From: | Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx> |
| Date: | Fri, 22 Jul 2011 13:05:14 -0500 |
| Cc: | xfs@xxxxxxxxxxx, Dave Chinner <david@xxxxxxxxxxxxx>, John Bokma <contact@xxxxxxxxxxxxx> |
| In-reply-to: | <201107220810.01889@xxxxxx> |
| References: | <4E24907F.6020903@xxxxxxxxxxxxx> <201107210820.01019@xxxxxx> <20110721064838.GA13963@dastard> <201107220810.01889@xxxxxx> |
| User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH, v2] xfs: set cursor in xfs_ail_splice() even when AIL was empty, Alex Elder |
|---|---|
| Next by Date: | [XFS updates] XFS development tree branch, for-linus, updated. v2.6.38-19012-g55fb25d5, xfs |
| Previous by Thread: | Re: 30 TB RAID6 + XFS slow write performance, Michael Monnerie |
| Next by Thread: | Re: 30 TB RAID6 + XFS slow write performance, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |