Re: missing objects -- prevention

2013-01-13 Thread Jeff King
On Sun, Jan 13, 2013 at 06:26:53AM +0530, Sitaram Chamarty wrote: > > Right, I meant if you have receive.fsckObjects on. It won't help this > > situation at all, as we already do a connectivity check separate from > > the fsck. But I do recommend it in general, just because it helps catch > > bad

Re: missing objects -- prevention

2013-01-12 Thread Sitaram Chamarty
On Sat, Jan 12, 2013 at 6:43 PM, Jeff King wrote: > On Sat, Jan 12, 2013 at 06:39:52AM +0530, Sitaram Chamarty wrote: > >> > 1. The repo has a ref R pointing at commit X. >> > >> > 2. A user starts a push to another ref, Q, of commit Y that builds on >> > X. Git advertises ref R, so the s

Re: missing objects -- prevention

2013-01-12 Thread Jeff King
On Sat, Jan 12, 2013 at 06:39:52AM +0530, Sitaram Chamarty wrote: > > 1. The repo has a ref R pointing at commit X. > > > > 2. A user starts a push to another ref, Q, of commit Y that builds on > > X. Git advertises ref R, so the sender knows they do not need to > > send X, but only

Re: missing objects -- prevention

2013-01-11 Thread Sitaram Chamarty
Thanks for the very detailed answer. On Fri, Jan 11, 2013 at 10:12 PM, Jeff King wrote: > On Fri, Jan 11, 2013 at 04:40:38PM +0530, Sitaram Chamarty wrote: > >> I find a lot of info on how to recover from and/or repair a repo that >> has missing (or corrupted) objects. >> >> What I need is info o

Re: missing objects -- prevention

2013-01-11 Thread Jeff King
On Fri, Jan 11, 2013 at 04:40:38PM +0530, Sitaram Chamarty wrote: > I find a lot of info on how to recover from and/or repair a repo that > has missing (or corrupted) objects. > > What I need is info on common reasons (other than disk errors -- we've > checked for those) for such errors to occur,