Applies to Ontap select Snapmirror Wafl scanner ONTAP 9 Issue Increase in the use of the disks on the aggregate combined with a high load of the cpu on the Ontap select hypervisor.
And blks used can get restarted every time a new delete occurs so it might take a long time for the ownblocks to get a chance to run & update the values, but there is no data integrity issue as far as...And blks used can get restarted every time a new delete occurs so it might take a long time for the ownblocks to get a chance to run & update the values, but there is no data integrity issue as far as the snapshot itself is concerned. Running wafl scan ownblocks_calc from nodeshell forces us to recalculate own blocks values through the scanner even if they are valid/scan has not been kicked off through blocks used which is why you see updated values once this is executed.
