[LU-2857] 2.1.4<->2.4.0 interop: sanity test_76: FAIL: inode slab grew from 11183 to 12183

• Type: Bug
• Resolution: Fixed
• Priority: Major
• Fix Version/s: Lustre 2.1.5
• Affects Version/s: Lustre 2.3.0, Lustre 2.4.0, Lustre 2.1.4, Lustre 1.8.9
• Labels: yuc2

Environment

Lustre b2_1 client build: http://build.whamcloud.com/job/lustre-b2_1/176
Lustre master server build: http://build.whamcloud.com/job/lustre-master/1269
Distro/Arch: RHEL6.3/x86_64

• Severity: 3
• Assignee: WC Triage
• Reporter: Jian Yu

Description

The sanity test 76 failed as follows:

== sanity test 76: confirm clients recycle inodes properly ====== 01:56:01 (1361526961)
before inodes: 11183
after inodes: 12183
wait 2 seconds inodes: 12183
wait 4 seconds inodes: 12183
wait 6 seconds inodes: 12183
wait 8 seconds inodes: 12183
wait 10 seconds inodes: 12183
wait 12 seconds inodes: 12183
wait 14 seconds inodes: 12183
wait 16 seconds inodes: 12183
wait 18 seconds inodes: 12183
wait 20 seconds inodes: 12183
wait 22 seconds inodes: 12183
wait 24 seconds inodes: 12183
wait 26 seconds inodes: 12183
wait 28 seconds inodes: 12183
wait 30 seconds inodes: 12183
wait 32 seconds inodes: 12183
 sanity test_76: @@@@@@ FAIL: inode slab grew from 11183 to 12183

Maloo report: https://maloo.whamcloud.com/test_sets/8b6bd050-7d77-11e2-85d0-52540035b04c

Issue Links

• is duplicated by: LU-2036 sanity.sh test_76: fails with lod/osp (inodes are not purged as expected)
• is related to: LU-10131 Update inode attributes on unlink

Comments

[Andreas Dilger]

Fixed via LU-10131.

[Andreas Dilger]

Per Patrick's comment in LU-2036:

This appears to be fixed by:
https://jira.hpdd.intel.com/browse/LU-10131
https://review.whamcloud.com/#/c/29651/

Test passes with that patch, fails without it.

[Peter Jones]

That's what the always_except lable is used for atm

[James A Simmons]

I purpose that a special tracker ticket be created that covers all the excepted test. This way these types of tickets will not get lost.

[Andreas Dilger]

James, I'm appreciative that you are closing old tickets, but in this case (maybe others) that are marked "always_except" it means the test that is failing has been excluded from the test list, but as James Nunez reported for 2.8.0 the test is still failing, and it does not mean that this bug is fixed.

Either the test needs to be fixed by a code or test script fix, or if the decision is that the tested functionality is obsolete then the test should be removed completely.

[James A Simmons]

Old ticket for unsupported version

[parinay v kondekar (Inactive)]

This issue is also seen on Seagate Test infrastructure quite regularly.
Client - 2.4.3, 2.5.1.x6
Server - 2.5.1.x6

[James Nunez (Inactive)]

sanity test 76 is still failing on master (pre-2.8.0). Recent result with logs is at https://testing.hpdd.intel.com/test_sets/7a914250-e8a1-11e4-b3c6-5254006e85c2

[Jian Yu]

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 76 hit the same failure:
https://maloo.whamcloud.com/test_sets/3c82ea6e-685e-11e3-a16f-52540035b04c

[Jian Yu]

Lustre client build: http://build.whamcloud.com/job/lustre-b1_8/258/ (1.8.9-wc1)
Lustre server build: http://build.whamcloud.com/job/lustre-b2_4/44/ (2.4.1 RC1)

sanity test 76 hit the same failure:
https://maloo.whamcloud.com/test_sets/77da1820-15ad-11e3-87cb-52540035b04c