In case anyone was looking through this, the recommendation from our vendor was to modify lru_max_age instead. Our OST's are right were they recommended (5 minutes), but our MDT's were off by 60 minutes. -Matt
-----Original Message----- From: lustre-discuss <[email protected]> On Behalf Of Bidwell, Matt Sent: Thursday, April 11, 2019 2:53 PM To: [email protected] Subject: [lustre-discuss] soft lockup native_queued_spin_lock_slowpath issue I seem to be hitting a known Lustre client issue, as I found several bug reports similar to: https://jira.whamcloud.com/browse/LU-11693. I'm running lustre-client-2.10.5. Running the proposed temporary solution on test clients lctl set_param ldlm.namespaces.*.lru_size=10000 appears to fix this issue. I'm not really sure the significance of this command. Is it safe to run on clients while jobs are running? I'd like to run this now, and then install a patched client during our next system time. Thanks. -Matt _______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org _______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
