Jim: If you haven't made any recent changes to your pvfs environment or Berkeley Db installation, then it looks like you have a corrupted metadata database. There is no way to easily recover. Sometimes, the Berkeley db command "db_recover" might work, but PVFS doesn't have transactions turned on, so normally it doesn't work. It's worth a try, just to be sure.
Do you have any recent backups of the databases? If so, then you will need to use a set of backups that were created around the same time, so the databases will be somewhat consistent with each other. Which version of Berkeley are you using? We have had corruption issues with older versions of it. We strongly recommend 4.8 or higher. There are some know problems with threads in the older versions . Becky Ligon On Fri, Mar 30, 2012 at 3:28 PM, Jim Kusznir <[email protected]> wrote: > Hi all: > > I got some notices from my users with "wierdness with pvfs2" this > morning, and went and investagated. eventually, I found the following > on one of my 3 serers: > > [S 03/30 12:22] PVFS2 Server on node pvfs2-io-0-2 version 2.8.2 starting... > [E 03/30 12:23] Warning: got invalid handle or key size in > dbpf_dspace_iterate_handles(). > [E 03/30 12:23] Warning: skipping entry. > [E 03/30 12:23] c_get failed on iteration 3044 > [E 03/30 12:23] dbpf_dspace_iterate_handles_op_svc: Invalid argument > [E 03/30 12:23] Error adding handle range > 1431655768-2147483649,3579139414-4294967295 to filesystem pvfs2-fs > [E 03/30 12:23] Error: Could not initialize server interfaces; aborting. > [E 03/30 12:23] Error: Could not initialize server; aborting. > > ------------ > pvfs2-fs.conf: > ----------- > > <Defaults> > UnexpectedRequests 50 > EventLogging none > LogStamp datetime > BMIModules bmi_tcp > FlowModules flowproto_multiqueue > PerfUpdateInterval 1000 > ServerJobBMITimeoutSecs 30 > ServerJobFlowTimeoutSecs 30 > ClientJobBMITimeoutSecs 300 > ClientJobFlowTimeoutSecs 300 > ClientRetryLimit 5 > ClientRetryDelayMilliSecs 2000 > StorageSpace /mnt/pvfs2 > LogFile /var/log/pvfs2-server.log > </Defaults> > > <Aliases> > Alias pvfs2-io-0-0 tcp://pvfs2-io-0-0:3334 > Alias pvfs2-io-0-1 tcp://pvfs2-io-0-1:3334 > Alias pvfs2-io-0-2 tcp://pvfs2-io-0-2:3334 > </Aliases> > > <Filesystem> > Name pvfs2-fs > ID 62659950 > RootHandle 1048576 > <MetaHandleRanges> > Range pvfs2-io-0-0 4-715827885 > Range pvfs2-io-0-1 715827886-1431655767 > Range pvfs2-io-0-2 1431655768-2147483649 > </MetaHandleRanges> > <DataHandleRanges> > Range pvfs2-io-0-0 2147483650-2863311531 > Range pvfs2-io-0-1 2863311532-3579139413 > Range pvfs2-io-0-2 3579139414-4294967295 > </DataHandleRanges> > <StorageHints> > TroveSyncMeta yes > TroveSyncData no > </StorageHints> > </Filesystem> > ------------- > Any suggestions for recovery? > > Thanks! > --Jim > _______________________________________________ > Pvfs2-users mailing list > [email protected] > http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users > -- Becky Ligon OrangeFS Support and Development Omnibond Systems Anderson, South Carolina
_______________________________________________ Pvfs2-users mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
