5a5493c0f72e62c5a85aa6bc.zip
[LU-10715] several conf-sanity tests failed: rmmod: ERROR: Module mgc is in use Created: 26/Feb/18 Updated: 04/Dec/23 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.11.0, Lustre 2.13.0, Lustre 2.14.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Elena Gryaznova | Assignee: | WC Triage |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
5a5493c0f72e62c5a85aa6bc.zip
|
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
stdout : stop ost1 service on fre1238 stop mds service on fre1237 stop mds service on fre1237 Trace dump: = /usr/lib64/lustre/tests/conf-sanity.sh:254:main() conf-sanity: FAIL: test-framework exiting on error stderr: rmmod: ERROR: Module mgc is in use test_88 log is attached |
| Comments |
| Comment by James Nunez (Inactive) [ 10/Sep/20 ] |
|
We’re seeing this error for conf-sanity test_5c. There are many failures for branch and review/patch testing on master going back over a year and a half. When this test fails with this error, most of the conf-sanity tests after 5c fail with ‘Unable to start MDS’, ‘MDT start failed’, ‘mount /mnt/lustre failed’ or ‘mount client /mnt/lustre failed’. The following routines are failing
224 unload_modules_conf () {
225 if combined_mgs_mds || ! local_mode; then
226 unload_modules || return 1
227 fi
228 }
229
230 cleanup_nocli() {
231 stop_ost || return 202
232 stop_mds || return 201
233 unload_modules_conf || return 203
234 }
Logs for some past failures are at |