Without a garbage collection policy, the fakefs database will grow in physical size without bound until all disk space is consumed, even if files in the virtual filesystem are apparently removed (e.g. by unlink or rename).
Different garbage collection plugins implement different garbage collection policies. See also the garbage collection daemon 16.1.
There are two parts to garbage collection policy: identification of garbage in the database, and scheduling garbage removal.