[LU-582] 1.8<->2.1 interop: sanity test_132: FAIL: some glimpse RPC is expected Created: 09/Aug/11 Updated: 09/Apr/13 Resolved: 20/Feb/13 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.0.0, Lustre 2.1.2, Lustre 2.1.3, Lustre 1.8.8, Lustre 1.8.6 |
| Fix Version/s: | Lustre 2.4.0, Lustre 2.1.5 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Jian Yu | Assignee: | Hongchao Zhang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Old Lustre Version: 1.8.6-wc1 New Lustre Version: 2.0.66.0 Clean upgrading (Lustre servers and clients were upgraded all at once) from Lustre 1.8.6-wc1 to Lustre 2.0.66.0 under the following configuration: OSS1: RHEL5/x86_64 |
||
| Attachments: |
|
| Severity: | 3 |
| Bugzilla ID: | 23,339 |
| Rank (Obsolete): | 4234 |
| Description |
|
After the upgrading, sanity test 132 failed on Lustre 2.0.66.0 as follows: == sanity test 132: som avoids glimpse rpc == 03:17:56 (1312885076) ====> SOM is disabled, 0 glimpse RPC occured sanity test_132: @@@@@@ FAIL: some glimpse RPC is expected Please refer to the Maloo report for more logs: https://maloo.whamcloud.com/test_sets/a570d34e-c278-11e0-8bdf-52540025f9af This is an known issue: bug 23339. |
| Comments |
| Comment by James A Simmons [ 23/Aug/11 ] |
|
This is also failing with Lustre 2.1 clients. == sanity test 132: som avoids glimpse rpc =========================================================== 12:59:06 (1314118746) |
| Comment by James A Simmons [ 23/Aug/11 ] |
|
Updated logs for the failure from one of my clients to your ftp site. Its in uploads/ |
| Comment by James A Simmons [ 23/Jan/12 ] |
|
Sanity test 132 no longer fails. Youc an close this ticket. |
| Comment by Peter Jones [ 23/Jan/12 ] |
|
Thanks James! |
| Comment by James A Simmons [ 08/Feb/12 ] |
|
Peter can you reopen this ticket. |
| Comment by Peter Jones [ 08/Feb/12 ] |
|
James Can you please confirm that the 1.8.x client that you are testing with is at least version 1.8.7-wc1 (not the Oracle 1.8.7)? Thanks Peter |
| Comment by James A Simmons [ 08/Feb/12 ] |
|
Originally this ticket reported a interop problem but I noted it that its fails with 2.X clients. It stopped failing but now its fails again with Lustre 2.X clients. prehaps this ticket shoudl be retitled. |
| Comment by Peter Jones [ 08/Feb/12 ] |
|
James I think that a new ticket would be simpler\clearer Peter |
| Comment by Andreas Dilger [ 17/May/12 ] |
|
This is failing 16% of the time currently, with 2.6.18 clients vs. 2.6.32 servers: https://maloo.whamcloud.com/test_sets/35a3f450-9faa-11e1-b416-52540035b04c |
| Comment by Jian Yu [ 07/Jun/12 ] |
|
Old Lustre Version: 1.8.8-wc1 New Lustre Version: 2.1.2 After clean upgrading with the following configuration, sanity test 132 still failed: OSS1: RHEL5/x86_64 OSS2: RHEL5/x86_64 MDS: RHEL5/x86_64 Client1: RHEL6/x86_64 Client2: RHEL6/x86_64 client-1: == sanity test 132: som avoids glimpse rpc == 04:43:30 (1339069410) client-1: ====> SOM is disabled, 0 glimpse RPC occured client-1: sanity test_132: @@@@@@ FAIL: some glimpse RPC is expected client-1: Dumping lctl log to /home/yujian/test_logs/2012-06-07/043300/sanity.test_132.*.1339069414.log client-1: FAIL 132 (5s) Maloo report: https://maloo.whamcloud.com/test_sets/c250c2d6-b0d3-11e1-99ce-52540035b04c |
| Comment by Jay Lan (Inactive) [ 20/Jun/12 ] |
|
Is there a new ticket for 2.x client? |
| Comment by Jian Yu [ 14/Aug/12 ] |
|
After clean upgrading from Lustre 1.8.8-wc1 to 2.1.3 RC1, the issue occurred again: |
| Comment by Hongchao Zhang [ 15/Aug/12 ] |
|
there is indeed glimpse request during calling 'stat $DIR/$tfile' in client-7 00000001:00010000:2.0:1344970176.071156:0:12030:0:(glimpse.c:120:cl_glimpse_lock()) Glimpsing inode [0x20b2735b0:0x1:0x0] in fat-intel-2 00010000:00000001:13.0:1344970176.078486:0:7796:0:(ldlm_lockd.c:1065:ldlm_handle_enqueue0()) Process entered the filter_intent_policy is called! |
| Comment by Hongchao Zhang [ 15/Aug/12 ] |
|
the logs of client and OST |
| Comment by Hongchao Zhang [ 16/Aug/12 ] |
|
Yujian help to reproduce the bug after upgrading Lustre, and the ldlm_glimpse_enqueue is indeed increased. the debug patch is tracked at http://review.whamcloud.com/#change,3692 Hi Yujian, could you please help to test with the debug patch? thanks!! |
| Comment by Jian Yu [ 16/Aug/12 ] |
The real patch is in http://review.whamcloud.com/#change,3693. Testing is ongoing. |
| Comment by Hongchao Zhang [ 17/Aug/12 ] |
|
there is a bug in get_ost_param get_ost_param() { ' | head -n 1) previous, there is only one OSS in autotest, then the problem is hidden, but in upgrade test, there are 2 OSS, |
| Comment by Hongchao Zhang [ 17/Aug/12 ] |
|
the patch has been updated |
| Comment by Jay Lan (Inactive) [ 31/Dec/12 ] |
|
I saw this problem between 2.1.3 server and 2.3.0 client. Let me know if you want the test_logs. |
| Comment by Stephen Champion [ 07/Feb/13 ] |
|
I've been using http://review.whamcloud.com/#change,3693 for |