Hello, A design question for a user-space RAID monitoring tool. The tool is intended to export machine-readable md state so that the system owners can creating automated alert policies etc. Should it get its information on md device state from /proc/mdstat, or /sys/block/*/md/ as a data source, or should it use the ioctl interface that mdadm uses (on the basis that this is more complete / heavily tested). I assume the issues are: . usability (/proc/mdstat is intended to be human-readable so machine parsing it seems bleugh - it's also incomplete?) . stability (perhaps /sys/block/*/md/ is less stable than the ioctl or proc interface? Or perhaps it's just fine and won't break in backward-incompatible ways?). Any thoughts? Should I see which way the recent "add bad block flag to disk state" patch-set thread goes? Tim. -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
