broad-processor-92400
02/15/2023, 9:36 PMlmdb_store
directory is currently at 46GiB, which is a fairly hefty proportion of my full disk. AIUI, pantsd is meant to be doing some GC on it, but, if so, there's a lot of non-garbage. Can I introspect the GC process? Is there a way to force a (harder) GC?curved-television-6568
02/15/2023, 9:38 PMrm -rf ~/.cache/pants
?witty-crayon-22786
02/15/2023, 9:38 PM.pants.d/pants.log
should record a GC every 4 hours, iircbroad-processor-92400
02/15/2023, 9:39 PMrm
😅
I'll have a look at the log, thankswitty-crayon-22786
02/15/2023, 9:40 PMtokio
task at this pointbroad-processor-92400
02/15/2023, 9:41 PM08:22:09.39 [INFO] Garbage collecting store. target_size=28,800,000,000
08:22:11.56 [INFO] Done garbage collecting store
I'll increase the log level and see what else comes out of itwitty-crayon-22786
02/15/2023, 9:41 PMbroad-processor-92400
02/15/2023, 9:42 PMShrinkBehavior::Compact
which sounds more aggressive than ShrinkBehavior::Fast
🤔 )witty-crayon-22786
02/15/2023, 9:42 PMbroad-processor-92400
02/15/2023, 9:44 PMwitty-crayon-22786
02/15/2023, 9:45 PMbitter-ability-32190
02/15/2023, 9:46 PMwitty-crayon-22786
02/15/2023, 9:46 PMbitter-ability-32190
02/15/2023, 9:47 PMwitty-crayon-22786
02/15/2023, 9:48 PMbitter-ability-32190
02/15/2023, 9:51 PMfast-nail-55400
02/15/2023, 10:01 PMtmpwatch
on the large file directory assuming atime is updatedwitty-crayon-22786
02/15/2023, 10:01 PMbitter-ability-32190
02/15/2023, 10:01 PMwitty-crayon-22786
02/15/2023, 10:02 PMbitter-ability-32190
02/15/2023, 10:02 PMbroad-processor-92400
02/15/2023, 11:40 PMwitty-crayon-22786
02/15/2023, 11:40 PMbroad-processor-92400
02/16/2023, 3:24 AM-ltrace
, it seems there's no additional logging beyond the INFO
above, ah well.
The fact that https://github.com/pantsbuild/pants/blob/3304f13aecd534f5581b35104ad77bea41809b5d/src/rust/engine/fs/store/src/lib.rs#L1099-L1106 didn't trigger (i.e. the GC successfully reduced the reported size below 28.8GB) would suggest that indeed this might be a fragmentation issue, since 46GB is a little larger than 28.8GB.
I'll try a ShrinkBehavior::Compact
GC to confirm.fs_util gc --target-size-bytes 28800000000
resulted in it the directory being the expected size