On Sep 9, 2021, at 02:49, Thomas Roth mailto:t.r...@gsi.de>>
wrote:
Hi all,
I have checked the lru_size on an (2.12.5) system that has just been restarted.
The defaults have never been touched on that system, and so I see lru_size=0
for all OSTs, on the MDS as on a client, as it should be.
The
On Sep 14, 2021, at 11:17, Vicker, Darby J. (JSC-EG111)[Jacobs Technology,
Inc.] via lustre-discuss wrote:
>
> Ah yes, I see what the lnet unit file is doing. OK, I think this is all
> straighten out and working great now. We have a fairly extensive init script
> (the lustre3 script in
On Sep 14, 2021, at 11:17, Vicker, Darby J. (JSC-EG111)[Jacobs Technology,
Inc.] via lustre-discuss
mailto:lustre-discuss@lists.lustre.org>> wrote:
Ah yes, I see what the lnet unit file is doing. OK, I think this is all
straighten out and working great now. We have a fairly extensive init
Hello,
I am about to deploy a new Lustre 2.12.7 systems.
With ZoL version should I choose for my Lustre/ZFS system ?
0.7.13, 0.8.6, 2.0.5, 2.1.0 ?
Thanks
Rick
___
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
Ah yes, I see what the lnet unit file is doing. OK, I think this is all
straighten out and working great now. We have a fairly extensive init script
(the lustre3 script in previous posts) that does various checks in addition to
loading modules and mounting/unmounting the filesystems. But at
When you start LNet via ‘modprobe lnet; lctl net up’, that doesn’t load the
configuration from /etc/lnet.conf. It is going to configure LNet based only on
kernel module parameters. Since you removed the ‘options lnet networks’ from
your modprobe.conf file, it is going to use the default
So I"m a little confused.
When I take the "options lnet networks=o2ib1(ib0)" line out of the modprobe
conf file and instead put that info in the lnet.conf file, things don't work
properly.
[root@r1i1n18 lnet]# cat /etc/modprobe.d/lustre.conf
options ko2iblnd map_on_demand=32
[root@r1i1n18
