Thanks Pete! I think I know why mount failed, as far as I remember I
havent linked the client binaries with IB, only server binaries. I'll
redo the install again today and see how it goes.
That brings me to another question: When you ask pvfs2 to use say IB,
does it mean that cliens also have to be also on IB. I was assuming
that IB will be used for internal communication among the servers only
. Is this not so?
Regards
Vikrant
[EMAIL PROTECTED] wrote on Thu, 24 Aug 2006 21:42 +0530:
Im trying to install PVFS2 on a cluster with Topspin IB. I have been
able to start the pvfs2-server and did some quick testing with MPICH2
and things seem ok. I would note here that during compilation of mpich2
I had to provide CFLAGS and LDFLAGS for lvapi and lmosal, to get the build.
These are all good signs, of course. I had to add -lvapi and
-lmosal too to get mpich2 to link when using libpvfs2. Not sure if
there's any way around that.
Anyways all this is without the kernel module and pvfs2-client. Now when
I start with this part, Im able to load the pvfs2 kernel module and
start the pvfs2-client application. When I try to say:
"mount -t pvfs2 ib://hostname:3335/pvfs2-fs /mnt/pvfs2 "
it throws an error:
mount: Protocol not available
Just to make sure the pvfs2-server on this machine is up using IB, and
on the correct port number.
I can get this error immediately if I misspell the protocol name,
like:
ib27# mount -t pvfs2 xy://ib21:3335/pvfs2-fs /pvfs-ib
mount: Protocol not available
(If you pick the wrong hostname or port, it takes a while to time
out, then reports a different error message.) Take a look at
/tmp/pvfs2-client.log, that's where the client by default sends its
output. It is probably complaining something like:
PVFS_isys_fs_add: Failed to initialize any appropriate BMI methods.
Did you perhaps start a non-IB-build pvfs2-client by accident? See
if it appears to be linked with IB:
ib27# ldd $(which pvfs2-client)
libpvfs2.so => /usr/local/pvfs2-ib-test/lib/libpvfs2.so (0x00002aaaaaaad000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00000034aaf00000)
libvapi.so => /usr/local/ibgd/lib/libvapi.so (0x00002aaaaac88000)
libmtl_common.so => /usr/local/ibgd/lib/libmtl_common.so (0x00002aaaaadaa000)
libmosal.so => /usr/local/ibgd/lib/libmosal.so (0x00002aaaaaeab000)
libmpga.so => /usr/local/ibgd/lib/libmpga.so (0x00002aaaaafbb000)
libdl.so.2 => /lib64/libdl.so.2 (0x00000034aa700000)
libc.so.6 => /lib64/libc.so.6 (0x00000034aa200000)
/lib64/ld-linux-x86-64.so.2 (0x00000034aa000000)
You can also try starting it with lots more debugging:
ib27# killall pvfs2-client
ib27# rm -f /tmp/pvfs2-client.log
ib27# pvfs2-client --gossip-mask=verbose
ib27# mount -t pvfs2 ib://ib21:3335/pvfs2-fs /pvfs-ib
Then see if anything stands out in the log.
-- Pete
|
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
