The "alias ko2iblnd-opa" line in ko2iblnd.conf doesn't do anything unless OPA
(or older QLogic) interfaces are detected on your system via the
/usr/sbin/ko2iblnd-probe script.
This indirection is used to allow better default module parameters between OPA
and MLX devices, which can't easily be
Anything in dmesg? We need to know _why_ the network failed to start.
Chris Horn
From: Kurt Strosahl
Date: Wednesday, October 2, 2019 at 1:55 PM
To: Chris Horn , "lustre-discuss@lists.lustre.org"
Subject: Re: [lustre-discuss] Lustre rpm install creating a file that breaks
lustre
To: Kurt Strosahl ; lustre-discuss@lists.lustre.org
Subject: [EXTERNAL] Re: [lustre-discuss] Lustre rpm install creating a file
that breaks lustre
Might be best to open a ticket for this. What was the nature of the failure?
Chris Horn
From: lustre-discuss on behalf of
Kurt Strosahl
Date
Might be best to open a ticket for this. What was the nature of the failure?
Chris Horn
From: lustre-discuss on behalf of
Kurt Strosahl
Date: Wednesday, October 2, 2019 at 1:30 PM
To: "lustre-discuss@lists.lustre.org"
Subject: [lustre-discuss] Lustre rpm install creating a file t
Good Afternoon,
While getting lustre 2.10.8 running on a RHEL 7.7 system I found that the
RPM install was putting a file in /etc/modprobe.d that was preventing lnet from
starting properly.
the file is ko2iblnd.conf, which contains the following...
alias ko2iblnd-opa ko2iblnd
options
