[LU-6102] OI scrub is triggered during racer test Created: 09/Jan/15 Updated: 23/Jan/15 Resolved: 22/Jan/15 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.7.0 |
| Type: | Bug | Priority: | Critical |
| Reporter: | nasf (Inactive) | Assignee: | nasf (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | MB | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 16980 | ||||||||
| Description |
|
When racer test for DNE2, we found that the OI scrub was triggered unexpectedly. We are not sure whether it is DNE2 patches introduced issue or it is existing bug on master. Lustre: lustre-MDT0002-o: trigger OI scrub by RPC for [0x300000401:0xd9:0x0], rc = 0 [1] Lustre: lustre-MDT0002-o: trigger OI scrub by RPC for [0x300000401:0xd9:0x0], rc = 0 [1] Lustre: lustre-MDT0002-o: trigger OI scrub by RPC for [0x300000401:0xd9:0x0], rc = 0 [1] Lustre: lustre-MDT0002-o: trigger OI scrub by RPC for [0x300000401:0xd9:0x0], rc = 0 [1] Lustre: lustre-MDT0002-o: trigger OI scrub by RPC for [0x300000401:0xd9:0x0], rc = 0 [1] Lustre: lustre-MDT0002-o: trigger OI scrub by RPC for [0x300000401:0xd9:0x0], rc = 0 [1] |
| Comments |
| Comment by Gerrit Updater [ 09/Jan/15 ] |
|
Fan Yong (fan.yong@intel.com) uploaded a new patch: http://review.whamcloud.com/13314 |
| Comment by nasf (Inactive) [ 20/Jan/15 ] |
|
Di, would you please to try the patch in your DNE racer tests to see what will happen? Thanks! |
| Comment by Di Wang [ 20/Jan/15 ] |
|
I tried a few times with this patch, but that problem did not happen again. Not easy to reproduce it for now. |
| Comment by Gerrit Updater [ 22/Jan/15 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/13314/ |
| Comment by Peter Jones [ 22/Jan/15 ] |
|
Landed for 2.7 |
| Comment by nasf (Inactive) [ 23/Jan/15 ] |
|
In fact, this patch is mainly for debug, we still not know the real reason for why OI scrub is trigger during NDE racer test. But because the issue was found on DNE branch, not directly on master, and Di said that he cannot reproduce it any more. We can re-open it until we hit it in the future. |