[LU-15381] Obtain file size information under locks for HSM release Created: 17/Dec/21 Updated: 09/Mar/22 Resolved: 11/Feb/22 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.15.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Qian Yingjin | Assignee: | Qian Yingjin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Severity: | 3 | ||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
In HSM release, it obtains file size and blocks information via @ll_merge_attr without any lock protection, it may get the wrong file size. we found a bug that a HSM restore followed by a HSM release will set the file size with 0 wrongly. |
| Comments |
| Comment by Qian Yingjin [ 17/Dec/21 ] |
|
As we use data version to flush all cache and revoke the locks on all clients, thus we could update the size and block attributes in data version operations (however, it still does not protect with any locks)? By this way, we can avoid the glimpse RPC to get the file size? Will make a patch sooner. |
| Comment by Gerrit Updater [ 24/Dec/21 ] |
|
"Yingjin Qian <qian@ddn.com>" uploaded a new patch: https://review.whamcloud.com/45935 |
| Comment by Gerrit Updater [ 26/Jan/22 ] |
|
"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/45935/ |
| Comment by Peter Jones [ 11/Feb/22 ] |
|
Landed for 2.15 |