> For example, a read failure may result in printing multiple read errors
in dmesg for each block it is not able to read. An event generated for
each block may be too much for udev to handle.
I don't think user-space is interested about individual errors like on
which block there's an error but that:
- there's a file system error
- which file system has the error
- maybe the types/classes of errors on that file system
I.e. at most the first error of certain type on certain file system should
Btw. Regarding corrupted FAT file system, background file system indexing
daemons sometimes behave in interesting ways when they encounter e.g.
infinite list of directory entries or infinitely deep directory
hierarchies on just mounted FAT file systems... Kernel re-mounting
buggy FS read-only doesn't help in these cases at all. (Such programs are
of course buggy and should be fixed, but it's not always easy to find &
correct such errors in programs beforehand.)