----- "Philipp Wollermann" <philipp@igowo.de> wrote:
> Hi again,
>
> Philipp Wollermann wrote on 2007-11-22:
> > John Szakmeister wrote on 2007-11-22:
> >> Can you run 'svnadmin verify' on the repository? You're likely to
> get
> >> the same error. If so, then you may be the first person I've met
> who
> >> can consistently cause this fsfs corruption error. Changing to
> mpm-
> >> prefork makes the issue go away, but I'm not entirely sure why.
> > Changing to mpm-prefork didn't change anything (I remembered to
> > completely restart apache). I still get the same error and WC
> > corruption. If you like and have the time, we can meet on IRC to
> discuss
> > the issue (my nick is philwo).
Unfortunately, I don't have much time at the moment. But...
> It gets funny. :) I investigated further:
>
> Using BDB as backend works perfectly even over HTTP using mpm_worker.
> I'll convert my repository to BDB now, so we can continue working on
> our project, but I'd like to help you solve this FSFS-corruption bug.
>
> So, to summarize, on my machine I can consistently reproduce the
> following:
> FSFS + mpm_worker: WC corruption
> FSFS + mpm_prefork: WC corruption
> BDB + mpm_prefork: works perfectly
> BDB + mpm_worker: works perfectly
That's very odd. I'd would have expected the corruption to exist in the repository. Can you send me a tarred up version of your repository and wc? I tried reproducing your problem this morning, and it didn't work (I also need to make sure I have everything configured the same).
Thanks!
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 22 16:16:30 2007