Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 1
    I've come across this too and would like a generic solution to limit the kernel module itself, as opposed to a specific userland process utilising btrfs, either at the interface to the disk, or at the interface from userland to the fs syscalls. It happens for me if I use old HDDs with slow seek times and then try to do a massive amount of simultaneous reads. I think it's a bug in btrfs where it allows and queues up too many requests, and they take too long to fulfill so it goes into read only mode, throws the generic IO error, and you have to remount the array (I've been doing this for years). Commented Jan 2 at 0:48
  • The error message could indicate a hardware problem under heavy load: disk or cables or ... Commented Jan 2 at 16:34