Bug #52341
[pwl] m_bytes_allocated is calculated incorrectly on reopen
% Done:
0%
Source:
Tags:
Backport:
pacific
Regression:
No
Severity:
2 - major
Reviewed:
Description
After restart and pwd/ssd cache will load existing entries and calc dirty_data which mean m_bytes_allocated. But the current code is less calculated .
This will cause overwrite which cause dirty-data overwrite by new data and can't flush to osd.
Related issues
History
#1 Updated by Ilya Dryomov over 2 years ago
- Subject changed from After restart, pwl/ssd cache can't calc correctly m_byte_allocated. to [pwl ssd] m_bytes_allocated is calculated incorrectly on reopen
#2 Updated by jianpeng ma over 2 years ago
#3 Updated by Ilya Dryomov over 2 years ago
- Status changed from New to Fix Under Review
- Assignee set to jianpeng ma
- Backport set to pacific
- Pull request ID set to 42883
#4 Updated by Ilya Dryomov over 2 years ago
- Related to Bug #52323: [pwl ssd] incorrect first_valid_entry calculation in retire_entries() added
#5 Updated by Ilya Dryomov over 2 years ago
- Subject changed from [pwl ssd] m_bytes_allocated is calculated incorrectly on reopen to [pwl] m_bytes_allocated is calculated incorrectly on reopen
#6 Updated by Ilya Dryomov over 2 years ago
- Status changed from Fix Under Review to Pending Backport
#7 Updated by Backport Bot over 2 years ago
- Copied to Backport #52569: pacific: [pwl] m_bytes_allocated is calculated incorrectly on reopen added
#8 Updated by Ilya Dryomov about 2 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".