[LU-1775] b1_8<->2.3 Test failure on test suite parallel-scale, subtest test_compilebench Created: 20/Aug/12 Updated: 21/Aug/12 Resolved: 21/Aug/12 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.3.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Maloo | Assignee: | Hongchao Zhang |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Environment: |
server: lustre-master-tag2.2.93 RHEL6 |
||
| Severity: | 3 |
| Rank (Obsolete): | 4184 |
| Description |
|
This issue was created by maloo for sarah <sarah@whamcloud.com> This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/6aa7c6e4-e939-11e1-a508-52540035b04c. The sub-test test_compilebench failed with the following error:
Lustre: DEBUG MARKER: /usr/sbin/lctl mark == parallel-scale test compilebench: compilebench == 19:18:31 \(1345256311\) Lustre: DEBUG MARKER: == parallel-scale test compilebench: compilebench == 19:18:31 (1345256311) Lustre: DEBUG MARKER: /usr/sbin/lctl mark .\/compilebench -D \/mnt\/lustre\/d0.compilebench -i 4 -r 4 --makej Lustre: DEBUG MARKER: ./compilebench -D /mnt/lustre/d0.compilebench -i 4 -r 4 --makej LustreError: 21970:0:(namei.c:256:ll_mdc_blocking_ast()) ### data mismatch with ino 144115205356510670/0 (ffff88007ced3550) ns: lustre-MDT0000-mdc-ffff880076906800 lock: ffff880076a5ee00/0x514695a8deadffa0 lrc: 2/0,0 mode: PR/PR res: 8589935622/122318 bits 0x3 rrc: 2 type: IBT flags: 0x2090 remote: 0xfd9936b15a0af713 expref: -99 pid: 21970 timeout: 0 LustreError: 21970:0:(namei.c:256:ll_mdc_blocking_ast()) Skipped 81666 previous similar messages LustreError: 21970:0:(namei.c:256:ll_mdc_blocking_ast()) ### data mismatch with ino 144115205389958238/0 (ffff880037536590) ns: lustre-MDT0000-mdc-ffff880076906800 lock: ffff88005e91bc00/0x514695a8def52a23 lrc: 2/0,0 mode: PR/PR res: 8589935624/15454 bits 0x3 rrc: 4 type: IBT flags: 0x2090 remote: 0xfd9936b15a2df3c4 expref: -99 pid: 21970 timeout: 0 LustreError: 21970:0:(namei.c:256:ll_mdc_blocking_ast()) Skipped 25372 previous similar messages LustreError: 21970:0:(namei.c:256:ll_mdc_blocking_ast()) ### data mismatch with ino 144115205389987242/0 (ffff88005f61f5d0) ns: lustre-MDT0000-mdc-ffff880076906800 lock: ffff88005e244e00/0x514695a8df306351 lrc: 2/0,0 mode: PR/PR res: 8589935624/44458 bits 0x3 rrc: 4 type: IBT flags: 0x2090 remote: 0xfd9936b15a4a8765 expref: -99 pid: 21970 timeout: 0 LustreError: 21970:0:(namei.c:256:ll_mdc_blocking_ast()) Skipped 12690 previous similar messages LustreError: 21970:0:(namei.c:256:ll_mdc_blocking_ast()) ### data mismatch with ino 144115205390019231/0 (ffff88002bda91d0) ns: lustre-MDT0000-mdc-ffff880076906800 lock: ffff88007ac47c00/0x514695a8df6db61a lrc: 2/0,0 mode: PR/PR res: 8589935624/76447 bits 0x3 rrc: 4 type: IBT flags: 0x2090 remote: 0xfd9936b15a6021ce expref: -99 pid: 21970 timeout: 0 LustreError: 21970:0:(namei.c:256:ll_mdc_blocking_ast()) Skipped 1865 previous similar messages LustreError: 21970:0:(namei.c:256:ll_mdc_blocking_ast()) ### data mismatch with ino 144115205390051268/0 (ffff88003b967d10) ns: lustre-MDT0000-mdc-ffff880076906800 lock: ffff880034a62c00/0x514695a8dfabe356 lrc: 2/0,0 mode: PR/PR res: 8589935624/108484 bits 0x3 rrc: 4 type: IBT flags: 0x2090 remote: 0xfd9936b15a75c89a expref: -99 pid: 21970 timeout: 0 LustreError: 21970:0:(namei.c:256:ll_mdc_blocking_ast()) Skipped 1684 previous similar messages SysRq : Show State |
| Comments |
| Comment by Peter Jones [ 20/Aug/12 ] |
|
Hongchao Could you please look into this one? Thanks Peter |
| Comment by Andreas Dilger [ 21/Aug/12 ] |
|
This is a known issue. The "data mismatch with ino 144115205356510670/0" message was the bug that we need to make the 1.8.8 release for... I don't have the Jira ticket number handy, but AFAIK there was a patch for this already, maybe from Yang Sheng. |
| Comment by Hongchao Zhang [ 21/Aug/12 ] |
|
Yes, |
| Comment by Peter Jones [ 21/Aug/12 ] |
|
ok then let's close this as a duplicate. This failure is expected until our interop testing is able to switch to a version of 1.8.x which contains the fix for |