up vote 1 down vote favorite
share [g+] share [fb]

We had a rapid shut down by mistake when our SVN server in the office was unplugged and it caused data corruption.

update

The last commit to this SVN server was last Thursday. The power outage that caused data corruption happened on Friday. If I understand correctly this happened because the data was not finished writing to the disk which caused the corruption. How could it not be finished writing to the disk after over 24 hours? Is it possible that wasn't how it got corrupted?

link|improve this question
90% accept rate
feedback

2 Answers

up vote 0 down vote accepted

Assuming is a linux you first need to do a fsck.
You have two options:
- Create an empty file in / partition named forcefsck: touch /forcefsck
or
- Run shutdown -Fr now to force a fsck after reboot.

Usually, this can solve file corruption.

Any old backups available?

HTH

link|improve this answer
The server automatically attempted that with no luck. – Webnet Aug 17 '10 at 13:48
feedback
up vote 0 down vote

What system do you run ? What error do you have ?

check the official documentation: http://svnbook.red-bean.com/en/1.1/ch05s03.html

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.