On 8/20/19 10:59 PM, Chris Murphy wrote: > On Tue, Aug 20, 2019 at 3:10 PM Peter Chant <p...@petezilla.co.uk> wrote: >> >> Chasing IO errors. BTRFS: error (device dm-2) in >> btrfs_run_delayed_refs:2907: errno=-5 IO failure >> >> >> I've just had an odd one. >> >> Over the last few days I've noticed a file system blocking, if that is >> the correct term, and this morning go read only. This resulted in a lot >> of checksum errors. > > That doesn't sound good. Checksum errors where? A complete start to > finish dmesg is most useful in this case. >
I've just booted, degraded, and the file system went readonly quickly. Is it good to post the dmesg to here, it is 1341 lines? I can do it with all disks if that helps? (or I could run it through grep, but I suspect there is good reason for not doing that.) I'll look at the sysrq stuff, but I'm not likely to hit that right this moment as the system is not really usable in this state and I'm assuming I'll do more harm than good soldiering on. Can't do anything with the systemd stuff as I'm running slackware which does not use it. Also, this is really bad timing, so although I can do stuff with the system for the next day or two I'll need to step away from it for a short while. Thank you, Pete
