On Wed, Feb 22, 2017 at 8:12 AM, Przemek Klosowski <przemek.klosowski@xxxxxxxx> wrote: > On 02/22/2017 09:37 AM, Vratislav Podzimek wrote: > > On Tue, 2017-02-21 at 14:29 -0700, Chris Murphy wrote: > > Tested Fedora 24 and Fedora 23, there's no notification with either > one of those. I have no idea if this is a VM thing. Or if it's a > regression. > > Maybe the notification was depending on smartd rather than mdadm. > Kinda need someone who knows more about how GNOME Shell handles faulty > devices - how it's intended to work at least. > > SMART-signaled failures are propagated/signaled by udisksd. > > SMART is very good but not conclusive: we've seen RAID failures where disks > just die or become unresponsive, without anything wrong indicated in SMART. > Backblaze did a series of hard drive reliability reports that document that > as well; they are a great read if you haven't seen them: > https://www.backblaze.com/blog/?s=reliability I'm pretty certain the notification I got from GNOME Shell was related to the array itself. That suggests it's not a smartd initiated notification. But at the moment I can't reproduce this by deleting an array member device using sysfs. The array does go degraded, there are numerous kernel messages as such, but no GNOME notification. -- Chris Murphy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
