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...
Glenn
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Lori Barfield Sent: Tuesday, March 07, 2006 10:57 PM To: toasters@mathworks.com Subject: Re: wafl scan reallocate
since toasters said it was harmless, just to find out what kind of fragmentation our normal activity creates, i ran wafl scan measure_layout on our busiest filer.
the volume is only about 3-4 months young, but it does get pretty full on a regular basis. here's the output that appeared in my messages file:
Tue Mar 7 15:16:36 PST [wafl.scan.start:info]: Starting WAFL layout measurement on volume vol1. Tue Mar 7 16:04:06 PST [wafl.scan.layout.advise:info]: WAFL layout ratio for volume vol1 is 1.26. A ratio of 1 is optimal. Based on your free space, 6.53 is expected.
i haven't read up on this at all yet...would someone like to interpret this for us wafl scan newbies?
...lori