[LU-5863] Can't mount MGS due to label being less than 8 characters long. Created: 04/Nov/14  Updated: 25/Jan/15  Resolved: 25/Jan/15

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.7.0
Fix Version/s: Lustre 2.7.0

Type: Bug Priority: Critical
Reporter: James A Simmons Assignee: James Nunez (Inactive)
Resolution: Fixed Votes: 0
Labels: HB, patch

Issue Links:
Duplicate
is duplicated by LU-5876 MGS volumes with short names do not m... Resolved
Severity: 3
Rank (Obsolete): 16404

 Description   

The patch for LU-5383 fixed a out bound for ldd_svname. It test to see if ldd_svname is at least 8 characters in length but the function in lustre_disk.h server_make_name() sets ldd_svname for the mgs to MGS which is to short. This can prevent the MGS from mounting.



 Comments   
Comment by James A Simmons [ 04/Nov/14 ]

Patch to fix this is at http://review.whamcloud.com/#/c/12564. I think it shows up for previously formatted file systems.

Comment by James Nunez (Inactive) [ 04/Nov/14 ]

Thanks for the patch, James.

Comment by Cliff White (Inactive) [ 06/Nov/14 ]

This bug has stopped all testing on the stable filesystem, as the stable filesystem (formatted with older Lustre ) can no longer be mounted.
arg[4] = /dev/mapper/iws11_4
arg[5] = /mnt/mgs
source = /dev/mapper/iws11_4 (/dev/mapper/iws11_4), target = /mnt/mgs
options = rw
checking for existing Lustre data: found
Reading CONFIGS/mountdata
mount.lustre: invalid name 'MGS'

I really don't want to nuke the stable side, so a fix would be appreciated

Comment by Cliff White (Inactive) [ 06/Nov/14 ]

And, I can't make a new clean filesystem, either. Hyperion is down
MGSNID="192.168.120.5@o2ib"
MGSDEV="/dev/mapper/iws10_4"
MDSDEV="/dev/mapper/iws10_1"
mkfs.lustre --reformat --mgs --device-size=$((512 * 1048576)) --fsname lustre $MGSDEV
mkfs.lustre --reformat --mdt --index=0 --mkfsoptions='-i 4096' --mgsnid=$MGSNID --device-size=$((2048 * 1048576)) --fsname lustre $MDSDEV

mkdir /mnt/mgs
mkdir /mnt/mds

mount -t lustre $MGSDEV /mnt/mgs
mount -t lustre $MDSDEV /mnt/mds
~
Fails with same error

Comment by Cliff White (Inactive) [ 06/Nov/14 ]

And i have confirmed that we do NOT test internally with a separate MGS - so this was a complete escape.

Comment by James Nunez (Inactive) [ 06/Nov/14 ]

Landed to master (pre-2.7)

Comment by Andreas Dilger [ 06/Nov/14 ]

The patch fixes the core of the problem, but it doesn't add a test. Clearly, we need a conf-sanity test that formats a separate MGS and mounts it, since we can't possibly have had such a test if this bug slipped through.

Comment by Jian Yu [ 10/Jan/15 ]

Hi James Simmons,
Are you going to add a regression test case into conf-sanity.sh or would you like me to do this?

Comment by James A Simmons [ 12/Jan/15 ]

Could you finish it off. I'm working on a few other tickets.

Comment by Jian Yu [ 13/Jan/15 ]

Sure. I'll do.

Comment by Jian Yu [ 13/Jan/15 ]

Hi Andreas,

Clearly, we need a conf-sanity test that formats a separate MGS and mounts it, since we can't possibly have had such a test if this bug slipped through.

I found that conf-sanity test 21d is a basic test case that starting a separate MGS. However, autotest system always uses the configuration of combined MGT and MDT, and then test 21d has been always skipped. Should we enhance autotest system to add a configuration of separated MGT and MDT, and run a test session with this configuration?
For now and this ticket, I'll just add a new test case that formats $fs2mds_DEV as a separate MGT and mounts it.

Comment by Patrick Farrell (Inactive) [ 13/Jan/15 ]

In case it influences the decision to know what people are doing in the real world, Cray is increasingly using separate MGS and MDS volumes for ease of backup and recovery.
Also for DNE - it's convenient to have MDS volumes all identical.

Comment by James A Simmons [ 13/Jan/15 ]

Same here. ORNL has run separate MGS/MDS servers for years. If I remember right running separate MGS/MDS is required for IR to work properly.

Comment by Gerrit Updater [ 14/Jan/15 ]

Jian Yu (jian.yu@intel.com) uploaded a new patch: http://review.whamcloud.com/13391
Subject: LU-5863 tests: add a separate MGS/MDS test case into conf-sanity
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 41231258e22cb35555e17a8b94d80c7bfdc5522d

Comment by Jian Yu [ 14/Jan/15 ]

Thank you Patrick and James for the information. The work to enhance autotest system is tracked in TEI-91. For this ticket, I pushed the above patch to add a test case into conf-sanity.sh to verify separate MGS/MDS. The new test case will not be skipped under autotest combined MGS/MDS configuration.

Comment by Gerrit Updater [ 25/Jan/15 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/13391/
Subject: LU-5863 tests: add a separate MGS/MDS test case into conf-sanity
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 589d93f8b01f0a923c0f6ebb64c7ad9935fb05da

Comment by Peter Jones [ 25/Jan/15 ]

Landed for 2.7

Generated at Sat Feb 10 01:55:10 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.