[LU-3280] when lock->l_lvb_data is freed, LDLM_FL_LVB_READY is not cleared Created: 06/May/13 Updated: 05/Aug/20 Resolved: 08/May/13 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.4.0 |
| Fix Version/s: | Lustre 2.4.0 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | CEA | Assignee: | Jinshan Xiong (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | MB | ||
| Severity: | 3 |
| Rank (Obsolete): | 8117 |
| Description |
|
in ldlm_lock_decref_internal() when l_lvb_data is freed to reduce memory consumption, LDLM_FL_LVB_READY is not cleared, so later when the lock is reused lvb is never updated. We hit this case after a restore in HSM. |
| Comments |
| Comment by jacques-charles lafoucriere [ 06/May/13 ] |
|
patch at http://review.whamcloud.com/6268 |
| Comment by Andreas Dilger [ 06/May/13 ] |
|
Jinshan, can you please take a look at this bug and see whether this will affect normal usage in 2.4.0, or does it only affect HSM? |
| Comment by Jinshan Xiong (Inactive) [ 06/May/13 ] |
|
Yes, it will affect normal usage of 2.4 because the inode can be purged by kernel but the corresponding layout lock can still exist. We should include this in 2.4. |
| Comment by Jodi Levi (Inactive) [ 08/May/13 ] |
|
Closing ticket as patch landed to master. If more work is needed, please let me know and I'll reopen. |