[LU-3554] 2.4.0<->2.3 interop: sanity test 233: FAIL: cannot access /mnt/lustre using its FID '[0xfc10c:0xed828a32:0x0]'

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 2.4.0
• Fix Version/s: Lustre 2.4.1, Lustre 2.5.0
• Type: Bug
• Priority: Minor
• Reporter: Jian Yu
• Assignee: Keith Mannthey (Inactive)
• Resolution: Fixed

Environment

Lustre server build: https://build.whamcloud.com/job/lustre-chris/25/
Lustre client build: http://build.whamcloud.com/job/lustre-b2_4/13/

• Severity: 3

Description

sanity test 233 failed as follows:

== sanity test 233: checking that OBF of the FS root succeeds == 21:44:37 (1372826677)
stat: cannot stat `/mnt/lustre/.lustre/fid/[0xfc10c:0xed828a32:0x0]': Invalid argument
 sanity test_233: @@@@@@ FAIL: cannot access /mnt/lustre using its FID '[0xfc10c:0xed828a32:0x0]' 

Dmesg on client node showed that:

Lustre: DEBUG MARKER: == sanity test 233: checking that OBF of the FS root succeeds == 21:44:37 (1372826677)
LustreError: 73818:0:(dir.c:433:ll_get_dir_page()) read cache page: [0x200000002:0x2:0x0] at 0: rc -1
LustreError: 73818:0:(dir.c:595:ll_dir_read()) error reading dir [0x200000002:0x2:0x0] at 0: rc -1
Lustre: DEBUG MARKER: /usr/sbin/lctl mark  sanity test_233: @@@@@@ FAIL: cannot access \/mnt\/lustre using its FID \'[0xfc10c:0xed828a32:0x0]\' 

Dmesg on MDS node showed that:

Lustre: DEBUG MARKER: == sanity test 233: checking that OBF of the FS root succeeds == 21:44:37 (1372826677)
Lustre: 126270:0:(mdd_device.c:880:obf_lookup()) mdd_obd-lustre-MDT0000: [0xfc10c:0xed828a32:0x0] is invalid, sequence should be >= 0x200000400
Lustre: DEBUG MARKER: /usr/sbin/lctl mark  sanity test_233: @@@@@@ FAIL: cannot access \/mnt\/lustre using its FID \'[0xfc10c:0xed828a32:0x0]\' 

Maloo report:
https://maloo.whamcloud.com/test_sets/9ed1db56-e3a4-11e2-9137-52540035b04c

The sanity test 233 was added by patch http://review.whamcloud.com/6209 which was not on Lustre b2_3 branch.

Comments

[Keith Mannthey (Inactive)]

It seems both test_233 and test_185 failed and this is due to advanced features in the 2.4 server.

I setup some patches for 2.4 (and they should end up in Master) to do a quick mds server version check before running sanity test 233.

Patch for 233:
http://review.whamcloud.com/6890

Patch for 185:
http://review.whamcloud.com/6891

[Keith Mannthey (Inactive)]

A master patch for 233 can be seen here: http://review.whamcloud.com/7324

Test 185 is fixed in Master by http://review.whamcloud.com/#/c/6887/

[Peter Jones]

Landed for 2.4.1 and 2.5.0