Re: repository corruption, many times

On 12/19/07, Jeremy Whitlock <jcscoobyrs@gmail.com> wrote:
>
> > The only thing I can think of at this point, aside from an outright bug,
> is
> > that when the trac pre/post commit scripts call back to check the
> repository
> > they're causing corruption -- but afaik they should be read-only ops and
> > this shouldn't cause any harm.
>
>
> Can you send the pre/post hooks for Trac?

Sure. Will send as another email. They're basically the vanilla scripts that
come with trac with a couple regex bugfixes.

I have Trac+Subversion
> running without any scripts and I'd like to see what you're doing. As
> for corruption, any error messages or access/error logs would be
> great.

No error logs. I've got a script that checks for corruption on every commit.
The commit that corrupts is always successful, but any subsequent commits to
the same files trigger errors. Access logs are just the SVN logs themselves.
I also have a couple examples of corrupted changeset files in revs. Relevant
bit is:

------------------------------------------------------------------------
r1296 | john | 2007-12-19 11:46:09 -0800 (Wed, 19 Dec 2007) | 1 line

refs#202 updated tracking spreadsheet to reflect latest thumbnail additions
------------------------------------------------------------------------
r1297 | joelp | 2007-12-19 11:46:15 -0800 (Wed, 19 Dec 2007) | 1 line

ART: Props: accessories: textures: globes, easels, umbrella; refs#195
------------------------------------------------------------------------

1297 is the one that ended up being corrupted today. Note the proximity of
the timestamps. 1296 was a 17K changeset, 1297 was a 25MB changeset.

  Are you using only svnserve or are you still doing Apache and
> svnserve?

Only using svnserve at this point.

Rick
Received on Wed Dec 19 22:48:07 2007