Bug #12828
ReplicatedBackend: populate recovery_info.size for clone (bug symptom is size mismatch on replicated backend on a clone in scrub)
0%
Description
This apparently never got filled in. It wasn't actually a problem since we do populate the the copy and clone subsets and the size is really only used for that. However, we now use the size to truncate out to the right size for the case where the end of the file is a hole (b5381c22a7b0d8d4c14cd8feb3a115f7d80d5d81). This didn't actually cause a failure until wip-proxy-write merged with a bug in ceph-test-rados causing an empty write past the end of the file resulting in such a hole.
Related issues
Associated revisions
ReplicatedBackend::prepare_pull: set recover_info.size for clones
Fixes: #12828
Signed-off-by: Samuel Just <sjust@redhat.com>
ReplicatedBackend::prepare_pull: set recover_info.size for clones
Fixes: #12828
Signed-off-by: Samuel Just <sjust@redhat.com>
(cherry picked from commit 1d3e46bedb9a8c0d2200e39f62f4e2c3337619f3)
History
#1 Updated by Samuel Just over 8 years ago
https://github.com/ceph/ceph/pull/5706
I'm out of town until 9/14
#2 Updated by Samuel Just over 8 years ago
/a/samuelj-2015-08-26_12:18:34-rados-wip-sam-testing-distro-basic-multi/1033873/remote
#3 Updated by Samuel Just over 8 years ago
- Assignee deleted (
Samuel Just)
#4 Updated by Sage Weil over 8 years ago
- Status changed from 7 to Resolved
#5 Updated by Sage Weil over 8 years ago
- Status changed from Resolved to Pending Backport
- Backport set to hammer
#6 Updated by Loïc Dachary over 8 years ago
#7 Updated by Loïc Dachary over 8 years ago
- Status changed from Pending Backport to Resolved