Chris Worley wrote: > On Fri, Mar 7, 2008 at 9:39 AM, Craig Prescott <[EMAIL PROTECTED]> wrote: >> I think your client modprobe.conf lnet option >> should be this: >> >> >> options lnet networks=o2ib(ib0) >> >> (not 'o2ib0'). > > It still seems to want the TCP connection: > > <snip>
Oh, sorry - I didn't notice you were using 'o2ib0's everywhere. In that case, you should keep it. > >> Another thing to try, if that doesn't work lctl >> ping your MDS/MGS/OSS nids, like so: >> >> lctl ping [EMAIL PROTECTED] > > Before and after the change it looks the same: > > # lctl ping [EMAIL PROTECTED] > [EMAIL PROTECTED] > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > If I change my modprobe.conf to look as on the MDS/OSS's: > > options lnet networks=o2ib0(ib0),tcp0(eth0) > > Then, mount just specifying o2ib: > > # mount -t lustre [EMAIL PROTECTED]:/ddnlfs /lfs > > It works, but, both ko2iblnd and ksocklnd are loaded. Ok, so you need the tcp nid for the mount to succeed. So it looks like the MGS is only available via the tcp nid. Is the quoting you had in the --mgsnode option when you created the fs responsible for this? Maybe. If you can recreate the filesystem again, try it without the quotes: mkfs.lustre --reformat --fsname=... --ost --whateverelse \ [EMAIL PROTECTED],[EMAIL PROTECTED] ... Cheers, Craig > The dmesg output is: > > Lustre: OBD class driver, [EMAIL PROTECTED] > Lustre Version: 1.6.4.2 > Build Version: > 1.6.4.2-19691231190000-PRISTINE-.usr.src.linux-2.6.9-67.0.4.EL-Lustre-1.6.4.2 > Lustre: Added LNI [EMAIL PROTECTED] [8/64] > Lustre: Added LNI [EMAIL PROTECTED] [8/256] > Lustre: Accept secure, port 988 > Lustre: Lustre Client File System; [EMAIL PROTECTED] > Lustre: ddnlfs-clilov-000001042f8b7c00.lov: set parameter stripesize=2M > Lustre: Client ddnlfs-client has started > > Can I be certain it'll use IB for LFS on this client? > > Thanks, > > Chris _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
