-
Improvement
-
Resolution: Fixed
-
Medium
-
None
-
3
-
9223372036854775807
Running lustre_rmmod when kmemleak is disabled will produce spurious error messages for many subtests like:
https://testing.whamcloud.com/gerrit-janitor/58788/testresults/conf-sanity2-zfs-rocky8.10_x86_64-rocky8.10_x86_64/conf-sanity.suite_log.oleg460-client.log
lustre_rmmod: line 114: echo: write error: Device or resource busy lustre_rmmod: line 156: echo: write error: Device or resource busy unloading modules via unload_modules_local on: 'oleg460-server' oleg460-server: oleg460-server.virtnet: executing unload_modules_local oleg460-server: lustre_rmmod: line 114: echo: write error: Device or resource busy oleg460-server: lustre_rmmod: line 156: echo: write error: Device or resource busy start mds service on oleg460-server test-framework.sh: line 1033: echo: write error: Device or resource busy test-framework.sh: line 1034: echo: write error: Device or resource busy
This makes it (incorrectly) appear that something is not working properly.
These messages should be quieted.
