diff options
| author | Kent Overstreet <kent.overstreet@linux.dev> | 2023-11-25 05:51:45 +0300 |
|---|---|---|
| committer | Kent Overstreet <kent.overstreet@linux.dev> | 2023-11-26 05:48:42 +0300 |
| commit | 7d9f8468ff7589073981b3eb8b175945c7dcd13c (patch) | |
| tree | 476fc1bf41080fb88acfc5203974ddd91ee7b1af /fs/bcachefs/errcode.h | |
| parent | 0af8a06a4ce823e380385cdd9538cdd968a1ffae (diff) | |
| download | linux-7d9f8468ff7589073981b3eb8b175945c7dcd13c.tar.xz | |
bcachefs: Data update path won't accidentaly grow replicas
Previously, there was a bug where if an extent had greater durability
than required (because we needed to move a durability=1 pointer and
ended up putting it on a durability 2 device), we would submit a write
for replicas=2 - the durability of the pointer being rewritten - instead
of the number of replicas required to bring it back up to the
data_replicas option.
This, plus the allocation path sometimes allocating on a greater
durability device than requested, meant that extents could continue
having more and more replicas added as they were being rewritten.
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Diffstat (limited to 'fs/bcachefs/errcode.h')
| -rw-r--r-- | fs/bcachefs/errcode.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/bcachefs/errcode.h b/fs/bcachefs/errcode.h index 68a1a96bb7ca..69b0627c2180 100644 --- a/fs/bcachefs/errcode.h +++ b/fs/bcachefs/errcode.h @@ -162,7 +162,7 @@ x(BCH_ERR_fsck, fsck_repair_unimplemented) \ x(BCH_ERR_fsck, fsck_repair_impossible) \ x(0, restart_recovery) \ - x(0, unwritten_extent_update) \ + x(0, data_update_done) \ x(EINVAL, device_state_not_allowed) \ x(EINVAL, member_info_missing) \ x(EINVAL, mismatched_block_size) \ |