Re: FSFS7 repository corruption during commit with background upgrade

2014-10-20 Thread Stefan Fuhrmann
On Tue, Sep 30, 2014 at 7:08 PM, Stefan Sperling wrote: > On Tue, Sep 30, 2014 at 08:40:00PM +0400, Ivan Zhakov wrote: > > I think there are the following viable options: > > 1) make the svnadmin upgrade work properly for hot repositories > > 2) do not enable log-addressing during svnadmin upgrad

Re: FSFS7 repository corruption during commit with background upgrade

2014-09-30 Thread Stefan Sperling
On Tue, Sep 30, 2014 at 08:40:00PM +0400, Ivan Zhakov wrote: > I think there are the following viable options: > 1) make the svnadmin upgrade work properly for hot repositories > 2) do not enable log-addressing during svnadmin upgrade. > > I think (1) is almost impossible to implement since Subver

Re: FSFS7 repository corruption during commit with background upgrade

2014-09-30 Thread Ivan Zhakov
On 28 September 2014 22:28, Stefan Fuhrmann wrote: > On Fri, Sep 26, 2014 at 4:38 PM, Ivan Zhakov wrote: >> >> I was looking how fsfs upgrade code works and found particular fsfs7 >> log-addressing repository corruption bug: >> 0. Repository has 999 revisions. >> 1. Client begins committing some

Re: FSFS7 repository corruption during commit with background upgrade

2014-09-28 Thread Stefan Fuhrmann
On Fri, Sep 26, 2014 at 4:38 PM, Ivan Zhakov wrote: > I was looking how fsfs upgrade code works and found particular fsfs7 > log-addressing repository corruption bug: > 0. Repository has 999 revisions. > 1. Client begins committing some data to fsfs v6 repository through Apache > 2. Apache web se