[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: truncated db/current file

From: Jeffrey Chang <jeffrey.chang_at_duke.edu>
Date: 2005-05-14 04:15:37 CEST

On May 13, 2005, at 11:09 AM, Max Bowsher wrote:

> Peter N. Lundblad wrote:
>> On Thu, 12 May 2005, Jeffrey Chang wrote:
>>> Investigating the error message, it appears that the db/current file
>>> got truncated somewhere, and now has 0 file length.
>> I haven't tested, but I *think* a dump/reload should resolve it.
> Create a current file with the contents "<youngest revision> zzzzz
> zzzzz". This should be sufficient to make read-only operations work,
> but it would be *extremely* inadvisable to try committing anything.
> Now you should be able to go ahead with the dump/reload as Peter
> suggested...

I hacked up a new current file and was able to dump the repository

>> Hmmm... I wonder how this file got truncated. It is written and moved
>> into
>> place atomically.
> Ditto, this is very odd.

I now think the problems may be on my end. I've been working with the
IT people here, who have seen some flakiness that they believe may be
caused by NFS. I wasn't able to reload the repository successfully
because the operation would always encounter an error at some point in
the middle of the process. It was usually a stale NFS handle, or
sometimes the truncated current file.

I ended up reloading the repository on another machine that did not
mount that particular disk.

Thanks very much for your help!


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 14 04:18:10 2005

This is an archived mail posted to the Subversion Users mailing list.