Hi Ryuta,
I don't know if you are still interested at this point, but there is a
workaround for this problem. You just need to set the MX_IMM_ACK
environment variable to 1 ("export MX_IMM_ACK=1") before starting
pvfs2-client.
I'm not sure what the performance ramifications are, but it should work
fine for testing for now.
-Phil
ryuuta wrote:
Hi,
I'm testing pvfs2 + open-mx on my laptop.
I was finally able to configure pvfs2 with open-mx bmi to confirm that
pvfs2-ping works
and pvfs2-server is functioning. So far so good.
Bad news is that pvfs2-client behaves erratically.
The client starts but it dies sporadically.
[ry...@oroppas]$ sudo more /tmp/pvfs2-client.log
[E 14:03:20.917081] PVFS Client Daemon Started. Version
2.8.1pre1-2009-10-20-045035
[D 14:03:20.917680] [INFO]: Mapping pointer 0xb60c3000 for I/O.
[D 14:03:20.935398] [INFO]: Mapping pointer 0xb6021000 for I/O.
[E 14:04:22.635267] pvfs2-client-core with pid 4502 exited with value 255
dmesg output is
pvfs2: module version 2.8.1pre1-2009-10-20-045035 loaded
pvfs2: pvfs2_statfs -- wait timed out; aborting attempt.
Any advice will be greatly appreciated.
Thanks,
-ryuta
------------------------------------------------------------------------
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users