[LU-3369] Interop 2.3.0<->2.4 sanity-scrub test_1a: Expect 'inconsistent', but got '' Created: 20/May/13  Updated: 16/Oct/13  Resolved: 24/May/13

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.4.0, Lustre 2.5.0
Fix Version/s: Lustre 2.4.0, Lustre 2.5.0

Type: Bug Priority: Major
Reporter: Maloo Assignee: nasf (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Environment:

server: 2.3.0
client: lustre-master tag-2.4.50RC1


Severity: 3
Rank (Obsolete): 8335

 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/ccfe0fd8-bf03-11e2-a1b0-52540035b04c.

The sub-test test_1a failed with the following error:

(9) Expect 'inconsistent', but got ''

OST console shows:

11:20:06:Lustre: 19426:0:(lustre_log.h:474:llog_group_set_export()) lustre-OST0000: export for group 0 is changed: 0xffff88007d358c00 -> 0xffff8800793d8000
11:20:06:Lustre: 19426:0:(lustre_log.h:474:llog_group_set_export()) Skipped 13 previous similar messages
11:20:06:Lustre: 19426:0:(llog_net.c:162:llog_receptor_accept()) changing the import ffff88007bc5b000 - ffff8800375d9800
11:20:06:Lustre: 19426:0:(llog_net.c:162:llog_receptor_accept()) Skipped 13 previous similar messages
11:20:06:Lustre: DEBUG MARKER: /usr/sbin/lctl mark  sanity-scrub test_1a: @@@@@@ FAIL: \(9\) Expect \'inconsistent\', but got \'\' 
11:20:06:Lustre: 4924:0:(client.c:1917:ptlrpc_expire_one_request()) @@@ Request  sent has timed out for slow reply: [sent 1368728396/real 1368728396]  req@ffff8800799c1400 x1435215426748837/t0(0) o400->MGC10.10.4.182@tcp@10.10.4.182@tcp:26/25 lens 224/224 e 0 to 1 dl 1368728403 ref 1 fl Rpc:XN/0/ffffffff rc 0/-1
11:20:06:LustreError: 166-1: MGC10.10.4.182@tcp: Connection to MGS (at 10.10.4.182@tcp) was lost; in progress operations using this service will fail
11:20:06:LustreError: 19424:0:(client.c:1125:ptlrpc_import_delay_req()) @@@ IMP_INVALID  req@ffff88007aa7c800 x1435215426748839/t0(0) o101->MGC10.10.4.182@tcp@10.10.4.182@tcp:26/25 lens 328/384 e 0 to 0 dl 0 ref 2 fl Rpc:/0/ffffffff rc 0/-1
11:20:06:LustreError: 19424:0:(client.c:1125:ptlrpc_import_delay_req()) @@@ IMP_INVALID  req@ffff8800799c1400 x1435215426748841/t0(0) o101->MGC10.10.4.182@tcp@10.10.4.182@tcp:26/25 lens 328/384 e 0 to 0 dl 0 ref 2 fl Rpc:/0/ffffffff rc 0/-1
11:20:06:Lustre: Evicted from MGS (at MGC10.10.4.182@tcp_0) after server handle changed from 0x477379a8557fd1e9 to 0x477379a8557fd386
11:20:06:Lustre: MGC10.10.4.182@tcp: Reactivating import
11:20:06:Lustre: MGC10.10.4.182@tcp: Connection restored to MGS (at 10.10.4.182@tcp)
11:20:06:Lustre: DEBUG MARKER: sanity-scrub test_1a: @@@@@@ FAIL: (9) Expect 'inconsistent', but got ''
11:20:06:Lustre: DEBUG MARKER: /usr/sbin/lctl dk > /logdir/test_logs/2013-05-16/lustre-b2_3-el6-x86_64-vs-lustre-master-el6-x86_64--full--2_6_1__1501__-70235156779280-104113/sanity-scrub.test_1a.debug_log.$(hostname -s).1368728404.log;
11:20:06:         dmesg > /logdir/test_logs/2013-05-16/lust


 Comments   
Comment by nasf (Inactive) [ 21/May/13 ]

Lustre-2.3 server does not support initial OI scrub, so test_1a (triggered by Lustre-2.4 client) cannot work. So please ignore sanity-scrub test_1a for the interoperability between Lustre-2.4 client and Lustre-2.3 server.

Comment by Andreas Dilger [ 22/May/13 ]

We want the tests to always pass, rather than have false errors that need to be investigated every time. If sanity-scrub test_1a() is known not to work with 2.3.0 servers, then it should be skipped from within the test_1a() script by checking the server version.

Comment by nasf (Inactive) [ 22/May/13 ]

This is the patch:

http://review.whamcloud.com/#change,6417

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