[Lustre-discuss] problem with clients and multiple transports

[John White]

I did have that, with the 2nd line commented out.  I just uncommented the 2nd, unloaded, depmod'd and reloaded only to see the same behavior.
----------------
John White
HPC Systems Engineer
(510) 486-7307
One Cyclotron Rd, MS: 50C-3396
University of California Berkeley
Berkeley, CA 94720

On Nov 2, 2011, at 9:01 AM, Ben Evans wrote:

> My guess is you've got two "options lnet" lines in modprobe.conf
> 
> It should look something like this:
> 
> options lnet networks=tcp0(eth0),o2ib0(ib0)
> options ko2iblnd ipif_name=ib0
> 
> 
> 
> -----Original Message-----
> From: lustre-discuss-bounces at lists.lustre.org
> [mailto:lustre-discuss-bounces at lists.lustre.org] On Behalf Of John White
> Sent: Wednesday, November 02, 2011 11:55 AM
> To: lustre-discuss at lists.lustre.org
> Subject: [Lustre-discuss] problem with clients and multiple transports
> 
> Hello Folks,
> 	I'm having a problem pinning a given FS to a given transport
> type.  I have 2 file systems hosted on the OSS/MDS side by an ib and tcp
> nid (each) being mounted by a client specifying the appropriate
> transport for each of the file systems (one over tcp and one over o2ib).
> I can not mount o2ib.  Period.  If my client's modprobe.conf lists o2ib
> before the tcp nid, any o2ib mount request fails.  If the modprobe.conf
> has tcp first, both mount requests will mount via tcp0, no matter how
> the mount request is crafted.  
> 
> 	So, am I just missing documentation somewhere that states you
> can only use a single transport on a client at a time or is this a bug?
> ----------------
> John White
> HPC Systems Engineer
> (510) 486-7307
> One Cyclotron Rd, MS: 50C-3396
> University of California Berkeley
> Berkeley, CA 94720
> 
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss