On 6/25/19 12:46 AM, Chris Murphy wrote:
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]
Seeing that this is apparently *rc2* (which is insane to ship) the explanation for the above is that 5.2-rc2 was tagged on 2019-05-26, but the patch for the above problem [1] was committed *after* that, on 2019-05-28. That may or may not explain the reason for the original error and its corruption, but whatever you're doing, stop running that kernel.. -h [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fee13fe96529523a709d1fff487f14a5e0d56d34
