[Pvfs2-users] Help: pvfs2-server won't start, errors detected
jkusznir at gmail.com
Fri Mar 30 16:55:21 EST 2012
I made no changes to my environment; it was up and running just fine.
I ran db_recover, and it immediately returned, with no apparent sign
of doing anything but creating a log.000000001 file.
I have the centos DB installed, db4-4.3.29-10.el5
I have no backups; this is my high performance filesystem of 99TB; it
is the largest disk we have and therefore have no means of backing it
up. We don't have anything big enough to hold that much data.
Is there any hope? Can we just identify and delete the files that
have the db dammange on it? (Note that I don't even have anywhere to
back up this data to temporally if we do get it running, so I'd need
to "fix in place".
On Fri, Mar 30, 2012 at 2:44 PM, Becky Ligon <ligon at omnibond.com> wrote:
> 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 <jkusznir at gmail.com> 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
>> [E 03/30 12:23] Warning: got invalid handle or key size in
>> [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.
>> 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
>> 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
>> Name pvfs2-fs
>> ID 62659950
>> RootHandle 1048576
>> Range pvfs2-io-0-0 4-715827885
>> Range pvfs2-io-0-1 715827886-1431655767
>> Range pvfs2-io-0-2 1431655768-2147483649
>> Range pvfs2-io-0-0 2147483650-2863311531
>> Range pvfs2-io-0-1 2863311532-3579139413
>> Range pvfs2-io-0-2 3579139414-4294967295
>> TroveSyncMeta yes
>> TroveSyncData no
>> Any suggestions for recovery?
>> Pvfs2-users mailing list
>> Pvfs2-users at beowulf-underground.org
> Becky Ligon
> OrangeFS Support and Development
> Omnibond Systems
> Anderson, South Carolina
More information about the Pvfs2-users