You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No I/O error counters in the statistics kept by kernel
The Linux kernel knows when disk IO errors happen and it will tell you about them. But only in the kernel message log, in a format that can vary from disk type to disk type and changes over time.
Some Linux filesystems do have some reporting of errors in sysfs, for example ext4's sysfs entries include an error count and information about the first and most recent errors experienced. But it's not clear what sort of 'errors' these are about, and the information is apparently persisted in the filesystem superblock instead of being transient. You might want to monitor the error count, though.
Problem
Would be nice to show a big fat "volume has serious problems" error in Varasto to alert users on time.
Solution
Look at Linux kernel's I/O error counters per block device.
How to do that?
Block device I/O errors
Status: BLOCKED 🚧
Seems to be close to impossible:
Source: https://medium.com/opsops/block-device-error-count-in-linux-f010ed4f7f76
Source: https://utcc.utoronto.ca/~cks/space/blog/linux/DiskErrorsSysfsCountWish
Other sources:
Filesystem driver error counter
(Source)
I encountered an error. Here's from
$ dmesg
:But the corresponding error counters in the FS driver are big fat nil:
Utterly useless.
The text was updated successfully, but these errors were encountered: