From: "Eric Barton" <[EMAIL PROTECTED]>
Date: Wed, 24 Jan 2007 14:44:49 -0000
Please holler if it's not clear in the documentation.
Wilco :-}
> At startup time, is it as simple as making sure all the right modules are
> loaded, and that the NID name in the mount command gets correctly parsed?
You can debug connectivity before trying any lustre stuff...
1. Get LNET running on relevent nodes: modprobe lnet && lctl net up
2. lctl ping <NID>
Yes. I'm not quite at the point of being able to do that, but getting closer.
I think "my-server" really means "[EMAIL PROTECTED]" because the network
type
of a NID defaults to "tcp" and the network number defaults to "0".
Ah, right, I forgot about that.
If the new network type your LND implements is "sc", then you should be
able to
say...
# mount -t lustre [EMAIL PROTECTED]:/lustrefs /mnt/internal-lustre
Note that all the string/NID conversion stuff is in
<lustre>/lnet/libcfs/nidstrings.c
Yup, I remember that now. We actually went over all that a while back, but
I'd forgotten that tidbit in all the mayhem.
Thanks!
_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
