It's not just mdadm. It likewise affects Btrfs, ZFS, and LVM. Also, there's a lack of granularity with linux command timer and SCT ERC applying only to the entire block device, not partitions. So there's a problem for mixed use cases. For example, two drives, each with two partitions. sda1 and sdb1 are raid0, and sda2 and sdb2 are raid1. What's the proper configuration for SCT ERC and the SCSI command timer? *shrug* I don't think the automatic udev configuration idea is fail safe. It sounds too easy for it to automatically cause a misconfiguration. And it also doesn't at all solve the problem that there's next to no error reporting to user space. smartd does, but it's narrow in scope and entirely defers to the hard drive's self-assessment. There's all sorts of problems that aren't in the domain of SMART that get reported in dmesg, but there's no method for gnome-shell or KDE or any DE or even send an email to a sysadmin, as an early warning. Instead, all too often it's "WTF XFS just corrupted itself!" meanwhile the real problem has been happening for a week, dmesg/journal is full of errors indicating the nature of those problems, but nothing bothered to inform a human being until the file system face planted. Chris Murphy -- 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
