[LU-3189] Interop b1_8, b2_1, b2_3 -> 2.4+ sanity test_53: FAIL: lustre-OST0000.last_id=0x0:929 ; MDS.last_id=929 Created: 18/Apr/13  Updated: 12/Feb/14  Resolved: 12/Feb/14

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.3.0, Lustre 2.4.0, Lustre 1.8.9, Lustre 2.1.6
Fix Version/s: Lustre 2.6.0, Lustre 2.5.1

Type: Bug Priority: Minor
Reporter: Maloo Assignee: Jian Yu
Resolution: Fixed Votes: 0
Labels: mn1, yuc2

Issue Links:
Related
is related to LU-3196 Ticket for tracking DNE test-script p... Closed
Severity: 3
Rank (Obsolete): 7782

 Description   

This issue was created by maloo for sarah <sarah@whamcloud.com>

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/b80113d6-a767-11e2-a6c0-52540035b04c.

The sub-test test_53 failed with the following error:

lustre-OST0006.last_id=0x0:865 ; MDS.last_id=865

test log shows:

== sanity test 53: verify that MDS and OSTs agree on pre-creation ====== 14:01:49 (1366146109)
CMD: client-13vm3 /usr/sbin/lctl get_param -n version
CMD: client-13vm3 /usr/sbin/lctl get_param -n version
CMD: client-13vm3 lctl get_param osc.*-osc-MDT0000.prealloc_last_id
CMD: client-13vm3 lctl get_param -n osc.lustre-OST0000-osc-MDT0000.prealloc_last_id
CMD: client-13vm4 lctl get_param -n obdfilter.lustre-OST0000.last_id
lustre-OST0000.last_id=0x0:929 ; MDS.last_id=929
 sanity test_53: @@@@@@ FAIL: lustre-OST0000.last_id=0x0:929 ; MDS.last_id=929 
Dumping lctl log to /logdir/test_logs/2013-04-16/lustre-master-el6-x86_64-vs-lustre-b1_8-el6-x86_64--full--2_4_1__1412__-70194522892240-115049/sanity.test_53.*.1366146110.log
CMD: client-13vm1.lab.whamcloud.com,client-13vm2,client-13vm3,client-13vm4 /usr/sbin/lctl dk > /logdir/test_logs/2013-04-16/lustre-master-el6-x86_64-vs-lustre-b1_8-el6-x86_64--full--2_4_1__1412__-70194522892240-115049/sanity.test_53.debug_log.\$(hostname -s).1366146110.log;
         dmesg > /logdir/test_logs/2013-04-16/lustre-master-el6-x86_64-vs-lustre-b1_8-el6-x86_64--full--2_4_1__1412__-70194522892240-115049/sanity.test_53.dmesg.\$(hostname -s).1366146110.log
CMD: client-13vm3 lctl get_param -n osc.lustre-OST0001-osc-MDT0000.prealloc_last_id
CMD: client-13vm4 lctl get_param -n obdfilter.lustre-OST0001.last_id


 Comments   
Comment by Andreas Dilger [ 07/May/13 ]

http://review.whamcloud.com/6106 fixed this problem on master, the sanity.sh test_53 part of it should be landed to b1_8 and b2_1.

Comment by Jian Yu [ 02/Jul/13 ]

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

sanity test 53 failed as follows:

CMD: client-16vm3 lctl get_param -n osc.lustre-OST0006-osc-MDT0000.prealloc_last_seq
client-16vm3: error: get_param: /proc/{fs,sys}/{lnet,lustre}/osc/lustre-OST0006-osc-MDT0000/prealloc_last_seq: Found no match
CMD: client-16vm3 lctl get_param -n osc.lustre-OST0006-osc-MDT0000.prealloc_last_id
CMD: client-16vm4 lctl get_param -n obdfilter.lustre-OST0006.last_id
lustre-OST0006.last_id=1857 ;MDS.last_id=1857
/usr/lib64/lustre/tests/sanity.sh: line 3837: [: 1857: unary operator expected
 sanity test_53: @@@@@@ FAIL: can not match last_seq/last_id for *OST*-osc-MDT0000

Maloo reports:
https://maloo.whamcloud.com/test_sets/2bf3c3f6-e287-11e2-8171-52540035b04c
https://maloo.whamcloud.com/test_sets/0219094e-e0f0-11e2-b3fd-52540035b04c

Comment by Jian Yu [ 14/Aug/13 ]

Lustre client build: http://build.whamcloud.com/job/lustre-b2_1/215/ (2.1.6)
Lustre server build: http://build.whamcloud.com/job/lustre-b2_4/29/

sanity test 53 hit the same failure:
https://maloo.whamcloud.com/test_sets/12a756a6-0474-11e3-a8e9-52540035b04c

Comment by Jian Yu [ 14/Aug/13 ]

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/31/

sanity test 53 hit the same failure:
https://maloo.whamcloud.com/test_sets/03a55dac-0478-11e3-90ba-52540035b04c

Comment by Jian Yu [ 03/Sep/13 ]

Lustre client: http://build.whamcloud.com/job/lustre-b2_1/215/ (2.1.6)
Lustre server: http://build.whamcloud.com/job/lustre-b2_4/44/ (2.4.1 RC1)

sanity test 53 hit the same failure:
https://maloo.whamcloud.com/test_sets/b8534f68-1484-11e3-ac48-52540035b04c

Comment by Jian Yu [ 04/Sep/13 ]

Lustre client: http://build.whamcloud.com/job/lustre-b2_3/41/ (2.3.0)
Lustre server: http://build.whamcloud.com/job/lustre-b2_4/44/ (2.4.1 RC1)

sanity test 53 hit the same failure:
https://maloo.whamcloud.com/test_sets/cde5bab8-14f3-11e3-9828-52540035b04c

Comment by Jian Yu [ 05/Sep/13 ]

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

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

Comment by Jian Yu [ 19/Dec/13 ]

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

Comment by Andreas Dilger [ 13/Jan/14 ]

Instead of continually reporting that this test is failing, why not backport the patch to fix it to b2_4, b2_1, b1_8, or wherever it is needed? Unfortunately, the patch 6106 doesn't look like it should be cherry-picked directly, since it is changing a lot of different tests, but at least the sanity test_53() fix should be backported.

Comment by Jian Yu [ 14/Jan/14 ]

Sorry for the postponed work due to continuous build/release testing. I'll create a patch today.

Comment by Jian Yu [ 14/Jan/14 ]

Patch for master branch: http://review.whamcloud.com/8833
Patch for b2_5 branch: http://review.whamcloud.com/8834
Patch for b2_4 branch: http://review.whamcloud.com/8832
Patch for b2_1 branch: http://review.whamcloud.com/8835
Patch for b1_8 branch: http://review.whamcloud.com/8840

Comment by Jian Yu [ 07/Feb/14 ]

Patches landed on master and b2_5 branches.

Comment by Peter Jones [ 12/Feb/14 ]

Landed for 2.5.1 and 2.6

Generated at Sat Feb 10 01:31:44 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.