[LU-11721] "lfs df -i" prints used blocks percentage instead of inodes Created: 29/Nov/18 Updated: 11/Jun/19 Resolved: 11/Jun/19 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.11.0 |
| Fix Version/s: | Lustre 2.13.0, Lustre 2.12.3 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Nikitas Angelinas | Assignee: | Nikitas Angelinas |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||
| Severity: | 3 | ||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||
| Description |
|
When issuing an "lfs df -i", the "IUse%" field shows the percentage of used blocks, instead of the percentage of used inodes. |
| Comments |
| Comment by Gerrit Updater [ 29/Nov/18 ] |
|
Nikitas Angelinas (nangelinas@cray.com) uploaded a new patch: https://review.whamcloud.com/33758 |
| Comment by Gerrit Updater [ 30/Jan/19 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/33758/ |
| Comment by Gerrit Updater [ 30/Jan/19 ] |
|
Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/34136 |
| Comment by Peter Jones [ 30/Jan/19 ] |
|
Landed for 2.13 |
| Comment by Gerrit Updater [ 01/Feb/19 ] |
|
Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/34164 |
| Comment by Gerrit Updater [ 02/Feb/19 ] |
|
Andreas Dilger (adilger@whamcloud.com) merged in patch https://review.whamcloud.com/34164/ |
| Comment by Gerrit Updater [ 03/Feb/19 ] |
|
Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/34167 |
| Comment by Andreas Dilger [ 06/Feb/19 ] |
|
This exposed a bug in lod_statfs() vs. ll_statfs_internal() because the new aggregate statfs code in lod_statfs() wasn't reducing the reported free inode counts if the OSTs report fewer total free inodes. |
| Comment by Andreas Dilger [ 12/Feb/19 ] |
|
This issue does not exist in 2.10.6, since it was introduced by the statfs proxy patch in 2.12, so no need to backport the patch. |
| Comment by Gerrit Updater [ 26/Feb/19 ] |
|
Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/34321 |
| Comment by Cory Spitz [ 15/Mar/19 ] |
|
nangelinas, this issue is resolved, but https://review.whamcloud.com/#/c/34167/ from Andreas is still marked in Gerrit as "Needs Code-Review". What should happen with that code? |
| Comment by Nikitas Angelinas [ 15/Mar/19 ] |
|
Reopening until https://review.whamcloud.com/#/c/34167/ lands. |
| Comment by Nikitas Angelinas [ 15/Mar/19 ] |
|
Cory, looking at the ticket history, we seem to have marked the ticket as Resolved after the initial patch that I submitted was landed, but Andreas submitted two additional patches to address an issue with the patch I submitted in DNE, and a related issue it uncovered with statfs aggregation. I am not sure what the process is, but I took the liberty of reopening the ticket until https://review.whamcloud.com/#/c/34167/ lands, which it should, imho. |
| Comment by Peter Jones [ 15/Mar/19 ] |
|
nangelinas - exactly right. Thanks for your eagle eyes spitzcor |
| Comment by Gerrit Updater [ 15/Mar/19 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/34167/ |
| Comment by Peter Jones [ 16/Mar/19 ] |
|
All landed for 2.13 now |
| Comment by Gerrit Updater [ 19/Mar/19 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/34136/ |
| Comment by Gerrit Updater [ 19/Mar/19 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/34321/ |
| Comment by Gerrit Updater [ 19/Mar/19 ] |
|
Minh Diep (mdiep@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/34453 |
| Comment by James Nunez (Inactive) [ 22/Mar/19 ] |
|
We are still seeing sanity test 418 fail with ''df and lfs df inodes output mismatch: ..." on master branch after all these patches have landed. Here are a couple of recent failures: |
| Comment by Gerrit Updater [ 22/Mar/19 ] |
|
Andreas Dilger (adilger@whamcloud.com) uploaded a new patch: https://review.whamcloud.com/34493 |
| Comment by Andreas Dilger [ 22/Mar/19 ] |
|
Looking at the client debug logs for the failure, it doesn't record any statfs RPCs at all during the test, and the exports are all reported IDLE. That should definitely not be the case for "lfs df" and "lfs df -i", since the client needs to contact all targets to get the statfs info. Only the "df" statfs can be aggregated, but it shouldn't be cached more than a second. The MDS logs show some activity, but not any of the actual statfs results, because the debug level is too low. It looks like the test is not running with full debugging enabled as it should for all sanity tests, so I pushed patch 34493 to ensure this is the case, and hopefully we will get some more usable debug logs after that patch lands. |
| Comment by Andreas Dilger [ 22/Mar/19 ] |
|
The actual problem looks mostly to be related to what the 34453 patch was trying to fix - namely that the proxy statfs data returned by "df -i" is not being limited to the number of OST objects in the filesystem as it should. This makes the total and free inodes wildly larger than what "lfs df -i" reports. That patch landed "Fri Mar 15 23:46:21 2019" so it shouldn't be seen in patches that are testing this week unless they haven't been rebased, and I confirmed at least one failure was running a patch that included this fix. There is a second, less common failure mode on ZFS (e.g. maybe 10% of cases) shows the "df -i" output is slightly different than the "lfs df -i". That might be due to e.g. ZFS background activity changing the number of free blocks, which affects the free inode estimate. This is not a problem for ldiskfs. We might have to allow a margin of error in the total and free inodes for ZFS. |
| Comment by Gerrit Updater [ 08/Jun/19 ] |
|
Oleg Drokin (green@whamcloud.com) merged in patch https://review.whamcloud.com/34453/ |
| Comment by Andreas Dilger [ 11/Jun/19 ] |
|
I suspect the last issue was fixed with |