[lustre-discuss] ko2iblnd.conf

2024-04-11 Thread Daniel Szkola via lustre-discuss
Hello all, I recently discovered some mismatches in our /etc/modprobe.d/ko2iblnd.conf files between our clients and servers. Is it now recommended to keep the defaults on this module and run without a config file or are there recommended numbers for lustre-2.15.X? The only thing I’ve seen that

Re: [lustre-discuss] ko2iblnd.conf

2024-04-11 Thread Andreas Dilger via lustre-discuss
On Apr 11, 2024, at 09:56, Daniel Szkola via lustre-discuss mailto:lustre-discuss@lists.lustre.org>> wrote: Hello all, I recently discovered some mismatches in our /etc/modprobe.d/ko2iblnd.conf files between our clients and servers. Is it now recommended to keep the defaults on this module and

Re: [lustre-discuss] ko2iblnd.conf

2024-04-11 Thread Daniel Szkola via lustre-discuss
On the server node(s): options ko2iblnd-opa peer_credits=32 peer_credits_hiw=16 credits=1024 concurrent_sends=64 ntx=2048 map_on_demand=256 fmr_pool_size=2048 fmr_flush_trigger=512 fmr_cache=1 conns_per_peer=4 On clients: options ko2iblnd peer_credits=128 peer_credits_hiw=64 credits=1024 conc

Re: [lustre-discuss] Could not read from remote repository

2024-04-11 Thread Jeff Johnson
Works fine for me. Make sure you don't have a hyperlink embedded in text or something. git clone git://git.whamcloud.com/fs/lustre-release.git [jeff@spinaltap ~/Devel] $ git clone git://git.whamcloud.com/fs/lustre-release.git Cloning into 'lustre-release'... remote: Counting objects: 386278, done

Re: [lustre-discuss] Could not read from remote repository

2024-04-11 Thread Jannek Squar via lustre-discuss
There must have been a problem with the connection, the same line is now working again. Thanks for your help. On 11/04/2024 20:54, Jeff Johnson wrote: Works fine for me. Make sure you don't have a hyperlink embedded in text or something. git clone git://git.whamcloud.com/fs/lustre-release.git

Re: [lustre-discuss] Could not read from remote repository

2024-04-11 Thread Jeff Johnson
Glad to help! On Thu, Apr 11, 2024 at 12:03 PM Jannek Squar wrote: > > There must have been a problem with the connection, the same line is now > working again. Thanks for your help. > > On 11/04/2024 20:54, Jeff Johnson wrote: > > Works fine for me. Make sure you don't have a hyperlink embedded