On 2021-12-12 18:09, Mathieu Othacehe wrote: >Hey, > >> OK, thanks. Looks it just finished removing the trash directory >> content. I started a GC process from my session to monitor it >> closely. > >Daily GC recap: > >* The GC process I started yesterday, did collect 5.5TiB in > approximately 24 hours, that are now in the /gnu/store/trash > directory. > >* The /gnu/store/trash directory contains 288910 entries. If those >items > are removed at the same rate than on the previous days, it will take > days/months to delete them all. On another note: when 'guix gc' determines that objects are dead, are they really dead then or can it be that they are 'locally' dead but in case the store serves as substitutes/offload server some external clients may still request dead objects? In the either case would make sense to run the GC more frequently, but for the later case a --min-age option to preserve objects that just died recently could be helping. Further it may consider the atime of objects for removal. And finally while I had this Idea: You mount the guix store with 'relatime' or 'nodiratme', if not that could explain the slow deletion process as well! Christian > >* I noticed that the upstream Nix GC process can now operate without > locking. I think it shouldn't be too hard to port it to our fork or > maybe rewrite the process in Guile while we are at it. > > That will not fix the slow hard-drives issues though. > >Thanks, > >Mathieu > > >