Recovering from disk errors
Ed Leafe <[email protected]>
| Newsgroups | gmane.comp.web.zope.zodb.dirstorage |
|---|---|
| Message-ID | <[email protected]> |
I'm hosed. I woke up this morning to a series of I/O error messages on
my server. They were so bad that I couldn't even log in at the console
to try to correct the problem.
I rebooted, and ran the drives through the SCSI utilities to check for
problems, and then fsck'ed like crazy, due to all the problems
reported. Supposedly, though, the disk is fixed, at least to fsck's
liking.
I can't start Zope, though. Since I store my data in /usr/zopestorage,
and the highest number of errors was in the /usr partition, I'm not too
surprised. I looked at the docs on the website, and found "checkds.py -
DirectoryStorage checking tool". Sounds like a good start, so I ran it:
[root@leafe DirectoryStorage]python snapshot.py /usr/zopestorage -
python checkds.py
failed to open /usr/zopestorage/config/snapshot.conf
SnapshotError: directory is not a snapshot
OK, not too surprising. So I renamed this to zopestorage.BAD, and then
restored from my backup. But when I ran it again, I got the exact same
result.
So what do you suggest I do next?
___/
/
__/
/
____/
Ed Leafe
http://leafe.com/
http://dabodev.com/
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com