bcachefs: print op->nonce on data update inconsistency

"nonce inconstancy" is popping up again, causing us to go emergency
read-only.

This one looks less serious, i.e. specific to the encryption path and
not indicative of a data corruption bug. But we'll need more info to
track it down.

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

diff --git a/fs/bcachefs/data_update.c b/fs/bcachefs/data_update.c
index 337494facac6407bd46de34c92a8b8751fcf6b0e..642fbc60ecab1de1b65c8c05e5a25b858652486e 100644 (file)
--- a/fs/bcachefs/data_update.c
+++ b/fs/bcachefs/data_update.c
@@ -340,6 +340,7 @@ restart_drop_extra_replicas:
                        struct printbuf buf = PRINTBUF;
 
                        prt_str(&buf, "about to insert invalid key in data update path");
+                       prt_printf(&buf, "\nop.nonce: %u", m->op.nonce);
                        prt_str(&buf, "\nold: ");
                        bch2_bkey_val_to_text(&buf, c, old);
                        prt_str(&buf, "\nk:   ");