These messages seem suspicious:
Btrfs detects write errors and forces the filesystem into read-only mode to prevent data corruption:
[ 7020.199614] BTRFS error (device nvme0n1p3): bdev /dev/nvme0n1p3 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0
[ 7020.199614] BTRFS error (device nvme0n1p3): bdev /dev/nvme0n1p3 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0
[ 7020.199614] BTRFS error (device nvme0n1p3): bdev /dev/nvme0n1p3 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0
[ 7020.199614] BTRFS error (device nvme0n1p3): bdev /dev/nvme0n1p3 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0
[ 7020.199642] BTRFS error (device nvme0n1p3): bdev /dev/nvme0n1p3 errs: wr 6, rd 0, flush 0, corrupt 0, gen 0
[ 7020.199642] BTRFS error (device nvme0n1p3): bdev /dev/nvme0n1p3 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0
[ 7020.199669] BTRFS error (device nvme0n1p3): bdev /dev/nvme0n1p3 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0
[ 7020.199673] BTRFS error (device nvme0n1p3): bdev /dev/nvme0n1p3 errs: wr 9, rd 0, flush 0, corrupt 0, gen 0
[ 7020.199682] BTRFS error (device nvme0n1p3): bdev /dev/nvme0n1p3 errs: wr 10, rd 0, flush 0, corrupt 0, gen 0
[ 7020.199683] BTRFS error (device nvme0n1p3): bdev /dev/nvme0n1p3 errs: wr 11, rd 0, flush 0, corrupt 0, gen 0
[ 7020.199700] BTRFS: error (device nvme0n1p3) in btrfs_commit_transaction:2523: errno=-5 IO failure (Error while writing out transaction)
[ 7020.199719] BTRFS info (device nvme0n1p3 state E): forced readonly
[ 7020.199727] BTRFS warning (device nvme0n1p3 state E): Skipping commit of aborted transaction.
[ 7020.199733] BTRFS error (device nvme0n1p3 state EA): Transaction aborted (error -5)
[ 7020.199739] BTRFS: error (device nvme0n1p3 state EA) in cleanup_transaction:2017: errno=-5 IO failure
Run a disk check. I do it with the “nvme” command:
sudo nvme smart-log /dev/nvme0n1