Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
I've eyeballed the cache size accounting looking for big discrepancies, so I can say it's at least mostly right over short-term usage. We need to do this in code though. I would suggest, at least while we're debugging, adding a signal handler for USR2 (or USR1, whatever), that makes Cache list it's dirs, sum up the actual sizes of objects stored, and compare that against its current stored value.
Attachments
Activity
Current suspicion is that the SM toolkit is the culprit. Since it doesn't go through SM to do those ops, but uses the cache and journal dirs, it creates differences SM doesn't know about. Otherwise accounting may be OK.
Will put this on hold and will reevaluate once the SM tools are fixed.
I haven't seen anything to make me think there is a problem since I fixed the SM toolkit, so I'll close this now.
Looks like there is in fact a small accounting error somewhere. There are a limited # of places where the accounting is changed, shouldn't be that hard to find.