[LU-9860] conf-sanity test_33a fails with “mount -t lustre failed“ for separate MDS and MGS Created: 10/Aug/17 Updated: 26/Aug/19 Resolved: 17/Jun/19 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.11.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | James Nunez (Inactive) | Assignee: | James Nunez (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | tests | ||
| Environment: |
Separate MGS and MDS or separate MGT and MDT |
||
| Issue Links: |
|
||||||||||||
| Severity: | 3 | ||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||
| Description |
|
conf-sanity test 33a fails when run on a Lustre file system configured with a separate MDS and MGS, even with a separate MDT and MGT on the same node. The error message is conf-sanity test_33a: @@@@@@ FAIL: mount -t lustre failed In the test log, we see that mounting the MDS for the newly created file system fails CMD: onyx-50vm7 mkdir -p /mnt/lustre-fs2mds; mount -t lustre /dev/lvm-Role_MDS/S1 /mnt/lustre-fs2mds onyx-50vm7: mount.lustre: mount /dev/mapper/lvm--Role_MDS-S1 at /mnt/lustre-fs2mds failed: Operation already in progress onyx-50vm7: The target service is already running. (/dev/mapper/lvm--Role_MDS-S1) This failure looks like it is due to the mgs flags used when the MDT is formatted; “—mgs” flag. When an MGS already exists, specifying that this node will be the MGS for the new file system causes problems. In addition, the lctl call in the following code needs to be run on the MGS 2418 do_facet $SINGLEMDS "$LCTL conf_param $FSNAME2.sys.timeout=200" || 2419 error "$LCTL conf_param $FSNAME2.sys.timeout=200 failed" We see similar failures for conf-sanity tests 43b, 53b, 54b Logs that capture test 33a failures are at Note: This tickets description was modified to state the problem more clearly and not only subscribe a solution. |
| Comments |
| Comment by Gerrit Updater [ 11/Aug/17 ] |
|
James Nunez (james.a.nunez@intel.com) uploaded a new patch: https://review.whamcloud.com/28478 |
| Comment by Gerrit Updater [ 11/Aug/17 ] |
|
James Nunez (james.a.nunez@intel.com) uploaded a new patch: https://review.whamcloud.com/28497 |
| Comment by Gerrit Updater [ 28/Aug/17 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/28497/ |
| Comment by James Nunez (Inactive) [ 28/Aug/17 ] |
|
The patch to add conf-sanity tests to the ALWAYS_EXCEPT list has landed to master. Let's keep this ticket open until we get a fix for conf-sanity tests 33a, 43b, 53b, 54b. |
| Comment by Gerrit Updater [ 24/Oct/17 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/28478/ |
| Comment by Gerrit Updater [ 22/Nov/17 ] |
|
James Nunez (james.a.nunez@intel.com) uploaded a new patch: https://review.whamcloud.com/30216 |
| Comment by Gerrit Updater [ 19/Dec/17 ] |
|
John L. Hammond (john.hammond@intel.com) merged in patch https://review.whamcloud.com/30216/ |
| Comment by James Nunez (Inactive) [ 17/Jun/19 ] |
|
All tests that were added to the ALWAYS_EXCEPT list have been removed or other tickets have been opened to track the issue. |
| Comment by Andreas Dilger [ 26/Aug/19 ] |
|
This was resolved with the landing of patch https://review.whamcloud.com/33589 " |