date:20180904

Re: [lustre-discuss] problem with resource-agents rpm

2018-09-04 Thread Nathaniel Clark

For CentOS resource-agents is available in the base package repository (for 7.4 
and 7.5). Can you double check which repositories are enabled?


--

Nathaniel Clark
Senior Software Engineer
Whamcloud


On Thu, 2018-08-30 at 12:05 -0700, Riccardo Veraldi wrote:

Lustre 2.10.5


seems like that lustre-resource-agents has a dependency problem


yum localinstall -y lustre-resource-agents-2.10.5-1.el7.x86_64.rpm

Loaded plugins: langpacks

Examining lustre-resource-agents-2.10.5-1.el7.x86_64.rpm:

lustre-resource-agents-2.10.5-1.el7.x86_64

Marking lustre-resource-agents-2.10.5-1.el7.x86_64.rpm to be installed

Resolving Dependencies

--> Running transaction check

---> Package lustre-resource-agents.x86_64 0:2.10.5-1.el7 will be installed

--> Processing Dependency: resource-agents for package:

lustre-resource-agents-2.10.5-1.el7.x86_64

--> Finished Dependency Resolution

Error: Package: lustre-resource-agents-2.10.5-1.el7.x86_64

(/lustre-resource-agents-2.10.5-1.el7.x86_64)

Requires: resource-agents

  You could try using --skip-broken to work around the problem


Anyone had this issue ?


thanks


Rick




___

lustre-discuss mailing list

lustre-discuss@lists.lustre.org

http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Re: [lustre-discuss] lustre client not able to lctl ping or mount

2018-09-04 Thread Pak Lui

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 modifying the map_on_demand parameter but not
the rest in that file.

Thank you all.

Regards,
- Pak

My current ko2iblnd.conf that is working:

options ko2iblnd peer_credits=128 peer_credits_hiw=64 credits=1024 ntx=2048
map_on_demand=16 fmr_pool_size=2048 fmr_flush_trigger=512 fmr_cache=1
conns_per_peer=4
install ko2iblnd /usr/sbin/ko2iblnd-probe

The default ko2iblnd.conf:

# Currently it isn't possible to auto-tune the o2iblnd parameters optimally
# inside the kernel since the OFED API hides the details from us.
# Unfortunately, there isn't a single set of parameters that provide optimal
# performance on different HCA/HFI types, so this file provides optimized
# tunables based on the installed IB interface cards.
#
# Card detection and tunable selection is handled via
/usr/sbin/ko2iblnd-probe
# at runtime when the ko2iblnd module is installed, either at boot or when
# Lustre is first mounted.

alias ko2iblnd-opa ko2iblnd
options ko2iblnd-opa peer_credits=128 peer_credits_hiw=64 credits=1024
ntx=2048 map_on_demand=256 fmr_pool_size=2048 fmr_flush_trigger=512
fmr_cache=1 conns_per_peer=4

install ko2iblnd /usr/sbin/ko2iblnd-probe

On Tue, Sep 4, 2018 at 9:40 AM, Mohr Jr, Richard Frank (Rick Mohr) <
rm...@utk.edu> wrote:

>
> > 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 ko2iblnd-opa ko2iblnd
> > # tried, as suggested in  http://wiki.lustre.org/
> Optimizing_o2iblnd_Performance
> > #options ko2iblnd-opa peer_credits=128 peer_credits_hiw=64 credits=1024
> ntx=2048 map_on_demand=0 fmr_pool_size=2048 fmr_flush_trigger=512
> fmr_cache=1 conns_per_peer=4
> > options ko2iblnd-opa peer_credits=128 peer_credits_hiw=64 credits=1024
> ntx=2048 map_on_demand=16 fmr_pool_size=2048 fmr_flush_trigger=512
> fmr_cache=1 conns_per_peer=4
> > install ko2iblnd /usr/sbin/ko2iblnd-probe
>
> The lines with ko2iblnd-opa are intended for OmniPath hardware.  Since you
> are using IB, you will want to just set your options like this:
>
> options ko2iblnd peer_credits=…, etc.
>
> Have you verified that the firewall is not running?  It’s possible a
> firewall might be allowing ping traffic but blocking the port needed by
> Lustre.
>
> --
> Rick Mohr
> Senior HPC System Administrator
> National Institute for Computational Sciences
> http://www.nics.tennessee.edu
>
>

-- 
Regards,
- Pak
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Re: [lustre-discuss] lustre client not able to lctl ping or mount

2018-09-04 Thread Klundt, Ruth

//lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20180904/08a17f0d/attachment-0001.html>

--

Message: 2
Date: Tue, 4 Sep 2018 16:00:19 +
From: Richard Henwood 
To: "lustre-discuss@lists.lustre.org"
, "pak@linaro.org"

Subject: Re: [lustre-discuss] lustre client not able to lctl ping or
mount
Message-ID: <5f920989941b1007874e988bf748eb1a84a38068.ca...@arm.com>
Content-Type: text/plain; charset="utf-8"

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 192.168.13.8@o2ib
> > failed to ping 192.168.13.8@o2ib: Input/output error <<<<<<<
>
> lustre client pinging to server over IPoIB works:
> > [root@n0~]# ping -c 1 192.168.13.8
> > PING 192.168.13.8 (192.168.13.8) 56(84) bytes of data.
> > 64 bytes from 192.168.13.8: icmp_seq=1 ttl=64 time=0.376 ms
>
> lustre client pinging to self or other client works:
> > [root@n0 ~]# lctl ping 192.168.13.54@o2ib
> > 12345-0@lo
> > 12345-192.168.13.54@o2ib
>
> lustre client pinging to self or otover IPoIB works:
> > [root@n0~]# ping -c 1 192.168.13.54
> > PING 192.168.13.54 (192.168.13.54) 56(84) bytes of data.
> > 64 bytes from 192.168.13.54: icmp_seq=1 ttl=64 time=0.017 ms
>
> The lustre server and client have specified the modprobe for lnet:
> > /etc/modprobe.conf
> > options lnet networks=o2ib(ib0)
>
> The client reports some error when trying to ping or mount from the
> client to server:
> modprobe lustre lnet
> lctl ping 192.168.13.8@o2ib
> mount -v -t lustre 192.168.13.8@o2ib:/zfs /mnt/zfs
>
> > [root@n0 ~]# dmesg|tail
> > [589805.093447] Lustre: Lustre: Build Version: 2.11.54
> > [589805.272652] LNet: Using FastReg for registration
> > [589805.275954] LNet: Added LNI 192.168.13.54@o2ib [8/256/0/180]
> > [589813.278370] LNet:
> > 22357:0:(o2iblnd_cb.c:3320:kiblnd_check_conns()) Timed out tx for 1
> > 92.168.13.186@o2ib: 589813 seconds
> > [589835.518404] LustreError:
> > 22463:0:(mgc_request.c:251:do_config_log_add()) MGC192.168.13.8@o2i
> > b: failed processing log, type 1: rc = -5
> > [589843.118385] LustreError:
> > 22488:0:(mgc_request.c:601:do_requeue()) failed processing log: -5
> > [589866.718389] LustreError: 15c-8: MGC192.168.13.8@o2ib: The
> > configuration from log 'zfs-client' failed (-5). This may be the
> > result of communication errors between this node and the MGS, a bad
> > configuration, or other errors. See the syslog for more
> > information.
> > [589866.741623] Lustre: Unmounted zfs-client
> > [589867.278516] LustreError:
> > 22463:0:(obd_mount.c:1599:lustre_fill_super()) Unable to mount  (-
> > 5)
>
> server reports some error during mounting:
> > [root@license ~]# Sep  4 07:26:56 license kernel: LNet:
> > 25518:0:(o2iblnd_cb.c:2475:kiblnd_passive_connect()) Can't accept
> > conn from 192.168.13.54@o2ib (version 12): max_frags 16
> > incompatible without FMR pool (256 wanted)
>
> The lustre server setup:
> > [root@license ~]# lfs df -h
> > UUID   bytesUsed   Available Use%
> > Mounted on
> > zfs-MDT_UUID  863.4M7.5M  853.9M   1%
> > /mnt/zfs[MDT:0]
> > zfs-OST_UUID1.7T   10.0G1.7T   1%
> > /mnt/zfs[OST:0]
> >
> > filesystem_summary: 1.7T   10.0G1.7T   1%
> > /mnt/zfs
>
> server: RHEL 7.5 (3.10.0-862.el7.x86_64), MLNX_OFED_LINUX-4.4-
> 2.0.7.0, lustre 2.11.54
> client: RHEL 7.5 (4.14.0-49.el7a.aarch64), MLNX_OFED_LINUX-4.4-
> 2.0.7.0 , lustre 2.11.54
>


It might be helpful to state the Lustre software versions that you have
used.

Also, given this is an Arm client with (with presumably 64K pg size),
connecting to a x86 server (with presumably 4K pg size), have you added
the map_on_demand=16 incantation to the server? I don't have direct
experience of this, but heard it was needed in some Arm configurations
(depending on server/client version):

https://jira.whamcloud.com/browse/LU-10

Re: [lustre-discuss] lustre client not able to lctl ping or mount

2018-09-04 Thread Mohr Jr, Richard Frank (Rick Mohr)


> 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 ko2iblnd-opa ko2iblnd
> # tried, as suggested in  
> http://wiki.lustre.org/Optimizing_o2iblnd_Performance
> #options ko2iblnd-opa peer_credits=128 peer_credits_hiw=64 credits=1024 
> ntx=2048 map_on_demand=0 fmr_pool_size=2048 fmr_flush_trigger=512 fmr_cache=1 
> conns_per_peer=4
> options ko2iblnd-opa peer_credits=128 peer_credits_hiw=64 credits=1024 
> ntx=2048 map_on_demand=16 fmr_pool_size=2048 fmr_flush_trigger=512 
> fmr_cache=1 conns_per_peer=4
> install ko2iblnd /usr/sbin/ko2iblnd-probe

The lines with ko2iblnd-opa are intended for OmniPath hardware.  Since you are 
using IB, you will want to just set your options like this:

options ko2iblnd peer_credits=…, etc.

Have you verified that the firewall is not running?  It’s possible a firewall 
might be allowing ping traffic but blocking the port needed by Lustre.

--
Rick Mohr
Senior HPC System Administrator
National Institute for Computational Sciences
http://www.nics.tennessee.edu

___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Re: [lustre-discuss] lustre client not able to lctl ping or mount

2018-09-04 Thread Pak Lui

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://wiki.lustre.org/Optimizing_o2iblnd_Performance
#options ko2iblnd-opa peer_credits=128 peer_credits_hiw=64 credits=1024
ntx=2048 map_on_demand=0 fmr_pool_size=2048 fmr_flush_trigger=512
fmr_cache=1 conns_per_peer=4
options ko2iblnd-opa peer_credits=128 peer_credits_hiw=64 credits=1024
ntx=2048 map_on_demand=16 fmr_pool_size=2048 fmr_flush_trigger=512
fmr_cache=1 conns_per_peer=4
install ko2iblnd /usr/sbin/ko2iblnd-probe


As for the Lustre software versions that I am using:

> server: RHEL 7.5 (3.10.0-862.el7.x86_64), MLNX_OFED_LINUX-4.4-
> 2.0.7.0, lustre 2.11.54
> client: RHEL 7.5 (4.14.0-49.el7a.aarch64), MLNX_OFED_LINUX-4.4-
> 2.0.7.0 , lustre 2.11.54

As for the IB hardware, it is Mellanox ConnectX-5 Socket Direct. Only 1
IPoIB for mlx5_0 (for the ib0 interface) is configured.

Thanks,
- Pak

On Tue, Sep 4, 2018 at 9:00 AM, Richard Henwood 
wrote:

> 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 192.168.13.8@o2ib
> > > failed to ping 192.168.13.8@o2ib: Input/output error <<<
> >
> > lustre client pinging to server over IPoIB works:
> > > [root@n0~]# ping -c 1 192.168.13.8
> > > PING 192.168.13.8 (192.168.13.8) 56(84) bytes of data.
> > > 64 bytes from 192.168.13.8: icmp_seq=1 ttl=64 time=0.376 ms
> >
> > lustre client pinging to self or other client works:
> > > [root@n0 ~]# lctl ping 192.168.13.54@o2ib
> > > 12345-0@lo
> > > 12345-192.168.13.54@o2ib
> >
> > lustre client pinging to self or otover IPoIB works:
> > > [root@n0~]# ping -c 1 192.168.13.54
> > > PING 192.168.13.54 (192.168.13.54) 56(84) bytes of data.
> > > 64 bytes from 192.168.13.54: icmp_seq=1 ttl=64 time=0.017 ms
> >
> > The lustre server and client have specified the modprobe for lnet:
> > > /etc/modprobe.conf
> > > options lnet networks=o2ib(ib0)
> >
> > The client reports some error when trying to ping or mount from the
> > client to server:
> > modprobe lustre lnet
> > lctl ping 192.168.13.8@o2ib
> > mount -v -t lustre 192.168.13.8@o2ib:/zfs /mnt/zfs
> >
> > > [root@n0 ~]# dmesg|tail
> > > [589805.093447] Lustre: Lustre: Build Version: 2.11.54
> > > [589805.272652] LNet: Using FastReg for registration
> > > [589805.275954] LNet: Added LNI 192.168.13.54@o2ib [8/256/0/180]
> > > [589813.278370] LNet:
> > > 22357:0:(o2iblnd_cb.c:3320:kiblnd_check_conns()) Timed out tx for 1
> > > 92.168.13.186@o2ib: 589813 seconds
> > > [589835.518404] LustreError:
> > > 22463:0:(mgc_request.c:251:do_config_log_add()) MGC192.168.13.8@o2i
> > > b: failed processing log, type 1: rc = -5
> > > [589843.118385] LustreError:
> > > 22488:0:(mgc_request.c:601:do_requeue()) failed processing log: -5
> > > [589866.718389] LustreError: 15c-8: MGC192.168.13.8@o2ib: The
> > > configuration from log 'zfs-client' failed (-5). This may be the
> > > result of communication errors between this node and the MGS, a bad
> > > configuration, or other errors. See the syslog for more
> > > information.
> > > [589866.741623] Lustre: Unmounted zfs-client
> > > [589867.278516] LustreError:
> > > 22463:0:(obd_mount.c:1599:lustre_fill_super()) Unable to mount  (-
> > > 5)
> >
> > server reports some error during mounting:
> > > [root@license ~]# Sep  4 07:26:56 license kernel: LNet:
> > > 25518:0:(o2iblnd_cb.c:2475:kiblnd_passive_connect()) Can't accept
> > > conn from 192.168.13.54@o2ib (version 12): max_frags 16
> > > incompatible without FMR pool (256 wanted)
> >
> > The lustre server setup:
> > > [root@license ~]# lfs df -h
> > > UUID   bytesUsed   Available Use%
> > > Mounted on
> > > zfs-MDT_UUID  863.4M7.5M  853.9M   1%
> > > /mnt/zfs[MDT:0]
> > > zfs-OST_UUID1.7T   10.0G1.7T   1%
> > > /mnt/zfs[OST:0]
> > >
> > > filesystem_summary: 1.7T   10.0G1.7T   1%
> > > /mnt/zfs
> >
> > server: RHEL 7.5 (3.10.0-862.el7.x86_64), MLNX_OFED_LINUX-4.4-
> > 2.0.7.0, lustre 2.11.54
> > client: RHEL 7.5 (4.14.0-49.el7a.aarch64), MLNX_OFED_LINUX-4.4-
> > 2.0.7.0 , lustre 2.11.54
> >
>
>
> It might be helpful to state the Lustre software versions that you have
> used.
>
> Also, given this is an Arm client with (with presumably 64K pg size),
> connecting to a x86 server (with presumably 4K pg size), have you added
> the map_on_demand=16 incantation to the server? I don't have direct
> experience of this, but heard it was needed in some Arm configurations
> (depending on server/client version):
>
>

Re: [lustre-discuss] lustre client not able to lctl ping or mount

2018-09-04 Thread Richard Henwood

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 192.168.13.8@o2ib
> > failed to ping 192.168.13.8@o2ib: Input/output error <<<
>
> lustre client pinging to server over IPoIB works:
> > [root@n0~]# ping -c 1 192.168.13.8
> > PING 192.168.13.8 (192.168.13.8) 56(84) bytes of data.
> > 64 bytes from 192.168.13.8: icmp_seq=1 ttl=64 time=0.376 ms
>
> lustre client pinging to self or other client works:
> > [root@n0 ~]# lctl ping 192.168.13.54@o2ib
> > 12345-0@lo
> > 12345-192.168.13.54@o2ib
>
> lustre client pinging to self or otover IPoIB works:
> > [root@n0~]# ping -c 1 192.168.13.54
> > PING 192.168.13.54 (192.168.13.54) 56(84) bytes of data.
> > 64 bytes from 192.168.13.54: icmp_seq=1 ttl=64 time=0.017 ms
>
> The lustre server and client have specified the modprobe for lnet:
> > /etc/modprobe.conf
> > options lnet networks=o2ib(ib0)
>
> The client reports some error when trying to ping or mount from the
> client to server:
> modprobe lustre lnet
> lctl ping 192.168.13.8@o2ib
> mount -v -t lustre 192.168.13.8@o2ib:/zfs /mnt/zfs
>
> > [root@n0 ~]# dmesg|tail
> > [589805.093447] Lustre: Lustre: Build Version: 2.11.54
> > [589805.272652] LNet: Using FastReg for registration
> > [589805.275954] LNet: Added LNI 192.168.13.54@o2ib [8/256/0/180]
> > [589813.278370] LNet:
> > 22357:0:(o2iblnd_cb.c:3320:kiblnd_check_conns()) Timed out tx for 1
> > 92.168.13.186@o2ib: 589813 seconds
> > [589835.518404] LustreError:
> > 22463:0:(mgc_request.c:251:do_config_log_add()) MGC192.168.13.8@o2i
> > b: failed processing log, type 1: rc = -5
> > [589843.118385] LustreError:
> > 22488:0:(mgc_request.c:601:do_requeue()) failed processing log: -5
> > [589866.718389] LustreError: 15c-8: MGC192.168.13.8@o2ib: The
> > configuration from log 'zfs-client' failed (-5). This may be the
> > result of communication errors between this node and the MGS, a bad
> > configuration, or other errors. See the syslog for more
> > information.
> > [589866.741623] Lustre: Unmounted zfs-client
> > [589867.278516] LustreError:
> > 22463:0:(obd_mount.c:1599:lustre_fill_super()) Unable to mount  (-
> > 5)
>
> server reports some error during mounting:
> > [root@license ~]# Sep  4 07:26:56 license kernel: LNet:
> > 25518:0:(o2iblnd_cb.c:2475:kiblnd_passive_connect()) Can't accept
> > conn from 192.168.13.54@o2ib (version 12): max_frags 16
> > incompatible without FMR pool (256 wanted)
>
> The lustre server setup:
> > [root@license ~]# lfs df -h
> > UUID   bytesUsed   Available Use%
> > Mounted on
> > zfs-MDT_UUID  863.4M7.5M  853.9M   1%
> > /mnt/zfs[MDT:0]
> > zfs-OST_UUID1.7T   10.0G1.7T   1%
> > /mnt/zfs[OST:0]
> >
> > filesystem_summary: 1.7T   10.0G1.7T   1%
> > /mnt/zfs
>
> server: RHEL 7.5 (3.10.0-862.el7.x86_64), MLNX_OFED_LINUX-4.4-
> 2.0.7.0, lustre 2.11.54
> client: RHEL 7.5 (4.14.0-49.el7a.aarch64), MLNX_OFED_LINUX-4.4-
> 2.0.7.0 , lustre 2.11.54
>


It might be helpful to state the Lustre software versions that you have
used.

Also, given this is an Arm client with (with presumably 64K pg size),
connecting to a x86 server (with presumably 4K pg size), have you added
the map_on_demand=16 incantation to the server? I don't have direct
experience of this, but heard it was needed in some Arm configurations
(depending on server/client version):

https://jira.whamcloud.com/browse/LU-10775

May be James can advise?

best regards,
Richard

--
richard.henw...@arm.com
Server Software Eco-System
Tel: +1 512 410 9612
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

[lustre-discuss] lustre client not able to lctl ping or mount

2018-09-04 Thread Pak Lui

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 error <<<

lustre client pinging to server over IPoIB works:

[root@n0~]# ping -c 1 192.168.13.8
PING 192.168.13.8 (192.168.13.8) 56(84) bytes of data.
64 bytes from 192.168.13.8: icmp_seq=1 ttl=64 time=0.376 ms


lustre client pinging to self or other client works:

[root@n0 ~]# lctl ping 192.168.13.54@o2ib
12345-0@lo
12345-192.168.13.54@o2ib

lustre client pinging to self or otover IPoIB works:

[root@n0~]# ping -c 1 192.168.13.54
PING 192.168.13.54 (192.168.13.54) 56(84) bytes of data.
64 bytes from 192.168.13.54: icmp_seq=1 ttl=64 time=0.017 ms


The lustre server and client have specified the modprobe for lnet:

/etc/modprobe.conf
options lnet networks=o2ib(ib0)


The client reports some error when trying to ping or mount from the client
to server:
modprobe lustre lnet
lctl ping 192.168.13.8@o2ib
mount -v -t lustre 192.168.13.8@o2ib:/zfs /mnt/zfs

[root@n0 ~]# dmesg|tail
[589805.093447] Lustre: Lustre: Build Version: 2.11.54
[589805.272652] LNet: Using FastReg for registration
[589805.275954] LNet: Added LNI 192.168.13.54@o2ib [8/256/0/180]
[589813.278370] LNet: 22357:0:(o2iblnd_cb.c:3320:kiblnd_check_conns())
Timed out tx for 192.168.13.186@o2ib: 589813 seconds
[589835.518404] LustreError:
22463:0:(mgc_request.c:251:do_config_log_add()) MGC192.168.13.8@o2ib:
failed processing log, type 1: rc = -5
[589843.118385] LustreError: 22488:0:(mgc_request.c:601:do_requeue())
failed processing log: -5
[589866.718389] LustreError: 15c-8: MGC192.168.13.8@o2ib: The configuration
from log 'zfs-client' failed (-5). This may be the result of communication
errors between this node and the MGS, a bad configuration, or other errors.
See the syslog for more information.
[589866.741623] Lustre: Unmounted zfs-client
[589867.278516] LustreError: 22463:0:(obd_mount.c:1599:lustre_fill_super())
Unable to mount  (-5)


server reports some error during mounting:

[root@license ~]# Sep  4 07:26:56 license kernel: LNet:
25518:0:(o2iblnd_cb.c:2475:kiblnd_passive_connect()) Can't accept conn from
192.168.13.54@o2ib (version 12): max_frags 16 incompatible without FMR pool
(256 wanted)


The lustre server setup:

[root@license ~]# lfs df -h
UUID   bytesUsed   Available Use% Mounted on
zfs-MDT_UUID  863.4M7.5M  853.9M   1%
/mnt/zfs[MDT:0]
zfs-OST_UUID1.7T   10.0G1.7T   1%
/mnt/zfs[OST:0]

filesystem_summary: 1.7T   10.0G1.7T   1% /mnt/zfs


server: RHEL 7.5 (3.10.0-862.el7.x86_64), MLNX_OFED_LINUX-4.4-2.0.7.0,
lustre 2.11.54
client: RHEL 7.5 (4.14.0-49.el7a.aarch64), MLNX_OFED_LINUX-4.4-2.0.7.0 ,
lustre 2.11.54

Regards,
- Pak
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

Re: [lustre-discuss] problem with resource-agents rpm

Re: [lustre-discuss] lustre client not able to lctl ping or mount

Re: [lustre-discuss] lustre client not able to lctl ping or mount

Re: [lustre-discuss] lustre client not able to lctl ping or mount

Re: [lustre-discuss] lustre client not able to lctl ping or mount

Re: [lustre-discuss] lustre client not able to lctl ping or mount

[lustre-discuss] lustre client not able to lctl ping or mount

7 matches

Site Navigation

Mail list logo

Footer information