[LU-11928] Noisy "mdt_attr_valid_xlate()) Unknown attr bits: 0x60000"

• Type: Bug
• Resolution: Duplicate
• Priority: Major
• Affects Version/s: Lustre 2.7.0, Lustre 2.10.5
• Severity: 3
• Assignee: Aurelien Degremont (Inactive)
• Reporter: Aurelien Degremont (Inactive)

Description

When testing 2.12.0 clients against 2.10.5 servers, the server log was filled up by this kind of message: 

LustreError: 14950:0:(mdt_lib.c:961:mdt_attr_valid_xlate()) Unknown attr bits: 0x60000
LustreError: 14950:0:(mdt_lib.c:961:mdt_attr_valid_xlate()) Skipped 3853 previous similar messages

 

2.12 clients are sending RPC with LSOM attributes, matching this 0x60000, that 2.10 servers do not understand. The error looks more to me like a warning as the server will simply ignore the LSOM attributes.

static __u64 mdt_attr_valid_xlate(__u64 in, struct mdt_reint_record *rr,
                                  struct md_attr *ma)
{

            ...

            in &= ~(MDS_ATTR_MODE | MDS_ATTR_UID | MDS_ATTR_GID | MDS_ATTR_PROJID |
                MDS_ATTR_ATIME | MDS_ATTR_MTIME | MDS_ATTR_CTIME |
                MDS_ATTR_ATIME_SET | MDS_ATTR_CTIME_SET | MDS_ATTR_MTIME_SET |
                MDS_ATTR_SIZE | MDS_ATTR_BLOCKS | MDS_ATTR_ATTR_FLAG |
                MDS_ATTR_FORCE | MDS_ATTR_KILL_SUID | MDS_ATTR_KILL_SGID |
                MDS_ATTR_FROM_OPEN | MDS_OPEN_OWNEROVERRIDE);
            if (in != 0)
                CERROR("Unknown attr bits: %#llx\n", in);
            return out;
}

 

I think we should make that at least a warning, of even maybe a debug.

What do you think? I can send a patch for that, based on your preference.

 

Issue Links

• is duplicated by: LU-12021 Error message of mdt_attr_valid_xlate() when 2.12 client to 2.10 server

Comments

[Andreas Dilger]

Patch is under LU-12021 so let's use that for tracking.

[Andreas Dilger]

There is already a patch https://review.whamcloud.com/34343 "LU-12021 lsom: Add an OBD_CONNECT2_LSOM connect flag". This is the only way to avoid this constant error on any old MDS from a new client without adding patches to all the old releases. The connect flag can be used for a few years and dropped eventually, as we've done with other flags. It would be good to still quiet the error message on the MDS so that we don't get this problem again in the future.

[Aurelien Degremont (Inactive)]

Try to find some time to do them.

Andreas, does this make sense to you:

> add the lazy flags to the list of known flags, so we quiet these specific errors, but are notified future errors

Add them to the `in` list in `mdt_attr_valid_xlate()` for 2.10 LTS?

> quiet the error message to not print to the console. I don't think marking it a warning is helpful

Replace `CERROR(...)` with `CDEBUG(D_INFO, ...)` in `mdt_attr_valid_xlate()` for 2.10 LTS, 2.12 LTS and master?

> add an OBD_CONNECT_LSOM flag so that clients don't send these flags to older servers that don't support it

A patch for master and maybe a backport for 2.12 ? Does it look like a bit overkill to add a connect flag for that?

 

[Peter Jones]

degremoa do you still plan to submit a patch for this?

[Stephane Thiell]

Just a quick note to say that we're seeing the same error messages on Lustre 2.8 servers (Regal, old system, EOL in 6 months so won't upgrade anymore) and Oak (Lustre 2.10, no problem to upgrade). The errors cannot be seen on Fir servers (Lustre 2.12, Regal's replacement). The logs started when we first upgraded our first clients to 2.12. Example on Regal's MDS:

LustreError: 6605:0:(mdt_lib.c:876:mdt_attr_valid_xlate()) Unknown attr bits: 0x60000
LustreError: 6605:0:(mdt_lib.c:876:mdt_attr_valid_xlate()) Skipped 2012250 previous similar messages

That was only with a handful of clients, but we're upgrading all our clients (~1,400) to 2.12 today so let's hope that this won't have a significant impact on MDT performance.

[Andreas Dilger]

I agree that this shouldn't be spewing on the console. I think there are a few options, possibly more than one is useful to add:

• add the lazy flags to the list of known flags, so we quiet these specific errors, but are notified future errors
• quiet the error message to not print to the console. I don't think marking it a warning is helpful
• add an OBD_CONNECT_LSOM flag so that clients don't send these flags to older servers that don't support it