[LU-1266] 2.1.1<->2.2 Test failure on test suite sanity, subtest test_133c Created: 28/Mar/12 Updated: 12/Apr/12 Resolved: 12/Apr/12 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Maloo | Assignee: | WC Triage |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 6426 | ||||||||
| Description |
|
This issue was created by maloo for sarah <sarah@whamcloud.com> This issue relates to the following test suite run: https://maloo.whamcloud.com/test_sets/92ac75da-7905-11e1-8f60-5254004bbbd3. The sub-test test_133c failed with the following error:
debug and dmesg log please see the attached. |
| Comments |
| Comment by Sarah Liu [ 28/Mar/12 ] |
|
debug and dmesg logs |
| Comment by Oleg Drokin [ 28/Mar/12 ] |
|
For some reason that I am not ready to say what was it, clio decided to split this single bunch of pages into two actual io RPCs, one 105 pages in size (xid x1397706881971181) and another one 151 pages in size (xid x1397706881971182). The client log in maloo has a very high debug level set so everything could be tracked precisely. I added Jinshan to CC list if he happens to look into this more deeply before me. This is not a 2.2 blocker in my opinion. |
| Comment by Andreas Dilger [ 12/Apr/12 ] |
|
Duplicates |