On 07/22/2015 11:11 AM, Dave Love wrote:
I had a configuration error that took an embarrassingly long time to
diagnose. I wonder if this sort of failure could be made more obvious
somehow, or if there's a useful debug flag that could be mentioned in
the doc (if I haven't missed something) as I guess it's a relatively
common mistake.
My pvfs2tab had the wrong fs_name in it. In that case, pvfs2-ping just
hangs on a reply from the server. Debug flags of
{client,server},network didn't help, and it wasn't obvious from
pvfs2-set-debugmask output if anything else might have been useful.
Oh man, that happened to one of my students, too. We didn't get a hang,
though.
It doesn't help that pvfs2-genconfig now makes a fs-name called
'orangefs' whereas the quickstart guids one finds on line suggests an
fs-name called pvfs2-fs
==rob
--
Rob Latham
Mathematics and Computer Science Division
Argonne National Lab, IL USA
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
