On Wed, Feb 27, 2019 at 12:22:04AM +0000, Eric Wong wrote: > Eric Wong <e...@80x24.org> wrote: > > Konstantin Ryabitsev <konstan...@linuxfoundation.org> wrote: > > > Eric: > > > > > > I noticed today that the LKML shard 6 has grown over 1.1 GB, which is the > > > size of other shards (0-5). I'm wondering if it will roll over to shard 7 > > > automatically, or if there are other steps that need to be undertaken. > > > > It only counts bytes in *.pack files; so you might need to repack > > (or wait for gc to run via --auto). > > Btw, have you checked this? I've been wondering if 7 will show up, too.
Yeah, I've repacked it, but we still haven't rolled over to 7. This is the latest on the server: $ git count-objects -v count: 18 size: 88 in-pack: 1036749 packs: 1 size-pack: 1169104 prune-packable: 0 garbage: 0 size-garbage: 0 $ ls -al objects/pack/pack-7d2041260250f79f5d2396f38959560e013c8d26.pack -r--r--r--. 1 archiver archiver 1168133236 Feb 27 13:10 objects/pack/pack-7d2041260250f79f5d2396f38959560e013c8d26.pack I'm looking at the code and I'm not entirely sure what PACKING_FACTOR is: my $PACKING_FACTOR = 0.4; ... rotate_bytes => int((1024 * 1024 * 1024) / $PACKING_FACTOR), Wouldn't that give us 2.7GB? (1024*1024*1024)/0.4 = 2,684,354,560 It's possible I'm not following the logic right. It looks to be the same code that properly sharded things on the initial import, so I'm not sure. -K
