Rick,
That ko2iblnd-opa was the cause, thanks.
In the default ko2iblnd.conf that was provided, there has already the
ko2iblnd-opa there appeared to be aliased to back to ko2iblnd, I didn't
think twice about changing the alias and the -opa lines initially which is
why it did not work by just modif
not able to lctl ping or mount (Pak Lui)
--
Message: 1
Date: Tue, 4 Sep 2018 08:06:09 -0700
From: Pak Lui
To: lustre-discuss@lists.lustre.org
Subject: [lustre-discuss] lustre client not able to lctl ping or mo
> On Sep 4, 2018, at 12:12 PM, Pak Lui wrote:
>
> I have tried "map_on_demand=16" to the "/etc/modprobe.d/ko2iblnd.conf" that
> was suggested. Also tried "map_on_demand=0" as suggested here:
> http://wiki.lustre.org/Optimizing_o2iblnd_Performance
>
> /etc/modprobe.d/ko2iblnd.conf
> alias ko2i
Richard, James,
I have tried "map_on_demand=16" to the "/etc/modprobe.d/ko2iblnd.conf" that
was suggested. Also tried "map_on_demand=0" as suggested here:
http://wiki.lustre.org/Optimizing_o2iblnd_Performance
/etc/modprobe.d/ko2iblnd.conf
alias ko2iblnd-opa ko2iblnd
# tried, as suggested in
http
On Tue, 2018-09-04 at 08:06 -0700, Pak Lui wrote:
> Hi all,
>
> I am having issue with the Lustre client pinging the server using
> o2ib.I want to find out if anyone has a suggestion on what could be
> the problem. Thanks in advance.
>
> lustre client pinging to server:
> > [root@n0 ~]# lctl ping 1
Hi all,
I am having issue with the Lustre client pinging the server using o2ib.I
want to find out if anyone has a suggestion on what could be the problem.
Thanks in advance.
lustre client pinging to server:
[root@n0 ~]# lctl ping 192.168.13.8@o2ib
failed to ping 192.168.13.8@o2ib: Input/output e
