[LU-8679] Lustre-2.8.0 with Mellanox Driver Created: 08/Oct/16  Updated: 11/Oct/16  Resolved: 11/Oct/16

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.8.0
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Atul Yadav Assignee: WC Triage
Resolution: Duplicate Votes: 0
Labels: None
Environment:

Mlnx 3.x with Lustre 2.8.0


Issue Links:
Duplicate
duplicates LU-8675 Lustre 2.8.0 + Centos 6.7 + MLNX_OFED... Resolved
Epic/Theme: CentOS-6.7, Lustre-2.8.0, Mellaonx
Business Value: 150
Severity: 4
Rank (Obsolete): 9223372036854775807

 Description   

Dear Team,

Need your help in adding MLNX_OFED_LINUX-3.3-1.0.4.0 in the Lustre 2.8.0 Infiniband stack.

Thank you
Atul Yadav



 Comments   
Comment by Peter Jones [ 08/Oct/16 ]

Atul

This issue tracker is focused on matters relating to upcoming community releases (at the moment 2.9 is our focus). If you want general help on usage with older releases (rather than reporting a bug which may still exist in the current releases) then you would be better off to either contact your Lustre support provider or else post to the lustre-idiscuss mailing list

Peter

Comment by Atul Yadav [ 09/Oct/16 ]

Peter,

We are using the luster server binary from the "https://downloads.hpdd.intel.com/public/lustre/lustre-2.8.0/el6.7/server/"

And for the client we are building it from the same source of repostiery.

The reason for changiing the IB stack to MLNX on client side is given below:-
Ansys application performance on MLNX IB stack is good.
MSC Nastran application performance on MLNX IB stack is good.
Home grown binary are perfectly tuned for MLNX IB stack.

That's the reason, there is a need of changing lustre IB stack to MLNX IB stack for using 150 TB storage.

Any guidance to achieve the requirement will be helpful.

Thank You
Atul Yadav

Comment by Atul Yadav [ 11/Oct/16 ]

Hi Team,

Waiting for your input...

Thanks in advance...
Atul Yadav

Comment by Atul Yadav [ 11/Oct/16 ]

Hi Team,

Can we have solution of my problem...

Generated at Sat Feb 10 02:19:38 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.