bcachefs: Fix nochanges/read_only interaction

Browse source

nochanges means "we cannot issue writes at all"; it's possible to go
into a pseudo read-write mode where we pin dirty metadata in memory,
which is used for fsck in dry run mode and doing journal replay on a
read only mount, but we do not want to allow an actual read-write mount
in nochanges mode.

But we do always want to allow early read-write, during recovery - this
patch clarifies that.

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

...

This commit is contained in:

Kent Overstreet 2023-12-23 17:50:29 -05:00

parent 5e32914514

commit 62719cf33c

4 changed files with 18 additions and 15 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

4

fs/bcachefs/fs.c

View file

2

fs/bcachefs/opts.h

View file

4

fs/bcachefs/recovery.c

View file

23

fs/bcachefs/super.c

View file