<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><font size="-1">Hi all,<br>
Two days ago I made the following Lustre configuration changes:<br>
<br>
lctl set_param -P osc.*.checksums=0<br>
lctl set_param -P osc.*.max_pages_per_rpc=512<br>
lctl set_param -P osc.*.max_rpcs_in_flight=32<br>
lctl set_param -P osc.*.max_dirty_mb=128<br>
<br>
I ran these commands on the MGS. The -P flag promised to make a
permanent change and doing this on the MGS would make it
system-wide. Indeed directly after running the commands, I
noticed that the settings were nicely propagated to other nodes.
<br>
<br>
When I look now, only "</font><font size="-1">max_rpcs_in_flight"
and </font><font size="-1">"max_dirty_mb" still have those
values, the others are back to their defaults, namely </font><font
size="-1"><font size="-1">checksums=</font>1 and </font><font
size="-1"><font size="-1">max_pages_per_rpc</font>=256. The
compute nodes have been rebooted in the mean time.<br>
<br>
Two questions:<br>
- Why were the settings of </font><font size="-1"><font
size="-1"><font size="-1">checksums</font> and </font><font
size="-1"><font size="-1">max_pages_per_rpc lost?</font></font>
(I suspect during the reboot)<br>
- What is the proper way to make these changes permanent? Should
I use "lctl conf_param"?<br>
<br>
Our lustre version:<br>
<br>
# lctl get_param version<br>
version=<br>
lustre: 2.7.0<br>
kernel: patchless_client<br>
build: 2.7.0-RC4--PRISTINE-3.10.0-327.36.3.el7.x86_64<br>
<br>
Thanks,<br>
Reinoud Bokhorst</font></p>
</body>
</html>