On 2013/07/27 6:00 PM, Jordan Slingerland wrote:
a few things, if you have gone from 8.1.2P3 to P4, you are probably going to want to do a sis start -s on all volumes over 50% or so (netapp says 70, I say 50) and any volumes on aggregates in the same boat.
I do not have the bug number off hand but there is a bug fixed in 8.1.2P4 that fixes an issue with deduplicaiton and causes your next dedup run to inflate the volumes by as much as 30%. I cant help wonder if this bug could be related to your issue. If you cant figure out the bug I am talking about, I can dig through my emails.
Also, just a shot in the dark. have you ran a statit to possibly see if a certain disk could be the source of a bottle neck?
All volumes are currently on the same aggregate (48 disks). Only one of the volumes so far is exhibiting the strange behaviour. Atfter reallocating and growing the volume to give it 40% free space, I still get the same behaviour when trying to initialise dedup on the volume for the first time.
I think I will migrate vm images off this volume onto one which is already dedup enabled. This is seeming like the easiest plan right now
Chris