subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Reser <>
Subject Re: Unable to open repository following reboot
Date Wed, 04 Dec 2013 23:20:33 GMT
On 12/4/13 12:52 PM, Pat Haley wrote:
> ---------------------
> (trying local access)
> ---------------------
> mseas(PaperWork)% svn update
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository 'file:///home/phaley/Papers/2011/ArpitVel/SvnPaper'
> svn: disk I/O error
> svn: disk I/O error
> -----------------------
> (trying network access)
> -----------------------
> chris@optiplex:~/Desktop$ svn update 3DDG
> Updating '3DDG':
> svn: E200030: Unable to connect to a repository at URL
> 'svn+ssh://mseas/software/Students/3DDG'
> svn: E200030: disk I/O error
> svn: E200030: disk I/O error

The second error contains an error code for an error from sqlite:
$ 200030

An update wouldn't be touching a sqlite database on the server since the only
sqlite database on the server side is the rep-cache.db which is only used at
commit time.

Additionally I believe the error message "disk I/O error" only occurs in the
sqlite code.

Are you sure that disk that your working copy is on is ok?

On 12/4/13 2:31 PM, Pat Haley wrote:
>> How about 'svnadmin verify /home/phaley/Papers/2011/ArpitVel/SvnPaper'?
> No, that also fails
> mseas(MeanAvg)% svnadmin verify /home/phaley/Papers/2011/ArpitVel/SvnPaper
> svnadmin: disk I/O error
> svnadmin: disk I/O error

This still looks like some sort of sqlite error.  The rep-cache.db I mentioned
above does get checked as part of svnadmin verify.

Can you run the svnadmin verify under strace:
strace svnadmin verify /home/phaley/Papers/2011/ArpitVel/SvnPaper

You'll get a lot of output but look for the error string in the output and then
look for the preceeding failing system call.  It'll probably be a file handle
so you'll need to dig further up looking for where it was opened.

If you want you could post the output someplace.  If you want to avoid your
data being exposed use "-s 0" to avoid data being printed (but the error string
won't be included).

You can cause strace to write to a file with "-o myoutputfile"

So if you want to post I'd do:
strace -o myoutputfile -s 0 svnadmin verify

View raw message