I am replying to this email across lists because I wanted to highlight to the git community this jgit change to repacking that we have up for review https://git.eclipse.org/r/#/c/87969/ This change introduces a new convention for how to preserve old pack files in a staging area (.git/objects/packs/preserved) before deleting them. I wanted to ensure that the new proposed convention would be done in a way that would be satisfactory to the git community as a whole so that it would be more easy to provide the same behavior in git eventually. The preserved pack files (and accompanying index and bitmap files), are not only moved, but they are also renamed so that they no longer will match recursive finds looking for pack files. I look forward to any review (it need not happen on the change, replies to this email would be fine also), in particular with respect to the approach and naming conventions. Thanks, -Martin On Tuesday, January 03, 2017 02:46:12 PM jmelvin@xxxxxxxxxxxxxx wrote: > We’ve noticed cases where Stale File Handle Exceptions > occur during git operations, which can happen on users of > NFS repos when repacking is done on them. > > To address this issue, we’ve added two new options to the > JGit GC command: > > --preserve-oldpacks: moves old pack files into the > preserved subdirectory instead of deleting them after > repacking > > --prune-preserved: prunes old pack files from the > preserved subdirectory after repacking, but before > potentially moving the latest old pack files to this > subdirectory > > The strategy is to preserve old pack files around until > the next repack with the hopes that they will become > unreferenced by then and not cause any exceptions to > running processes when they are finally deleted (pruned). > > Change is uploaded for review here: > https://git.eclipse.org/r/#/c/87969/ > > Thanks, > James -- The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation