I believe that the right perspective is to take the "view it as a gc" and leave the file system to do it's job! I don't have the references on hand, but among

I believe that the right perspective is to take the "view it as a gc" and leave the file system to do it's job! I don't have the references on hand, but among possible memory management schemes, "stop and copy" garbage collection is asymptotically fastest, though it does potentially result in "pauses" in the mutator/executing program. Any other scheme has to worry about keeping track of unused data and all the bad news that comes with multiple things going on at the same time.