| |||||||||||||
Ext3 and RAID: silent data killers?Ext3 and RAID: silent data killers?Posted Sep 3, 2009 15:37 UTC (Thu) by yohahn (subscriber, #4107)In reply to: Ext3 and RAID: silent data killers? by Klavs Parent article: Ext3 and RAID: silent data killers?
Right, but what standard method to trigger this when a raid goes degraded. (and how will applications respond to their disks becoming read-only suddenly)
(Log in to post comments)
Ext3 and RAID: silent data killers? Posted Sep 3, 2009 21:42 UTC (Thu) by Cato (subscriber, #7643) [Link]
When disks are remounted read-only, there is no message to the end user (at least on Ubuntu) - as a result, one PC where this happened had a read-only root filesystem for weeks until I noticed this from the logs.
Sending notifications of serious system events like this would be very helpful, with a bundle of standard event filters that can easily generate an email or other alert.
Ext3 and RAID: silent data killers? Posted Sep 11, 2009 17:59 UTC (Fri) by jengelh (subscriber, #33263) [Link]
You can only remount ro when there are no files open in write mode. And there usually are on /.
Ext3 and RAID: silent data killers? Posted Sep 4, 2009 8:22 UTC (Fri) by njs (guest, #40338) [Link]
mdadm has a hook to let you run an arbitrary script when a RAID device changes state (degrades, etc.); I don't have a remount -o ro script handy myself, though.
Ext3 and RAID: silent data killers? Posted Sep 4, 2009 23:39 UTC (Fri) by giraffedata (subscriber, #1954) [Link] (and how will applications respond to their disks becoming read-only suddenly) I think this would be only marginally better than shutting the whole system down. In many ways it would be worse, since users have ways to deal with a missing system but not a system acting strangely.
|
|||||||||||||