[LU-13465] Interop 2.12 <-> master sanity test_27A: lfs setstripe: setstripe error for '/mnt/lustre': Unknown error 524

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.14.0
• Severity: 3
• Assignee: Sebastien Buisson
• Reporter: Maloo

Description

This issue was created by maloo for S Buisson <[e-mail]>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/3a01b782-5c68-42bc-a3a6-207b7413418e

test_27A failed with the following error:

lfs setstripe: setstripe error for '/mnt/lustre': Unknown error 524

The test stops on a different error (error deleting stripe '/mnt/lustre'), but the original problem happens at the very beginning of the test, when the striping cannot be set, with the error:

lfs setstripe: setstripe error for '/mnt/lustre': Unknown error 524

In the client's console, we can see the following message:

[ 1579.789018] LustreError: 11-0: MGC10.9.4.89@tcp: operation mgs_set_info to node 10.9.4.89@tcp failed: rc = -524

And in MGS console, we have:

[ 1497.640748] LustreError: 13035:0:(tgt_handler.c:626:tgt_handler_find_check()) MGS: unsupported opcode 0xff

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity test_27A - error deleting stripe '/mnt/lustre'

Issue Links

• is related to: LU-13430 Rework __vfs_getxattr/__vfs_setxattr/__vfs_removexattr support

Comments

[Peter Jones]

Landed for 2.14

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/38301/
Subject: LU-13465 vfs: make ll_vfs_setxattr return -EOPNOTSUPP
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: b4d061dfa6d8a80020925c20e81b26a766509bf5

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/38311/
Subject: LU-13465 mgs: re-introduce mgs_set_info for interop purpose
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 5501c414dc13a01004825a532079cbb21a036cc4

[Gerrit Updater]

Sebastien Buisson ([e-mail]) uploaded a new patch: https://review.whamcloud.com/38311
Subject: LU-13465 mgs: re-introduce mgs_set_info for interop purpose
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: df9f281b0c6828709bf12ff627146e0a41e9294c

[Gerrit Updater]

Sebastien Buisson ([e-mail]) uploaded a new patch: https://review.whamcloud.com/38301
Subject: LU-13465 vfs: make ll_vfs_setxattr return -EOPNOTSUPP
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 2b10ac5a2dcf8cea9bc7205c210361f41e29fb4a

[Andreas Dilger]

The "524" error may be from lustre/include/lustre_errno.h:

#define LUSTRE_ENOTSUPP         524     /* Operation is not supported */

It looks like this is a defect in the recently landed patch https://review.whamcloud.com/38175 "LU-13430 vfs: add ll_vfs_getxattr/ll_vfs_setxattr compat macro", which is using "-ENOTSUPP" instead of "-EOPNOTSUPP"? The llapi_layout_get_by_fd() code checks for "-EOPNOTSUPP" and handles this specially.

Also, I'm guessing that the case of missing i_op->setxattr() and i_op->getxattr() in the compat macros should be marked unlikely()? Both Lustre and ext4 have these methods, and the check is mostly only useful for PCC accessing a cache filesystem that does not have xattr support.