It didn't actually give any output. After a couple of runs, I added -v, but all I got was this message:
db_recover: Finding last valid log LSN: file: 1 offset 28 Bart. On Fri, Jun 18, 2010 at 7:45 AM, Sam Lang <[email protected]> wrote: > > On Jun 17, 2010, at 3:52 PM, Bart Taylor wrote: > > > We had a pvfs2 server with a local disk file system go down with a bad > mother > > board. After getting the node back up and verifying the configuration was > still > > correct, the server failed to start. Here are the log messages: > > > > > > Jun 17 14:09:45 server2 PVFS2: [D] PVFS2 Server version > 2.6.2pre1-2010-03-11-195020 starting. > > Jun 17 14:09:48 server2 PVFS2: [E] c_get failed on iteration 1 > > Jun 17 14:09:48 server2 PVFS2: [E] Warning: non PVFS2 error code (4243): > > Bart, > > It looks like berkeley db is returning an error right away, with an error > code that PVFS doesn't recognize. What messages does db_recover spit out > when you run it? > > -sam > > > Jun 17 14:09:48 server2 PVFS2: [E] dbpf_dspace_iterate_handles_op_svc: > Unknown error 4243 > > Jun 17 14:09:48 server2 PVFS2: [E] Error adding handle range > 134217731-268435457,2281701363-2415919089 to filesystem pvfs2-fs > > Jun 17 14:09:48 server2 PVFS2: [E] Error: Could not initialize server > interfaces; aborting. > > Jun 17 14:09:48 server2 PVFS2: [E] Error: Could not initialize server; > aborting. > > > > > > I ran db_recover a few times from the storage directory and the fsid > directory, > > but I continue to get these errors. Has anyone run into this? What is the > trick > > to bring it back? > > > > Thanks, > > Bart. > > _______________________________________________ > > Pvfs2-users mailing list > > [email protected] > > http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users > >
_______________________________________________ Pvfs2-users mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
