Same call trace on ro mount and ro scrub with 5.2.0-rc2+, but also an
additional call trace related to zstd. As this is a zstd compressed
file system, it might be related.
[ 366.319583] ================================
[ 366.325036] WARNING: inconsistent lock state
[ 366.330615] 5.2.0-0.rc2.git1.2.fc31.x86_64 #1 Tainted: G W
[ 366.336202] --------------------------------
[ 366.341788] inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
[ 366.347423] swapper/4/0 [HC0[0]:SC1[1]:HE1:SE0] takes:
[ 366.353042] 000000006070e818 (&(&wsm.lock)->rlock){+.?.}, at:
zstd_reclaim_timer_fn+0x26/0x170 [btrfs]
full dmesg for that is here:
https://drive.google.com/open?id=1GJlSExS2xQcplVRyg-hjI47KWR7Vs7iS
I'm going to try to boot off the damaged volume, and use
systemd.debug-shell=1 to see if I can gain access to the system at the
crash point. I'm gonna guess it's this same message, failure to clean
up a transaction due to some prior corruption, and then probably goes
read only.
Chris Murphy
