[LU-3559] MGS formatted with Lustre 2.1 cannot be started with Lustre 2.4

• Type: Bug
• Resolution: Fixed
• Priority: Blocker
• Fix Version/s: Lustre 2.4.1, Lustre 2.5.0
• Affects Version/s: Lustre 2.4.0, Lustre 2.5.0
• Severity: 3
• Assignee: Bruno Faccini (Inactive)
• Reporter: Sebastien Buisson (Inactive)

Description

With Lustre 2.1, I format an MGS with the follwing command:

mkfs.lustre --reformat --quiet --fsname=migrate --mgs
--mkfsoptions="-m 0" --device-size=204800 /root/mgt

Before starting this MGS, tunefs.lustre gives:

# tunefs.lustre --print /root/mgt
checking for existing Lustre data: found CONFIGS/mountdata
Reading CONFIGS/mountdata

   Read previous values:
Target:     MGS
Index:      unassigned
Lustre FS:  migrate
Mount type: ldiskfs
Flags:      0x74
              (MGS needs_index first_time update )
Persistent mount opts: user_xattr,errors=remount-ro
Parameters:


   Permanent disk data:
Target:     MGS
Index:      unassigned
Lustre FS:  migrate
Mount type: ldiskfs
Flags:      0x74
              (MGS needs_index first_time update )
Persistent mount opts: user_xattr,errors=remount-ro
Parameters:

Still with Lustre 2.1, I successfully start this MGS, and afterwards tunefs.lustre gives:

# tunefs.lustre --print /root/mgt
checking for existing Lustre data: found CONFIGS/mountdata
Reading CONFIGS/mountdata

   Read previous values:
Target:     MGS
Index:      unassigned
Lustre FS:  migrate
Mount type: ldiskfs
Flags:      0x74
              (MGS needs_index first_time update )
Persistent mount opts: user_xattr,errors=remount-ro
Parameters:


   Permanent disk data:
Target:     MGS
Index:      unassigned
Lustre FS:  migrate
Mount type: ldiskfs
Flags:      0x74
              (MGS needs_index first_time update )
Persistent mount opts: user_xattr,errors=remount-ro
Parameters:

Then I update to Lustre 2.4 on my node, and when I try to start this MGS I get:

# mount -t lustre -o loop /root/mgt /mnt/migrate/mgt
mount.lustre.orig: /dev/loop0 has no index assigned (probably formatted with old mkfs)

In Lustre 2.4, it seems mount.lustre requires every target, including MGT, to have an index. But with Lustre 2.1, MGTs can be formatted without specifying an index, and this is the way all our customers did. So if these customers migrate to Lustre 2.4, they will not be able to start their MGS.

I will propose a patch for mount.lustre in Lustre 2.4 to address this issue.

Sebastien.

Issue Links

• is related to: LU-2022 MGS fails to mount due to "has no index assigned (probably formatted with old mkfs" error

Comments

[Peter Jones]

Landed for 2.4.1 and 2.5

[Bruno Faccini (Inactive)]

Added Li Wei and myself as reviewers.

[Jodi Levi (Inactive)]

Reopened for b2_4 patch

[Sebastien Buisson (Inactive)]

Hi,

I would like this ticket to be reopened as I have just pushed a b2_4 version of the patch:
http://review.whamcloud.com/7176

Thanks,
Sebastien.

[Jodi Levi (Inactive)]

Patch landed to master, so closing ticket. If more work is needed, let me know and I will reopen.

[Jodi Levi (Inactive)]

Patch landed to Master. Can this ticket be closed or is more work needed?

[Sebastien Buisson (Inactive)]

Gosh, the 2.1 MGT manipulation is not that easy...
This is why I would like to have the patch in the 2.4 release we will roll out to our customers )

[Bruno Faccini (Inactive)]

Seems that original fix for LU-2022 has been lost in its last change patch-set.

[Bruno Faccini (Inactive)]

Ok, so seems that original (and identical to your!) fix for LU-2022 has been diverted for some reason (others missing index issues, DNE, ...) leading to this interop bug to be left not fixed.

So now I will ask for some other reviewers. And re-trigger the change to auto-tests since it failed due to some known and currently worked-on test problem (LU-3560).

On the other hand, and in case of absolute need without the fix in, you can allow your 2.1 formatted MGT to be mounted by/after :

       _ "mount -t [ldiskfs,zfs]" your MGT stand-alone device
       _ binary edit underlying "CONFIGS/mountdata" file
       _ change the unset/"ffff" MGT index value, at offset 0x18/24 in file, to "0000"

[Sebastien Buisson (Inactive)]

You are right about the joint MGS/MDT case, I have updated my patch accordingly.

Concerning you other question, I can tell for sure that without this patch I simply cannot start my MGT

Sebastien.