Have you actually tried db_recover yet? It can fix some things even
without a transaction log.
I would recommend making a backup of your .db files first. After you
have tried Kevin's suggestion, you can go into the directory for the
collection (where the dataspace_attributes.db and
collections_attributes.db are) and try running db_recover -v.
Kevin and I found recently that db_recover doesn't necessarily print
much of anything to stdout even with the -v, just to warn you.
-Phil
Kevin Harms wrote:
You could try running db_verify -o <file>.db and see what it says.
kevin
On Sep 14, 2009, at 10:34 AM, Becky Ligon wrote:
To all:
We had a disk crash causing the dataspace database to become corrupted in
our production environment. The log messages indicate that we should run
a db_recover, but, as everyone knows, there is not a transactions log
from
which to recover. So, are there any PVFS tools or Berkeley db tools that
we should try?
Becky
--
Becky Ligon
PVFS Developer
Clemson University
864-656-3865
_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
