Hi Rob,
pvfs2-ping works fine on server1 itself, but failed on both client1 and 
client2.Even using IP address in the /etc/pvfs2tab file does not help.The pvfs2 
version is 1.3.2, the latest release, 
fromftp://ftp.parl.clemson.edu/pub/pvfs2/pvfs2-1.3.2.tar.gz.The detailed 
information is shown as below.
Peng
>From server1, on which PVFS2 works, the results is:[EMAIL PROTECTED] ~]# 
>pvfs2-ping -m /mnt/pvfs2
(1) Parsing tab file...
(2) Initializing system interface...
(3) Initializing each file system found in tab file: /etc/pvfs2tab...
   /mnt/pvfs2: Ok
(4) Searching for /mnt/pvfs2 in pvfstab...
   PVFS2 servers: tcp://server1:3334   Storage name: pvfs2-fs   Local mount 
point: /mnt/pvfs2
   meta servers:   tcp://server1:3334
   data servers:   tcp://server1:3334
(5) Verifying that all servers are responding...
   meta servers:   tcp://server1:3334 Ok
   data servers:   tcp://server1:3334 Ok
(6) Verifying that fsid 526730110 is acceptable to all servers...
   Ok; all servers understand fs_id 526730110
(7) Verifying that root handle is owned by one server...
   Root handle: 1048576   Ok; root handle is owned by exactly one server.
============================================================
The PVFS filesystem at /mnt/pvfs2 appears to be correctly configured.

>From client1, with 2.4.20-8 kernel:[EMAIL PROTECTED] root]# pvfs2-ping -m 
>/mnt/pvfs2/
(1) Parsing tab file...
(2) Initializing system interface...
(3) Initializing each file system found in tab file: /etc/fstab...
[E 16:05:10.117316] *** msgpairarray_completion_fn: msgpair failed, noretry: No 
route to host[E 16:05:10.117445] PINT_server_get_config failed: No route to 
host   /mnt/pvfs2: FAILURE!Failure: could not initialize at least one of the 
target file systems.


>From client2, with 2.6.5 kernel,[EMAIL PROTECTED] ~]# pvfs2-ping -m 
>/mnt/pvfs2/(1) Parsing tab file...
(2) Initializing system interface...
(3) Initializing each file system found in tab file: /etc/pvfs2tab...
[E 15:28:40.137400] *** msgpairarray_completion_fn: msgpair failed, noretry: No 
route to host[E 15:28:40.137529] PINT_server_get_config failed: No route to 
host   /mnt/pvfs2: FAILURE!Failure: could not initialize at least one of the 
target file systems.







I tried both hostname and IP address, the pvfs2-ping gives the same results.For 
hostname, the content of the /etc/pvfs2tab file (the same on allthe three 
machines) is :tcp://server1:3334/pvfs2-fs /mnt/pvfs2 default,noauto 0 0
For IP addresses, the content is:tcp://129.93.164.223:3334/pvfs2-fs /mnt/pvfs2 
default,noauto 0 0


On 12/17/05, Rob Ross <[EMAIL PROTECTED]> wrote:> Hi,>> Can you "ping" between 
the various machines using those same names?> Does pvfs2-ping work with those 
hostnames?  Does it work with IP> addresses?  What version of PVFS2 is this?>> 
At least the second error looks like a networking problem.>> Thanks,>> Rob>> 
Peng Gu wrote:> > When I tried to mount the pvfs2, I got the error: "mount: No 
route to host".> > The detailed information is as follows:> > I have three 
Linux machines altogether, namely server1, clients1 and client2.> > server1 
serves as both metadata server and I/O server. All the threemachines are 
clients, including the server itself.> > The problem is, I managed to mount the 
pvfs file system on the server1, however,I failed on both client1 and client2.> 
> The kernels for the three machines:server1:           2.6.9-5ELsmp with 
Fedoraclient1:            2.4.20-8  with Redhat 9client2:            
2.6.9-5ELsmp with Fedora> >> > On client1, when I type,mount -t pvfs2 !
pvfs2 /mnt/pvfs2 -o tcp://server1:3334/pvfs2-fs> > the outcome is:pvfs2_get_sb 
-- wait timed out (ec0001). aborting attempt.pvfs2_get_sb: mount failed with 
15466497mount: Invalid argument> >> > On client2, when I type,mount -t pvfs2 
tcp://server1:3334/pvfs2-fs /mnt/pvfs2-fs> > the outcome is:mount: No route to 
host.> > Any suggestion is appreciated!> >> > Peng>
_______________________________________________
PVFS2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users

Reply via email to