Date: Thu, 25 Oct 2018 16:27:40 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 232684] [gmirror] gmirror overly aggressive provider destruction Message-ID: <bug-232684-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232684 Bug ID: 232684 Summary: [gmirror] gmirror overly aggressive provider destruction Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: cem@freebsd.org CC: geom@FreeBSD.org, markj@FreeBSD.org Depends on: 232671 Blocks: 232683 +++ This bug was initially created as a clone of Bug #232671 +++ In the bug we cloned from, gmirror destroyed the root0 provider because the= two disks it currently knew about were both invalid (one stale, one partially sychronized). Transitioning to RUNNING with no ACTIVE disks is its own bug (the original we cloned) but in general gmirror is quick to kill itself whe= n it enters a bad state. I don't think this is necessarily a good idea. It might be best to limp al= ong in a degraded mode that ENXIO's all operations but allows (1) an administra= tor to re-plug devices to the system in case they had an ACTIVE mirror disk lyi= ng around disconnected or (2) maybe hardware was just slow to settle. I haven't thought through the ramifications of this proposal thoroughly and it's possible this is nonsensical. It's certainly a lower priority than the other two recent GEOM PRs I've filed. Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232671 [Bug 232671] [gmirror] gmirror fails to recover from degraded mirror sets in some circumstances https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232683 [Bug 232683] [gmirror] gmirror could provide much better administrative introspection into decision-making processes --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-232684-227>