Re: [lustre-discuss] set_param permanent on client side ?

2018-05-28 Thread Dilger, Andreas
Running"lctl get_param -P" and "lctl conf_param" need to be done on the MGS to be able to store the records in the config log, and to ensure that the user has the correct access permissions. The clients are notified of the config log update and apply the logs locally, the parameters do not nee

Re: [lustre-discuss] set_param permanent on client side ?

2018-05-28 Thread Riccardo Veraldi
the problem is that some of these parameters seems like are not there on the MDS side lctl get_param osc.*.checksums error: get_param: param_path 'osc/*/checksums': No such file or directory lctl get_param osc.*.max_pages_per_rpc error: get_param: param_path 'osc/*/max_pages_per_rpc': No such fil

Re: [lustre-discuss] set_param permanent on client side ?

2018-05-23 Thread Artem Blagodarenko
Hello Riccardo, There is “lctl set_param -P” command that set parameter permanently. It needs to be executed on MGS server (and only MGS must be mounted), but parameter is applied to given target (or client). From your example: lctl set_param -P osc.*.checksums=0 Will execute “set_param os

[lustre-discuss] set_param permanent on client side ?

2018-05-22 Thread Riccardo Veraldi
Hello, how do I set_param in a persistent way on the lsutre clinet side so that it has not to be set every time after reboot ? Not all of these parameters can be set on the MDS, for example the osc.* : lctl set_param osc.*.checksums=0 lctl set_param timeout=600 lctl set_param at_min=250 lctl set