bcachefs: Cached pointers should not be erasure coded

Browse source

There's no reason to erasure code cached pointers: we'll always have
another copy, and it'll be cheaper to read the other copy than do a
reconstruct read. And erasure coded cached pointers would add
complications that we'd rather not have to deal with, so let's make sure
to disallow them.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>

...

This commit is contained in:

Kent Overstreet 2023-02-21 19:22:44 -05:00

parent e094beccc1

commit c9163bb03b

3 changed files with 37 additions and 3 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

6

fs/bcachefs/data_update.c

View file

32

fs/bcachefs/extents.c

View file

2

fs/bcachefs/extents.h

View file