[LU-8763] LustreError: 18461:0:(update_records.c:72:update_records_dump()) after lctl abort_recovery Created: 26/Oct/16 Updated: 16/Feb/17 Resolved: 07/Nov/16 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.8.0 |
| Fix Version/s: | Lustre 2.9.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Olaf Faaland | Assignee: | Lai Siyao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | llnl, patch | ||
| Environment: |
lustre-2.8.0_3.chaos-1.ch6.x86_64 |
||
| Issue Links: |
|
||||
| Severity: | 3 | ||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
After running lctl abort_recovery on an MDT, lustre starts reporting the following on the console: 2016-10-15 15:50:52 [ 1161.390842] LustreError: 18461:0:(update_records.c:72:update_records_dump()) master transno = 4295056926 batchid = 35538 flags = 0 ops = 42 params = 32 2016-10-15 15:50:52 [ 1161.408040] LustreError: 18461:0:(update_records.c:72:update_records_dump()) master transno = 4295056931 batchid = 35542 flags = 0 ops = 42 params = 32 In one case there were about 30,000 such messages. In another case there were about 80,000 such messages. |
| Comments |
| Comment by John Hammond [ 26/Oct/16 ] |
|
I think we can remove the calls to dtrq_list_dump(). These are not useful error messages. |
| Comment by Joseph Gmitter (Inactive) [ 26/Oct/16 ] |
|
Hi Lai, Can you please look at making these changes? Thanks. |
| Comment by Gerrit Updater [ 27/Oct/16 ] |
|
Olaf Faaland-LLNL (faaland1@llnl.gov) uploaded a new patch: http://review.whamcloud.com/23444 |
| Comment by Olaf Faaland [ 27/Oct/16 ] |
|
Please label this ticket topllnl, thank you. My patch is the most naive possible interpretation of John's comment; please take a look. |
| Comment by Gerrit Updater [ 07/Nov/16 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/23444/ |
| Comment by Peter Jones [ 07/Nov/16 ] |
|
Landed for 2.9 |