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

truncated db/current file

From: Jeffrey Chang <jeffrey.chang_at_duke.edu>
Date: 2005-05-13 03:25:37 CEST

Hello everybody,

I'm using subversion 1.1.3 on linux with an fsfs repository. I'm the
only user of this repository. After a successful commit, I started
getting the following errors when trying to do update my working copy
on another computer:
[jefftc@ifrit2 e2fmodule]$ svn update
svn: Can't read file '/home/jefftc/svn/db/current': End of file found
[jefftc@ifrit2 e2fmodule]$ svn commit
svn: Commit failed (details follow):
svn: Can't read file '/home/jefftc/svn/db/current': End of file found
svn: Your commit message was left in a temporary file:
svn: '/home/jefftc/projects/e2fmodule/svn-commit.tmp'

Investigating the error message, it appears that the db/current file
got truncated somewhere, and now has 0 file length.

Is there any way to recover this file or regenerate it? This kind of
error doesn't seem to be something that svnadmin can handle.

I looked through the fs_fs.c file, and it appears that db/current is in
the format:
<youngest revision> <node_id> <copy_id>

I can fill in "youngest revision," but I don't know what node_id or
copy_id is for. Has anybody else run into this? Is there any way I
can recover these values, or regenerate a new db/current file so I can
work with this repository again?

Thanks very much,

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 13 14:47:09 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.