yeah but that will also rehashes all directories all the time... the setdefault is intentional - it the whole point - don't traverse directories that haven't had any activity since the last replication pass. But if that goes on for a long time...
I think either the hash.pkl can get updated to maybe include also a timestamp next to the hash, so that come reclaim age these really inactive suffixes can go ahead and get swept out, or have something that notices reclaim-aged objects (like the auditor) call invalidate_hash.
Anyway, I don't think just hashing all the directories all the time is gunna work how how we want...
yeah but that will also rehashes all directories all the time... the setdefault is intentional - it the whole point - don't traverse directories that haven't had any activity since the last replication pass. But if that goes on for a long time...
I think either the hash.pkl can get updated to maybe include also a timestamp next to the hash, so that come reclaim age these really inactive suffixes can go ahead and get swept out, or have something that notices reclaim-aged objects (like the auditor) call invalidate_hash.
Anyway, I don't think just hashing all the directories all the time is gunna work how how we want...