Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\s+Performance\s+on\s+NetApp\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\s+Performance\s+on\s+NetApp\s*$/: 3 ]

Total 3 documents matching your query.

1. XFS Performance on NetApp (score: 1): Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>; Date: Wed, 27 Oct 2010 00:33:35 +0200; Does anybody have a report how XFS behaves on a NetApp storage with thin provisioning? They have a completely "weird" storage, their WAFL (write anywhere file layout) together with deduplication and; /archives/xfs/2010-10/msg00338.html (7,853 bytes)
2. Re: XFS Performance on NetApp (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Wed, 27 Oct 2010 10:10:07 +1100; Not about the Netapp as such. However, as a general rule thin provisioned storage will have unpredictable performance characteristics as the block number/physical location correlation is meaningless.; /archives/xfs/2010-10/msg00340.html (8,156 bytes)
3. Re: XFS Performance on NetApp (score: 1): Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>; Date: Wed, 27 Oct 2010 01:57:03 +0200; Yes, but for NetApp: maybe. With this whole deduplication thingy, I wonder if even such a simple assumption is true. And then some people make a snapshot every hour, whichmeans your log will wander a; /archives/xfs/2010-10/msg00343.html (8,883 bytes)

Current List: 1 - 3
Page: [1]