On Thu, May 17, 2007 at 11:24:45PM +0700, [EMAIL PROTECTED] wrote:
>    - In the procedure *4.4 Testing your Installation* The results are
>    [EMAIL PROTECTED] bin]# ./pvfs2-ping -m /mnt/pvfs2/

It helps to address the issues pvfs2-ping finds in order...

>    (3) Initializing each file system found in tab file: /etc/pvfs2tab...
> 
>       PVFS2 servers: tcp://metadata:3334
>       Storage name: pvfs2-fs
>       Local mount point: /mnt/pvfs2
>    [E 16:15:43.804866]     FS config file integrity checks failed;
>    [E 16:15:43.805660]      FS config file on tcp://metadata:3334 -> (SHA1)
>    fb4fb28220028639c823bb936b09304701eac492
>    [E 16:15:43.805720]      FS config file on tcp://ionode2:3334 -> (SHA1)
>    90f57402bdcb45eac525fc84fae62f8943b8356e
>    [E 16:15:43.805769]      FS config file on tcp://ionode3:3334 -> (SHA1)
>    90f57402bdcb45eac525fc84fae62f8943b8356e
>       /mnt/pvfs2: FAILURE!

This suggests you maybe started the metadata server with an old
fs.conf ?  When you create the config files with 'pvfs2-genconfig'
you'll get an 'fs.conf' that should be used for all servers, and a
server-specific config file for local settings.

Once all the servers are up and running with the same configuration
information, we can move on to the next problem.

==rob

-- 
Rob Latham
Mathematics and Computer Science Division    A215 0178 EA2D B059 8CDF
Argonne National Lab, IL USA                 B29D F333 664A 4280 315B
_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers

Reply via email to