[LU-11760] formatted OST recognition change

• Type: Bug
• Resolution: Fixed
• Priority: Critical
• Fix Version/s: Lustre 2.13.0, Lustre 2.12.3
• Labels: patch
• Severity: 3
• Assignee: Sergey Cheremencev
• Reporter: Sergey Cheremencev

Description

We faced multiple missing OST objects mdtest job failure during failover/failback test(stripe count 2).

V-1: Entering unique_dir_access...
V-1: Entering mdtest_stat...
08/14/2018 21:46:25: Process 25(nid00016): FAILED in mdtest_stat, unable to stat file: No such file or directory
08/14/2018 21:46:25: Process 30(nid00045): FAILED in mdtest_stat, unable to stat file: No such file or directory

Failure occurred because of absent the range of objects on one of the OSTs.

The marker of the failure could be the following message after recovery on OST:

Aug 14 21:46:07 snx11205n004 kernel: format at ofd_dev.c:1713:ofd_create_hdl doesn't end in newline 

Issue Links

• is related to: LU-12415 conf-sanity test 69 fails with 'OST replacement created too many inodes; X'
• is related to: LU-12404 conf-sanity test 69 fails with 'create file after reformat'

Comments

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/35388/
Subject: Revert "LU-11760 ofd: formatted OST recognition change"
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 8065d44c0a2b29885ca429674ccab7785d2db08b

[Gerrit Updater]

Andreas Dilger ([e-mail]) uploaded a new patch: https://review.whamcloud.com/35388
Subject: Revert "LU-11760 ofd: formatted OST recognition change"
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 563277b8d728c45bd89074c07a22f1432beea344

[Gerrit Updater]

Sergey Cheremencev ([e-mail]) uploaded a new patch: https://review.whamcloud.com/35373
Subject: LU-11760 ofd: limit num of objects to create in 1 transaction
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: e75f4977695657710a9144a31a0d149fa1925ef8

[Sergey Cheremencev]

I don't mind to have a change that is increasing the maximum number of objects created per commit, but this needs to be negotiated between the MDS and OSS at connect time, with a new OBD_CONNECT2_MAX_PRECREATE flag and an ocd_max_precreate field (probably using __u32 padding1) that passes the current OST_MAX_PRECREATE value, and use OST_MAX_PRECREATE_OLD = 20000 if the feature is not available. This also allows fixing the problem properly in older releases.

If we increase OST_MAX_PRECREATE on MDS also, I am afraid MDS will ask OST to precreate too rare. It may cause several different problems. For example OST after failover needs to precreate more objects that takes extra time(500 000 instead of 20 000).

I suggest to use the 2nd approach with commit callback and revert https://review.whamcloud.com/33833.
I will push a patch.

[Andreas Dilger]

I think that this is not a full solution to the problem, and is causing a lot of test failures for conf-sanity test_69 for OSTs that do not have 500k free inodes.

I think there are two problems with the patch that was landed:

• this essentially is changing OST_MAX_PRECREATE on the OST side, but not on the MDS, so isn't properly handling the recovery
• the root of the problem is not the number of objects created per RPC but rather the number of objects created per commit

I don't mind to have a change that is increasing the maximum number of objects created per commit, but this needs to be negotiated between the MDS and OSS at connect time, with a new OBD_CONNECT2_MAX_PRECREATE flag and an ocd_max_precreate field (probably using __u32 padding1) that passes the current OST_MAX_PRECREATE value, and use OST_MAX_PRECREATE_OLD = 20000 if the feature is not available. This also allows fixing the problem properly in older releases.

Until this is fixed (and even afterward), the proper solution is to track on the OST how many objects have been created by each MDT/sequence within the current transaction (use a commit callback to reset the "created this transaction" counter to zero), and force a sync journal commit during precreate if the number exceeds OST_MAX_PRECREATE. If there are multiple MDTs creating, or the create rate is not too large, or if the clients do some IO and force a transaction commit anyway, then there is no need for a commit. This also avoids the future bug when 500k+ precreates can happen within a single commit, since we are already over 150k/s creates on the MDS, and that is processing separate RPCs while the OST is in a fast local loop precreating objects.

I was going to say that the if (diff > 500000) check in ofd_create_hdl() could be modified to also check if LAST_ID < 5 or similar, to detect if this is a newly-formatted filesystem, but I realize that this case may also happen if e.g. the OST is restored from a backup or a snapshot and has an old LAST_ID but is not new. It would be useful to update the comment to reflect this.

[Peter Jones]

Landed for 2.13

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/33833/
Subject: LU-11760 ofd: formatted OST recognition change
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: d07d9c5ed0aa1d6614944c7d1e0ca55cba301dc4

[Gerrit Updater]

Sergey Cheremencev ([e-mail]) uploaded a new patch: https://review.whamcloud.com/33833
Subject: LU-11760 ofd: formatted OST recognition change
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 829732b1fd8f11e4a4aa5bc7ef6509c4aa771dc3

[Sergey Cheremencev]

The reason of failures is uncommitted journal transaction.
By default jbd2 commits transaction each 5 seconds or in case when journal buffers are full.
Create of one object doesn't need a lot of space(inode size + direntry). Thus usually under mdtest load
journal buffers don't become full and commit is occurred every 5 seconds.
In respect that OST creates objects asynchronously(except several rare cases), we can get a situation
when MDS think that successfully created 100 000 objects despite these objects are not written to disk(OST side) .
In case of failover these uncommitted objects could be lost and should be recreated after establishing connection from OST to MDT.
MDT sends LAST_ID to OST and it should recreate missing object.
This scheme works fine for a long time however there is exclusion for the case when the difference between MDS_Last_ID and OST_Last_ID is bigger then 100 000 (5 * OST_MAX_PRECREATE).

                /* This can happen if a new OST is formatted and installed
                 * in place of an old one at the same index.  Instead of
                 * precreating potentially millions of deleted old objects
                 * (possibly filling the OST), only precreate the last batch.
                 * LFSCK will eventually clean up any orphans. LU-14 */
                if (diff > 5 * OST_MAX_PRECREATE) {
                        diff = OST_MAX_PRECREATE / 2; 
                        LCONSOLE_WARN("%s: Too many FIDs to precreate "
                                      "OST replaced or reformatted: "
                                      "LFSCK will clean up",
                                      ofd_name(ofd)); 

In such case It decides OST is formatted and recreates only last 10 000. For us it means we can have huge gaps in OST objects.
I think 100 000 constant was actual for old systems and should be revised.