[lustre-discuss] lctl set_param not setting values permanently
Andreas Dilger
adilger at whamcloud.com
Thu Nov 8 11:14:28 PST 2018
Jira is your friend. This is a known bug and fixed in 2.12. LU-10906.
Cheers, Andreas
> On Nov 8, 2018, at 09:25, Riccardo Veraldi <Riccardo.Veraldi at cnaf.infn.it> wrote:
>
> Hello,
>
> I did set a bunch of params from the MDS so that they can be taken up by the Lustre clients
>
> lctl set_param -P osc.*.checksums=0
> lctl set_param -P timeout=600
> lctl set_param -P at_min=250
> lctl set_param -P at_max=600
> lctl set_param -P ldlm.namespaces.*.lru_size=2000
> lctl set_param -P osc.*.max_rpcs_in_flight=64
> lctl set_param -P osc.*.max_dirty_mb=1024
> lctl set_param -P llite.*.max_read_ahead_mb=1024
> lctl set_param -P llite.*.max_cached_mb=81920
> lctl set_param -P llite.*.max_read_ahead_per_file_mb=1024
> lctl set_param -P subsystem_debug=0
>
> it works but not for osc.*.checksums=0
>
> every time a client reboots and the filesystem is remounted I have to lctl set_param -P osc.*.checksums=0 on the MDS again so that
>
> all the clients will take again this setting. I do not know why this happens. Any clue ?
>
> I am using Lustre 2.10.5 Centos 7 with kernel 3.10.0-862.14.4.el7.x86_64
>
> thanks
>
> Riccardo
>
>
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
More information about the lustre-discuss
mailing list