https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-4757 Lustre <p>On an OSS, am unable to configure a persistent throttle the number of ost_io threads. It may be user or doc error, but have tried kernel module settings and a few different conf_param syntax, per section 32.9 of the Lustre manual:</p> <p><span class="error">&#91;root@oss0 ~&#93;</span># lctl get_param ost.OSS.ost_io.threads_max<br/> ost.OSS.ost_io.threads_max=512</p> <p><span class="error">&#91;root@oss0 ~&#93;</span># cat /etc/modprobe.d/lustre.conf<br/> options lnet networks=tcp1(eth3)<br/> options ost oss_num_threads=256</p> <p><span class="error">&#91;root@oss0 ~&#93;</span># lctl conf_param cal.ost.ost_io.threads_max=128<br/> No device found for name MGS: Invalid argument<br/> This command must be run on the MGS.<br/> error: conf_param: No such device</p> <p><span class="error">&#91;root@oss0 ~&#93;</span># lctl conf_param ost.OSS.ost_io.threads_max=128<br/> No device found for name MGS: Invalid argument<br/> This command must be run on the MGS.<br/> error: conf_param: No such device</p> <p><span class="error">&#91;root@oss0 ~&#93;</span># lctl set_param ost.OSS.ost_io.threads_max=128<br/> ost.OSS.ost_io.threads_max=128</p> <p><span class="error">&#91;root@oss0 ~&#93;</span># lctl get_param ost.OSS.ost_io.threads_max<br/> ost.OSS.ost_io.threads_max=128</p> <p><span class="error">&#91;root@oss0 ~&#93;</span># cat /proc/fs/lustre/version<br/> lustre: 2.4.2<br/> kernel: patchless_client<br/> build: 2.4.2-RC2--PRISTINE-2.6.32-358.23.2.el6_lustre.x86_64</p> LU-4757

Unable to set upper limit on ost_io threads

Bug Minor Resolved Won't Fix WC Triage Brett Lee Wed, 12 Mar 2014 19:24:41 +0000 Sat, 9 Oct 2021 05:59:38 +0000 Sat, 9 Oct 2021 05:59:38 +0000 Lustre 2.4.2 0 3 <p>Did you notice the part of the conf_param "This command must be run on the MGS."? Also, sadly, the device naming for conf_param is different than set_param, you need to check the manual, since I don't know it offhand.</p> <p>The module parameters definitely should work, however, so this needs further investigation.</p> <p>Yes, I did see that about conf_param on the MGS, but attributed that to a mistake as it didn't seem logical (looks like the mistake is mine). I have this as an open item to verify the functionality, so will report back once I've checked via the MGS.</p> <p>"<tt>lctl conf_param</tt>" is deprecated, use "<tt>lctl set_param -P</tt>" instead.</p> Development Rank 1|hzwhif: Rank (Obsolete) 13090 Severity