That's not a very useful error, but it looks like there might be
something wrong with your dspace db. Can you run it in gdb, set a
breakpoint at dbpf-dspace.c:650, step to the next line and print the
result of "ret"? Line 650 should have:
ret = dbc_p->c_get(dbc_p, &key, &data, DB_MULTIPLE_KEY|DB_NEXT);
The ret value is getting translated to a trove error code, except the
BDB error value isn't one that trove recognizes, so it just spits out
an error code that says it doesn't know anything about the error code.
What version of berkeley DB are you using?
-sam
On May 27, 2009, at 9:45 AM, David Metheny wrote:
I’m getting the following error starting up a PVFS2 server, running
both IO and metadata
PVFS2: [D] PVFS2 Server version 2.6.2pre1-2009-05-12-185735 starting.
PVFS2: [E] c_get failed on iteration 3059
PVFS2: [E] Warning: non PVFS2 error code (4243):
PVFS2: [E] dbpf_dspace_iterate_handles_op_svc: Unknown error 4243
PVFS2: [E] Error adding handle range
805306369-1073741823,2952790009-3221225463 to filesystem pvfs2-fs
PVFS2: [E] Error: Could not initialize server interfaces; aborting.
PVFS2: [E] Error: Could not initialize server; aborting.
The server is configured to sync both metadata and data. The
server’s connected storage experienced a connection problem, causing
a ‘read-only file system’ error. After stopping and starting the
server, it throws the above errors each time.
I’m using the base 2.6 release, with many patches applied. Any ideas
on how to debug this, or recover from it?
Thanks,
_______________________________________________
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
