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

File Corruption Problem

From: J Kramer <kramer.newsreader_at_gmail.com>
Date: 2007-08-01 01:41:14 CEST

Hi. First let me apologize to those of you who read the SVN Google
group. This question is posted there, but it looks like few people read
that group (and this is a crucial problem).

I'm running SVN over Apache and having an issue. It seems that
an older revision file (110) is corrupt. We are on revision 998 right
now and haven't had any problems before this. The on-site back ups
for this file are corrupt also (well, the files are okay, but empty, I
presume as a result of the original being corrupt). There are some
older off-site backups that might be able to be used to restore.

My apache error log is as follows:

[Tue Jul 31 14:12:43 2007] [error] [client 131.252.150.116] Unable to
PUT new contents for /svn/PATTRepository/!svn/wrk/f312b441-4ca6-1045-
bbac-214dfd993366/PATT Development/trunk/PATT Libraries/Merged/SW,
GENERIC.LIX. [403, #0]
[Tue Jul 31 14:12:43 2007] [error] [client 131.252.150.116] Could not
prepare to write the file [500, #70014]
[Tue Jul 31 14:12:43 2007] [error] [client 131.252.150.116] Can't read
file 'E:\\SVN\\PATTRepository\\db\\revs\\110': End of file found
[500, #70014]
[Tue Jul 31 14:12:43 2007] [error] [client 131.252.150.116] Unable to
PUT new contents for /svn/PATTRepository/!svn/wrk/f312b441-4ca6-1045-
bbac-214dfd993366/PATT Development/trunk/PATT Libraries/Merged/SW,
GENERIC.LIX. [403, #0]
[Tue Jul 31 14:12:43 2007] [error] [client 131.252.150.116] Could not
prepare to write the file [500, #160012]
[Tue Jul 31 14:12:43 2007] [error] [client 131.252.150.116] Cannot
write to the prototype revision file of transaction '998-1' because a
previous representation is currently being written by this process
[500, #160012]

Why am I just getting this error message now? I've committed this
file many times before this. Is it because I had to reinstall SVN
recently?

Is there a way to fix this without recovering rev 110? I have all of the
new files in the repository.
Received on Wed Aug 1 01:40:08 2007

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.