[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