Hi Lori,
This may answer your question:
http://forums.netapp.com/searchresults.asp?pos=5&page=2&searchterm=w...
Lori, from your log snippet, I have a few questions which you might have some time free to reply on:
1. Did the scan take ~1hr to run? 2. What size was the volume in question? 3. Did you see any performance impact on the filer? 4. Are you snapmirroring the volume in question? If so did you turn off snapmirroring for the duration of the scan?
Thanks alot, Philip
On Wednesday 08 March 2006 05:01, Lori Barfield wrote:
On 3/7/06, Glenn Walker ggwalker@mindspring.com wrote:
Looks like you are doing pretty good...
Keep in mind, it's an average, so for specific data sets in the volume it may be much higher (or lower). Workload measurements (statit during specific operations) can tell you much more sometimes.
Filling the volume is typically a bad idea (tm) as WAFL will spend more time finding free space to write. If this is a flexvol and the aggr has tons of space available, this is not a concern.
7.X has great improvements on fixing fragmentation and preventative measures to keep it from becoming an issue.
Remember: Fragmentation is NORMAL with any filesystem and isn't necessarily a problem. What fragmentation _does_ do is introduce latencies that can be detrimental to responsiveness... sometimes this can be felt (ie, it's a problem), sometimes it cannot be felt...
thanks, glenn. can you tell us what this means?
Based on your free space, 6.53 is expected.
...lori