Data ONTAP 8.3
What does Performance Metadata stand for?
Performance Metadata is a collection of the blocks that are consumed by the deleted/overwritten data, these blocks haven't been accounted in the free space as their corresponding bitmaps are yet updated. It's introduced by a new featured called Volume Blog.
What is "Volume Blog"?
- "Volume Blog" is a new featured introduced from Data ONTAP 8.3, it's used to accumulate the bitmap updates to lessen the performance impact caused by random bitmap updates.
- With this new feature, the second half of the block freeing procedure might be postponed, and all the postponed bitmap updates would be done in a batcheing manner at a later point.
What is the procedure to free blocks at the Volume layer?
Two steps have to be carried out to clear up a file and reclaim the space. For example, if a file is to be deleted:
- WAFL has to traverse the buftree of this file, and tear down all of indirect blocks.
- WAFL has to update the bitmaps to mark those deleted blocks(both indirect blocks and the user data blocks) as free blocks.
Note: The file is already gone after the first step is done, but the space will only be reclaimed after the second step is complete.
What is the difference in space reporting that "blog" brings to us?
- The space occupied by the deleted files might not be able to return to the free space immediately.
Note: The free space could be checked in the
availablecolumn of the
- There is an Upper Cap for this space locked in this Performance Metadata, it's approximately 2% of the volume size. Once it reaches the Upper Cap, WAFL will start draining it right away and return it to the free space in a batch.
Note: All the above examples are against the file deletion, but Volume Blog works in a similar way for overwrites and hole punching.
Add your text here.