[LU-3312] Interop 2.1.5<->2.4 failure on test suite sanity test_27z: FAIL: FF stripe 0x2000013a0:0x1b2f0:0x0] != 0

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.1.6
• Affects Version/s: Lustre 2.4.0
• Environment: server: 2.1.5; client: lustre-master build #1481
• Severity: 3
• Assignee: James Nunez (Inactive)
• Reporter: Maloo

Description

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

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/a00f384c-b88e-11e2-891d-52540035b04c.

The sub-test test_27z failed with the following error:

test_27z failed with 5

Info required for matching: sanity 27z

Comments

[Sarah Liu]

Also hit this problem when running interop between 2.3.0 server and 2.5 client:

https://maloo.whamcloud.com/test_sets/4926deda-02b8-11e3-a4b4-52540035b04c

[James Nunez (Inactive)]

This ticket/failure was corrected by patch http://review.whamcloud.com/6468 with the addition of stripe count to the end of the output of ll_decode_filter_fid.

I verified that test 27z passes with master clients and 2.1.6-RC2 servers.

[James Nunez (Inactive)]

In 2.3.64, stripe was added to the output of ll_decode_filter_fid. The output looks like

/mnt/ost5/O/0/d2/28610: parent=[0x2000013a0:0xad:0x0] stripe=5

Before 2.3.64, the output of ll_decode_filter_fid didn't print stripe:

/mnt/ost1/O/0/d2/2946: objid=2946 seq=0 parent=[0x2000059f0:0x29:0x0]

A solution for interop tests to stop failing is just not parse stripe from ll_decode_filter_fid output and don't check against the getstripe output.

[Andreas Dilger]

This is very likely just a problem with the output format for test_27z. Several fixes have been made to this test already, but it needs some more work for interop I guess.