[LU-15082] osp can stop refreshing statfs data Created: 12/Oct/21 Updated: 30/Mar/23 Resolved: 11/Jun/22 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.16.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Alex Zhuravlev | Assignee: | WC Triage |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
there is a race between osp_statfs_timer_cb() and osp_precreate_thread() when the timer callback is called just before statfs data gets stale (according to @opd_statfs_fresh_till) and then woken osp_precreate_thread() finds statfs data valid. essentially it's early-wakeup leading stale statfs data. if no creates happen on this OST for a reason (e.g. current space usage), then statfs data won't be refreshed for a long time. |
| Comments |
| Comment by Gerrit Updater [ 12/Oct/21 ] |
|
"Alex Zhuravlev <bzzz@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/45199 |
| Comment by Gerrit Updater [ 11/Jun/22 ] |
|
"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/45199/ |
| Comment by Peter Jones [ 11/Jun/22 ] |
|
Landed for 2.16 |