[LU-8108] Separated MGS/MDS: conf-sanity test_32a: Unable to mount (-114) Created: 05/May/16  Updated: 17/Aug/17

Status: Open
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Related
is related to LU-8688 All Lustre test suites should run/PAS... Open
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for sarah_lw <wei3.liu@intel.com>

This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/4fe49bb2-078e-11e6-b5f1-5254006e85c2.

The sub-test test_32a failed with the following error:

test_32a failed with 5

MGS console

01:36:10:Lustre: DEBUG MARKER: mount -t lustre -o loop,exclude=t32fs-OST0000 /tmp/t32/mdt /tmp/t32/mnt/mdt
01:36:10:LDISKFS-fs (loop0): mounted filesystem with ordered data mode. quota=on. Opts: 
01:36:10:LustreError: 15d-9: The MGS service was already started from server
01:36:10:LustreError: 11211:0:(obd_mount_server.c:1512:server_put_super()) no obd t32fs-MDT0000
01:36:10:LustreError: 11211:0:(obd_mount_server.c:140:server_deregister_mount()) t32fs-MDT0000 not registered
01:36:10:LustreError: 11211:0:(obd_mount.c:1426:lustre_fill_super()) Unable to mount  (-114)
01:36:10:Lustre: DEBUG MARKER: losetup -a
01:36:10:Lustre: DEBUG MARKER: /usr/sbin/lctl mark  conf-sanity test_32a: @@@@@@ FAIL: Mounting the MDT 
01:36:10:Lustre: DEBUG MARKER: conf-sanity test_32a: @@@@@@ FAIL: Mounting the MDT


 Comments   
Comment by James Nunez (Inactive) [ 17/Aug/17 ]

It looks like the patch for LU-7497, https://review.whamcloud.com/#/c/25940/. fixed this issue by not turning on the MGS service in the disk image.

I'm not closing this ticket because it looks like more work is necessary. From the commit message of 25940:

It turned out that the MGS svc was wrongly turned on in disk image
'disk2_4-zfs.tar.bz2', which caused the OST mount failure with
EALREADY because the MGS service has already been started by the MDS.

This is just a temporary solution and the final fix would be to clean
the disk image in question.
Generated at Sat Feb 10 02:14:42 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.