diff options
| author | Kent Overstreet <kent.overstreet@linux.dev> | 2025-03-22 16:26:32 -0400 |
|---|---|---|
| committer | Kent Overstreet <kent.overstreet@linux.dev> | 2025-03-24 09:50:37 -0400 |
| commit | 2adfa467347f6e5d8091ecbc45a78cac3d2a2b91 (patch) | |
| tree | c7f6fa14f4b554c57bce8dc8a8954ebc9828e351 /tools/perf | |
| parent | 739200c57384313e688e6945b56782721c29459f (diff) | |
bcachefs: btree node write errors now print btree node
It turned out a user was wondering why we were going read-only after a
write error, and he didn't realize he didn't have replication enabled -
this will make that more obvious, and we should be printing it anyways.
Link: https://www.reddit.com/r/bcachefs/comments/1jf9akl/large_data_transfers_switched_bcachefs_to_readonly/
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
Diffstat (limited to 'tools/perf')
0 files changed, 0 insertions, 0 deletions