A feature of Drive Bender is it's ability to track the number and types of files within the pool. We often get asked how reliable this count is, and how it works. So here's the answer.
This file type and count tracking sounds reasonably easy to accomplish, however as the number of files within a pool grow, this task becomes increasingly more difficult. Drive Bender tracks files using two methods. The first is a pool audit, this is simply a count of all primary and duplicate files within the pool. This audit occurs while the Drive Bender health monitor performs it's normal pool health check (depending on the version of Drive Bender you are running, this may occur as infrequently as every 7 days).
The second method is to track files new files written to the pool, and files deleted from the pool (real time tracking). So in theory once we have a solid file count via an audit, simply tracking the files created and deleted should keep us close to a true number.
In reality, quite often this is not how things work. The issue with employing these two methods, is that if there is a lot of file activity during the audit (i.e. file created and / or deleted), there may be files that are either not audited, or have been audited but no longer exist. The end result may well be a file count that is not quite correct (FYI - we have found that these numbers become more accurate overtime).
If you want to re-audit these numbers, you can manually start the Drive Bender health monitor which will check the system and update this count.
Start file system health monitor in v1
Start file system health monitor in v2