[LU-1488] 2.1.2 servers, 1.8.8 clients _mdc_blocking_ast()) ### data mismatch with ino

• Type: Bug
• Resolution: Fixed
• Priority: Major
• Fix Version/s: Lustre 1.8.9
• Affects Version/s: Lustre 1.8.8
• Severity: 3
• Assignee: Yang Sheng
• Reporter: Cliff White (Inactive)

Description

When running 2.1.2 servers with RHEL5/1.8.8 clients, Servers are RHEL6 - seeing this error quite a bit.Test is recovery-scale, but error also observed with other tests.

un 6 09:50:44 ehyperion354 Lustre: Server lustre-MDT0000_UUID version (2.1.1.0) is much newer than client version (1.8.8)
Jun 6 09:50:44 ehyperion354 LustreError: 25302:0:(namei.c:256:ll_mdc_blocking_ast()) ### data mismatch with ino 144115305952584894/0 (ffff8101b4b8e9a0) ns: lustre-MDT0000-mdc-ffff81021762a000 lock: ffff810160e1f400/0x793342fb2430adf9 lrc: 3/0,0 mode: PR/PR res: 8589941618/9406 bits 0x1 rrc: 2 type: IBT flags: 0x2002c90 remote: 0xe77c1b87ad8301fe expref: -99 pid: 25116 timeout: 0
Jun 6 09:50:44 ehyperion354 LustreError: 25116:0:(mdc_locks.c:653:mdc_enqueue()) ldlm_cli_enqueue error: -4
Jun 6 09:50:44 ehyperion354 LustreError: 25116:0:(file.c:3331:ll_inode_revalidate_fini()) failure -4 inode 180355073
Jun 6 09:50:44 ehyperion354 LustreError: 25303:0:(client.c:858:ptlrpc_import_delay_req()) @@@ IMP_INVALID req@ffff810162637400 x1403992855059565/t0 o101->lustre-MDT0000_UUID@192.168.120.126@o2ib:12/10 lens 544/1232 e 0 to 1 dl 0 ref 1 fl Rpc:/0/0 rc 0/0

Issue Links

• Trackbacks: Lustre 2.1.2 release testing tracker Lustre 2.1.2 RC3 Tag: v212RC3 Build:

Comments

[Peter Jones]

Fix landed for b1_8

[Yang Sheng]

I think b1_8 has some issue run on test system, Please take a look for http://review.whamcloud.com/3539 . I just change lustre/ChangeLog. It still failed in same result and it works well when i download the packages on my local box.

[Christopher Morrone (Inactive)]

Alright, thanks!

[Yang Sheng]

I don't think this issue will cause a real problem. We only reference fid_res_name_eq() in ll_mdc_blocking_ast() and just doing a check and output a error message. In fact, it harmless.

[Christopher Morrone (Inactive)]

Is there no way to fix this from the 2.X side?

[Yang Sheng]

Patch upload to http://review.whamcloud.com/3522.

[Yang Sheng]

This issue cause by commit ef8bd11416bae8c03a65682f3a10a4da39922b45. The fid_build_reg_res_name() & fid_res_name_eq() use different way build & compare lu_fid & res. I'll produce a patch to fix it.

[Peter Jones]

Yangsheng will look into this one

[Peter Jones]

Bob

Could you please look into this one?

Thanks

Peter

[James A Simmons]

Just test Lustre 2.2.0 servers with 1.8.8 and I saw the same problem.