Wondering where to look exactly to figure out why 1000's of files which were recalled are not stubbing back out again. Which logs are required to diagnose the "lack of stubbing or disk cleanup" and are more verbose logging levels needed to really see where the decisions are being made on a per-file basis? I've looked at the FileScan and CXHSMStub logs but am not seeing anything useful:
These are Linux (RHEL7.4) machines running XFS and the disk cleanup rules do not seem to be honored at all. V11 SP10
CXHSMStub::DoStub() - Nothing to stub.
CXHSMStub::DoStub() -  Successfully archived 0 file(s) and skipped/failed 0 file(s)
We've even tried touching the atimes on a bunch of candidate files(setting it back in time) to see if that did anything (which isn't the case anyways since we are using LVM snaps to preserve them during backups).
Set the % min free space to 0, no change, it is not the disk usage preventing cleanup, that is certain.
We have about 45TB to recall and restub but at this pace it will take a year unless we can figure out where they are getting skipped. The disk cleanup does not seem to work as "predictable" as it did in v10 at all.