[LU-13221] conf-sanity test_112: FAIL: MDS start failed

• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Affects Version/s: Lustre 2.14.0, Lustre 2.15.0, Lustre 2.15.1
• Severity: 3
• Assignee: WC Triage
• Reporter: Maloo

Description

This issue was created by maloo for jianyu <[e-mail]>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/94e11602-472f-11ea-a1c8-52540065bddc

test_112 failed with the following error:

Starting mds2:   /dev/mapper/mds2_flakey /mnt/lustre-mds2
CMD: trevis-6vm5 mkdir -p /mnt/lustre-mds2; mount -t lustre   /dev/mapper/mds2_flakey /mnt/lustre-mds2
trevis-6vm5: mount.lustre: mount /dev/mapper/mds2_flakey at /mnt/lustre-mds2 failed: No such file or directory
trevis-6vm5: Is the MGS specification correct?
trevis-6vm5: Is the filesystem name correct?
trevis-6vm5: If upgrading, is the copied client log valid? (see upgrade docs)
Start of /dev/mapper/mds2_flakey on mds2 failed 2
 conf-sanity test_112: @@@@@@ FAIL: MDS start failed 

<<Please provide additional information about the failure here>>

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
conf-sanity test_112 - MDS start failed

Issue Links

• is related to: LU-12818 replay-single test_70b and other tests fail with “Numerical result out of range” error
• is related to: LU-13184 conf-sanity test_112: problem creating f112.conf-sanity.0 on OST0000
• is related to: LU-13813 conf-sanity test_112: can't put import for mdc.lustre-MDT0000-mdc-*.mds_server_uuid into FULL state after 1475 sec, have DISCONN