Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

What is ownblocks_calc scanner and how does it work?

Last Updated:

Applies to

  • ONTAP 9


  • The snapshot is safely written to disk on the first consistency point after a snapshot command is issued.
  • The size etc are computed after the face by a slow ownblocks_calc scan that is deliberately throttled.
  • We run the ownblocks_calc when a snap is created, or blocks used completes (kicked off after a snap delete) or if a list command is executed.
  • Further, since we only invalidate the values when blks used runs, it is possible that the values become quite stale until blks used finishes.
  • 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.

Example output:

::> set advanced
::*> run local wafl scan status volume_name
Volume volume_name:
Scan id                   Type of scan     progress
  843657    block ownership calculation     block 19994 of 30803


Scan to view the article on your device