[LU-13797] quiet e2fsck "extent tree (at level 1) could be narrower" message Created: 17/Jul/20 Updated: 14/Dec/20 Resolved: 14/Dec/20 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Andreas Dilger | Assignee: | WC Triage |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | e2fsck | ||
| Issue Links: |
|
||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
The e2fsck error "Inode 4457806 extent tree (at level 1) could be narrower. Optimize<y>?" can be very noisy (many thousands of lines), and doesn't really improve filesystem performance in any significant way (typically saving a few extent index blocks for files that were written with holes that were later filled in). It would be better to change the e2fsck default to not optimize the extents, to avoid confusing users with a lot of messages and giving them worries that their filesystem is corrupted. I've discussed this with Ted already, and he agrees that this is an acceptable change. |
| Comments |
| Comment by Gerrit Updater [ 12/Dec/20 ] |
|
Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/40952 |
| Comment by Bob Hawkins [ 14/Dec/20 ] |
|
Please use spelling "spurious" in the new e2fsck.conf comment line. |
| Comment by Gerrit Updater [ 14/Dec/20 ] |
|
Andreas Dilger (adilger@whamcloud.com) merged in patch https://review.whamcloud.com/40952/ |
| Comment by Andreas Dilger [ 14/Dec/20 ] |
You are right, but I didn't see this comment until after I landed the patch. The right place for the comment would be on the patch itself. There is a "Register" link at the top of every page to create an account, and we're happy to have more patch reviewers, especially for things like user interfaces, documentation, etc. |