| From | Sent On | Attachments |
|---|---|---|
| Lev Serebryakov | Oct 4, 2011 11:04 am | |
| Lev Serebryakov | Oct 4, 2011 11:08 am | |
| Freddie Cash | Oct 4, 2011 11:12 am | |
| Alexander Motin | Oct 4, 2011 11:28 am | |
| Garrett Cooper | Oct 4, 2011 12:14 pm | |
| Lev Serebryakov | Oct 4, 2011 1:11 pm | |
| Freddie Cash | Oct 4, 2011 1:16 pm | |
| Miroslav Lachman | Oct 4, 2011 2:26 pm | |
| Alexander Motin | Oct 4, 2011 2:45 pm | |
| Andrey V. Elsukov | Oct 4, 2011 10:06 pm | |
| Lev Serebryakov | Oct 4, 2011 11:19 pm | |
| Lev Serebryakov | Oct 4, 2011 11:26 pm | |
| Lev Serebryakov | Oct 4, 2011 11:39 pm | |
| Lev Serebryakov | Oct 4, 2011 11:51 pm | |
| Andrey V. Elsukov | Oct 5, 2011 12:51 am | |
| Miroslav Lachman | Oct 5, 2011 1:23 am | |
| Lev Serebryakov | Oct 5, 2011 1:50 am | |
| Lev Serebryakov | Oct 5, 2011 1:58 am | |
| Alexander Motin | Oct 5, 2011 2:18 am | |
| Lev Serebryakov | Oct 5, 2011 2:29 am | |
| Miroslav Lachman | Oct 5, 2011 7:49 am | |
| Scot Hetzel | Oct 5, 2011 8:11 am | |
| Alexander Motin | Oct 5, 2011 2:34 pm | |
| Miroslav Lachman | Oct 5, 2011 3:12 pm | |
| John-Mark Gurney | Oct 5, 2011 3:53 pm | |
| Lev Serebryakov | Oct 5, 2011 11:39 pm | |
| Lev Serebryakov | Oct 5, 2011 11:46 pm | |
| Ivan Voras | Oct 6, 2011 4:06 am | |
| Daniel Kalchev | Oct 6, 2011 4:29 am | |
| Ivan Voras | Oct 6, 2011 5:36 am | |
| Daniel Kalchev | Oct 6, 2011 5:42 am | |
| Miroslav Lachman | Oct 6, 2011 5:58 am | |
| Ivan Voras | Oct 6, 2011 6:43 am | |
| Lev Serebryakov | Oct 6, 2011 6:53 am | |
| Lev Serebryakov | Oct 6, 2011 6:55 am | |
| Daniel Kalchev | Oct 6, 2011 6:58 am | |
| Pieter de Goeje | Oct 6, 2011 7:03 am | |
| Andrey V. Elsukov | Oct 6, 2011 7:40 am | |
| Lev Serebryakov | Oct 7, 2011 12:27 am | |
| per...@pluto.rain.com | Oct 7, 2011 7:06 am | |
| Lev Serebryakov | Oct 7, 2011 12:43 pm | |
| Daniel Kalchev | Oct 7, 2011 1:13 pm | |
| Ivan Voras | Oct 7, 2011 1:22 pm | |
| Lev Serebryakov | Oct 8, 2011 1:55 am | |
| Lev Serebryakov | Oct 8, 2011 1:56 am | |
| Lev Serebryakov | Oct 8, 2011 2:04 am | |
| per...@pluto.rain.com | Oct 8, 2011 2:51 am | |
| Daniel Kalchev | Oct 8, 2011 12:56 pm | |
| Lev Serebryakov | Oct 9, 2011 12:29 am | |
| Lev Serebryakov | Oct 9, 2011 12:31 am | |
| Miroslav Lachman | Oct 9, 2011 6:13 am | |
| per...@pluto.rain.com | Oct 9, 2011 6:59 am | |
| John | Oct 9, 2011 6:26 pm | |
| per...@pluto.rain.com | Oct 10, 2011 2:04 am |
| Subject: | Re: RFC: Project geom-events | |
|---|---|---|
| From: | Lev Serebryakov (le...@FreeBSD.org) | |
| Date: | Oct 4, 2011 11:19:34 pm | |
| List: | org.freebsd.freebsd-current | |
Hello, Miroslav. You wrote 5 октября 2011 г., 1:27:03:
I am still missing one thing - dropped provider is not marked as failed RAID provider and is accessible for anything like normal disk device. So in some edge cases, the system can boot from failed RAID component instead of degraded RAID. This can cause data loss or demage.
What RAID do you mean exactly? geom_stripe? geom_mirrot? geom_raid? Something else? If GEOM class drops underlying provider due to errors, it doesn't have chances to update metadata for it. But most of classes, if dropped provider attached again, will rebuild itself, as they track which components are actual and which ones are old. Do you want GEOM classes to track droppen components somewhere else and din't even try to attach them automaticaly when they re-appear?
Is it possible to fix it by something like your geom-events, or should it be done in each GEOM RAID class separately?
geom-events only process events from GEOM classes in userland. Each class should decide what happens to him by itself, as only class itself knows is this particular error fatal or not. geom-events could help, if it replaces dropped component fith spare drive, as in such case most classes prefer "latest" drive, not old one. Without spares, everything will be exactly as it is now, plus e-mails to administrator :)
-- // Black Lion AKA Lev Serebryakov <le...@FreeBSD.org>
_______________________________________________ free...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "free...@freebsd.org"





