Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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


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?

share|improve this question
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
- Run shutdown -Fr now to force a fsck after reboot.

Usually, this can solve file corruption.

Any old backups available?


share|improve this answer
The server automatically attempted that with no luck. – Webnet Aug 17 '10 at 13:48

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

check the official documentation:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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