Granted that I'm not an LNet expert, but "errno: -1 descr: cannot parse net
'<255:65535>' " doesn't immediately lead me to the same conclusion as if
"unknown internface 'ib0' " were printed for the error message. Also "errno:
-1" is "-EPERM = Operation not permitted", and doesn't give the same
A LU ticket and patch for lnetctl or for me being an under-caffeinated
idiot? ;-)
On Wed, Jan 10, 2024 at 12:06 PM Andreas Dilger wrote:
>
> It would seem that the error message could be improved in this case? Could
> you file an LU ticket for that with the reproducer below, and ideally along
It would seem that the error message could be improved in this case? Could you
file an LU ticket for that with the reproducer below, and ideally along with a
patch?
Cheers, Andreas
> On Jan 10, 2024, at 11:37, Jeff Johnson
> wrote:
>
> Man am I an idiot. Been up all night too many nights
Man am I an idiot. Been up all night too many nights in a row and not
enough coffee. It helps if you use the correct --net designation. I
was typing ib0 instead of o2ib0. Declaring as o2ib0 works fine.
(cleanup from previous)
lctl net down && lustre_rmmod
(new attempt)
modprobe lnet -v
lnetctl
Howdy intrepid Lustrefarians,
While starting down the debug rabbit hole I thought I'd raise my hand
and see if anyone has a few magic beans to spare.
I cannot get lnet (via lnetctl) to init a o2iblnd interface on a
RoCEv2 interface.
Running `lnetctl net add --net ib0 --if enp1s0np0` results in
