The right thing to do here is to stop using read_threshold and find a suitable replacement. Blacklisting a command to a drive because it does the right thing when faced with an illegal command is ridiculous.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092622 Title: disks hang as atasmart is sending illegal smart command to "green" disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/1092622/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
