Hi, In case it helps in raising this as an issue with JFrog, we have seen a similar issue just today in my company, on Artifactory 4.1.3 OSS. The efficiency value had climbed to 226%, and when I tried running the Storage Garbage Collection, I got similar errors to the previous user about files still being read, and thus not being deleted. Solution in our instance was to restart Artifactory, and immediately run the Storage GC, at which point 216 GB was freed (>50% of the storage used!), and no such errors appeared. We never had this happen until now, and we had not restarted the application since upgrading to 4.1.3 in late October.
Thus this looks to be a bug in artifactory 4.1.x whereby the storage GC simply doesn't work correctly, and registers files for deleted artifacts as still being accessed, meaning the space is not freed. This seems to get reset on restart, and freed up. I can't find any ticket open in the artifactory Jira suggesting this is fixed in a later release yet either, so for the time being we will likely have to arrange preventative restarts every 4-6 weeks. Best Regards, Paddy -- View this message in context: http://forums.jfrog.org/Artifactory-4-1-0-artifacts-size-vs-binaries-size-tp7580636p7580666.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
