I am confused... I am doing pvfs2 server/client in user space rather than pvfs2 kernel interface. I am also sure that pvfs2 client and server are latest version because they were just installed.
I tried many times but still could not figure out why I got a wrong version error. If I uninstall pvfs2.8.1 and follow the same way to install pvfs2.7.1, then everything is running smoothly. Here is my server log: [D 10/08 12:38] PVFS2 Server version 2.8.1 starting. [E 10/08 12:38] Error: BMI_sockio_bind_sock: Address already in use [E 10/08 12:38] Error: tcp_server_init() failure. [E 10/08 12:38] Error: BMI_initialize: Address already in use [E 10/08 12:38] Error: Could not initialize server interfaces; aborting. [E 10/08 12:38] Error: Could not initialize server; aborting. Ben -----Original Message----- From: Phil Carns [mailto:[email protected]] Sent: Wed 10/7/2009 10:51 To: Huang, Bin Cc: [email protected] Subject: Re: [Pvfs2-users] Some verbose logging from pvfs2-cp failure Huang, Bin wrote: > Phil and list, > > Here is what I learned from my pvfs2-cp failure. It turned > out that I did not install my Berkeley DB which I thought > I did. > > I found that without Berkeley DB, pvfs2.8.1 deamon can > still be installed, be configured and be run partially > (only pvfs2-cp and pvfs2-touch failed). For me, that makes > debugging difficult because there is no reminder for missing > a DB in the verbose message.Correct me if I was wrong. > > But after I installed the DB 4.3, pvfs2.8.1-ping gave me a new failure: > > (1) Parsing tab file... > > (2) Initializing system interface... > > (3) Initializing each file system found in tab file: > /home/bhuang2/research/pvfs/swfs/pvfs2/pvfs2-build/pvfs2tab... > > PVFS2 servers: tcp://rsass-homer:3334 > Storage name: pvfs2-fs > Local mount point: /mnt/pvfs2 > [E 10:53:34.815650] Error: poorly formatted protocol message received. > [E 10:53:34.815763] Protocol version mismatch: received major version > 5 when expecting 6. > [E 10:53:34.815778] Please verify your PVFS2 installation > [E 10:53:34.815790] and make sure that the version is consistent. > [E 10:53:34.815813] msgpairarray decode error: Protocol not supported > /mnt/pvfs2: FAILURE! > > Failure: could not initialze at least one of the target file systems. > > (4) Searching for /mnt/pvfs2 in pvfstab... > [E 10:53:34.815869] Error: /mnt/pvfs2/ resides on a PVFS2 file system > that has not yet been initialized. > Failure: could not find filesystem for /mnt/pvfs2 in pvfs2tab > /home/bhuang2/pvfs2-build/pvfs2tab > Entry 0: /mnt/pvfs2 > > I have tried this patch by kevin but that does not help: > http://www.pvfs.org/fisheye/rdiff/PVFS?csid=MAIN:slang:20090306220603&u&N > <http://www.pvfs.org/fisheye/rdiff/PVFS?csid=MAIN:slang:20090306220603&u&N> > > Maybe I will switch back to the stable pvfs2.7.1. > > Thanks for all your helping. > > Ben Hi Ben, That error message indicates that pvfs2-ping was communicating with an old server. Can you double check that you upgraded both the client side tools and all of the server daemons at the same time? I'm surprised that you were able to compile PVFS without a Berkeley DB library. Do you by any chance still have a config.log from that build? thanks, -Phil
_______________________________________________ Pvfs2-users mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
