[LU-3391] Interop 2.3.0<->2.4 failure on test suite sanity test_154: setxattr should fail Created: 24/May/13  Updated: 25/Feb/16  Resolved: 25/Feb/16

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.3.0
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Maloo Assignee: Nathaniel Clark
Resolution: Won't Fix Votes: 0
Labels: None
Environment:

client: 2.3.0
server: lustre-master tag-2.4.50


Severity: 3
Rank (Obsolete): 8394

 Description   

This issue was created by maloo for sarah <sarah@whamcloud.com>

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/f5f6460c-c409-11e2-a2df-52540035b04c.

The sub-test test_154 failed with the following error:

setxattr should fail.

MDS dmesg shows:

Lustre: DEBUG MARKER: == sanity test 154: Open-by-FID == 16:34:42 (1369352082)
LustreError: 23760:0:(fld_handler.c:169:fld_server_lookup()) srv-lustre-MDT0000: Cannot find sequence 0xf00000400: rc = -5
LustreError: 23760:0:(fld_handler.c:169:fld_server_lookup()) Skipped 1 previous similar message
Lustre: 23760:0:(mdd_device.c:561:obf_lookup()) lustre-MDD0000: bad FID format [f.sanity.154], should be [0x200000400:0x1:0x0]
Lustre: DEBUG MARKER: sanity test_154: @@@@@@ FAIL: setxattr should fail.


 Comments   
Comment by Andreas Dilger [ 24/May/13 ]

It looks like there is a bug in the test script, where it is using the filename instead of the FID for open-by-fid in some cases. Not sure why it is inconsistent.

My guess is the unknown sequence error is because the "fid" that is passed coincidentally has "f" at the start, and somehow gets interpreted as 0xf00000400?

If that is not the case, then there may be a more serious underlying problem, so we'd like some investigation (hopefully today) to determine the root cause.

Comment by Nathaniel Clark [ 28/May/13 ]

In change http://review.whamcloud.com/5298 the prohibition to setxattr on .lustre and .lustre/fid was removed so the 2.3.0 check to ensure it fails is no longer valid for 2.4 MDTs (2.3.64 and following).

Comment by Nathaniel Clark [ 28/May/13 ]

Should I submit a patch on b2_3 to fix this?

Comment by Jian Yu [ 04/Sep/13 ]

Lustre client: http://build.whamcloud.com/job/lustre-b2_3/41/ (2.3.0)
Lustre server: http://build.whamcloud.com/job/lustre-b2_4/44/ (2.4.1 RC1)

sanity test 154 hit the same failure:
https://maloo.whamcloud.com/test_sets/cde5bab8-14f3-11e3-9828-52540035b04c

Comment by Jian Yu [ 19/Dec/13 ]

Lustre client: http://build.whamcloud.com/job/lustre-b2_3/41/ (2.3.0)
Lustre server: http://build.whamcloud.com/job/lustre-b2_4/69/ (2.4.2 RC1)

sanity test 154 hit the same failure:
https://maloo.whamcloud.com/test_sets/3c82ea6e-685e-11e3-a16f-52540035b04c

Generated at Sat Feb 10 01:33:30 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.