Failed files when removing unreferenced files from vaults

[avillanueva]

Just a quick share for vault maintenance. I noticed that when I was removing unreferenced files from one of my vault folders, this one folder failed to moving anything.

mainvault, maincontentvault33
 
Site Name [master]; Vault Name [mainvault]; Folder Name [maincontentvault33]; Size Freed [5,693,163 KB]; Number Of Unreferenced Items [41,392]; Number Of Files For Cleanup [41,392]; Number Of Cleaned Files [0]; Number Of Failed Files [41,392].

All others succeeded. I checked the number of files in that folder. Dawned on my that its using my file vault threshold limit of 1M on the unreferenced subfolder. Paranoid and keeping copy of files. No biggie as this entire volume will be archived soon. So if you see this, it this setting:

wt.fv.fvFileThreshold=1000000

[<redacted> vaults]$ cd maincontentvault33
[<redacted> maincontentvault33]$ ls -l  | wc -l
867827
[<redacted> maincontentvault33]$ cd .unreferenced/
[<redacted> .unreferenced]$ ls -l  | wc -l
1270355

[avillanueva · Accepted solution]

Voilà!

[dnordin]

The unreferenced files don't count towards the wt.fv.fvFileThreshold setting.  Please see Article - CS59822

[avillanueva]

No but the .unreferenced folder clearly is. Seems to be a block on writing more files to a folder. Removing unreferenced files and preserving a copy does a move operation and it will not move if that folder has more than the threshold. Has to be since I just tested it. No, if there are unreferenced files in the folder that have not been cleared, I think that is what that article is talking about.