[LU-16306] using multiop to simulate I/O call sequence parsing from Lustre debug log Created: 10/Nov/22 Updated: 18/Aug/23 Resolved: 18/Aug/23 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Qian Yingjin | Assignee: | Qian Yingjin |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
For some I/O application (not open source software) that can be only ran on the customer system, we can only analyze from the Lustre debug log, which makes the debug processing complicated between the customer and developer. It would better that we can reproduce the bug directly according to the Lustre debug log. Thus we propose a mechanism to simulate the I/O call sequences via multiop according to the parsing result from the Lustre debug log and try to reproduce the bug happened on the customer environment. |
| Comments |
| Comment by Gerrit Updater [ 10/Nov/22 ] |
|
"Qian Yingjin <qian@ddn.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/49094 |
| Comment by Andreas Dilger [ 12/Mar/23 ] |
|
Very similar to LU-15367. |
| Comment by Patrick Farrell [ 18/Aug/23 ] |
|
I'm going to merge this with LU-15367, but the patch from Yingjin is very useful, so I'm going to bring that over, not abandon it. |
| Comment by Patrick Farrell [ 18/Aug/23 ] |
|
Duplicate of LU-15367 |