* Filesystem Degrades to read Only
@ 2019-12-18 4:23 Rob
0 siblings, 0 replies; only message in thread
From: Rob @ 2019-12-18 4:23 UTC (permalink / raw
To: linux-btrfs
Kernel: 4.19.0
btrfs-progs: 4.20.1
Attempts to write data to the filesystem end up with the system being degraded to read only.
dmesg shows this:
[14544.006701] BTRFS: error (device sdi) in __btrfs_free_extent:6800: errno=-2 No such entry
[14544.006703] BTRFS info (device sdi): forced readonly
[14544.006706] BTRFS: error (device sdi) in btrfs_run_delayed_refs:2935: errno=-2 No such entry
[14544.726934] BTRFS warning (device sdi): Skipping commit of aborted transaction.
Ran a btrfs check:
[2/7] checking extents
ref mismatch on [18366485364736 16384] extent item 1, found 0
backref 18366485364736 root 2 not referenced back 0x56417a8551f0
incorrect global backref count on 18366485364736 found 1 wanted 0
backpointer mismatch on [18366485364736 16384]
owner ref check failed [18366485364736 16384]
ref mismatch on [18366487035904 16384] extent item 0, found 1
tree backref 18366487035904 parent 2 root 2 not found in extent tree
backpointer mismatch on [18366487035904 16384]
ERROR: errors found in extent allocation tree or chunk allocation
[3/7] checking free space cache
cache and super generation don't match, space cache will be invalidated
Should I run a btrfs check repair on the system?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-12-18 4:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-12-18 4:23 Filesystem Degrades to read Only Rob
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.