On 08/01/2020 17:41, philip@xxxxxxxxxxxxxxxx wrote: > A bad drive caused i/o errors, but no notifications were sent out > because "btrfs dev stats" fails to increase the error counter. > > When checking dmesg, looking for something completely different, there > were some error messages indicating that this drive is causing i/o > errors and may die soon: > > BTRFS info (device sda3): read error corrected: ino 194473 off 2170880 I am not convinced that that message is telling you that the error happened on device sda3. Certainly in some other cases Btrfs error messages identify the **filesystem** using the name of the device the kernel thinks is mounted, which might be sda3. > But checking the stats (as generally recommended to get notified about > such errors) claims that no errors have occurred (nothing to see here, > keep moving): > > # btrfs dev stats / | grep sda3 | grep read > [/dev/sda3].read_io_errs 0 Have you checked the stats for the other devices as well?
