> Hi,
>
> we encountered (again) the error already discussed in the
> earlier thread
> "Corrupted FSFS commit" (starting February 25).
Update:
Server version: 1.6.5
Client version: 1.6.7
Martin
Hi,
we encountered (again) the error already discussed in the earlier thread
"Corrupted FSFS commit" (starting February 25).
When checking out a reporitory from a subversion 1.6.5 server via https
(apache 2.2), a client receives a connection abort.
The log file states "Svndiff contains a too-
> Mariusz Droździel wrote:
> After some time it turned out, that there are few revisions in our
> repository, which are broken, probably on the filesystem level.
>
> % svnadmin verify /storage/svn
> [...]
> * Verified revision 1025.
> * Verified revision 1026.
> svnadmin: Decompression of svndiff
> Daniel Shahaf wrote:
> Kutter, Martin wrote on Thu, 25 Feb 2010 at 13:29 +0100:
> > I got a strange error in one of our subversion
> > repositories: On checking
> > out a file from revision 3865 on, svn reports "Svndiff
> > contains a too-large window"
Daniel Shahaf wrote:
> Kutter, Martin wrote on Thu, 25 Feb 2010 at 13:29 +0100:
> > I got a strange error in one of our subversion
> > repositories: On checking
> > out a file from revision 3865 on, svn reports "Svndiff
> > contains a too-large window".
&g
Hello,
I got a strange error in one of our subversion repositories: On checking
out a file from revision 3865 on, svn reports "Svndiff contains a too-large
window".
The same error is reported by "svnadmin verify" and "svnadmin dump".
Server OS is RedHat Enterprise Linux 5.4 (64 bit)
Subversion
