Can you tell us more about the version of Lustre you are using, that
options to the bonding module are you setting, and possibly what type of
switch you are using?  Those things may help.    If you are able to set
up two separate networks on the two interfaces, it is possible(correct
me here guys if I have this wrong) that Lustre can just run over the two
interfaces and be just happy.  For example, can you make all the eth0
interfaces be on the 10.10.10.0/24 network, and all the eth1 interfaces
on the 10.10.20.0/24 network.  The just use the lnet module
parameters(>=1.4.6 only) to set two channels for traffic.


Evan 

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Mann
> Sent: Thursday, December 14, 2006 2:21 PM
> To: [email protected]
> Subject: [Lustre-discuss] Using Lustre on channel bonded interfaces
> 
> First of all, thanks to everyone for an awesome product! My 
> first usage of Lustre has been on a small cluster with 
> gigabit interfaces. I can saturate the network and achieve 
> 100 MB/s accessing the Lustre filesystem. My problem comes 
> into when I channel bond 2 gigabit interfaces, my speed drops 
> to 54 MB/s. A recent thread I googled says that this problem 
> is due to the robin-robin trunking of a default channel 
> bonded system, which I now understand.
> 
> My question is, is anybody else out there using Lustre with 
> channel bonded interfaces? If so, what trunking and kernel 
> options for bonding are you using?
> 
> Thanks for any hints or tips!
> 
> --
> Jeremy Mann
> [EMAIL PROTECTED]
> 
> University of Texas Health Science Center Bioinformatics Core 
> Facility http://www.bioinformatics.uthscsa.edu
> Phone: (210) 567-2672
> 
> _______________________________________________
> Lustre-discuss mailing list
> [email protected]
> https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
> 

_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss

Reply via email to