From owner-freebsd-geom@freebsd.org Thu Oct 25 16:27:42 2018 Return-Path: Delivered-To: freebsd-geom@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B7C6107E924 for ; Thu, 25 Oct 2018 16:27:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4A2A58D32D for ; Thu, 25 Oct 2018 16:27:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0F81B107E920; Thu, 25 Oct 2018 16:27:42 +0000 (UTC) Delivered-To: geom@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E1C50107E91E for ; Thu, 25 Oct 2018 16:27:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 838A88D326 for ; Thu, 25 Oct 2018 16:27:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id A20B517996 for ; Thu, 25 Oct 2018 16:27:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w9PGReMS086086 for ; Thu, 25 Oct 2018 16:27:40 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w9PGRevB086083 for geom@FreeBSD.org; Thu, 25 Oct 2018 16:27:40 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: geom@FreeBSD.org Subject: [Bug 232684] [gmirror] gmirror overly aggressive provider destruction Date: Thu, 25 Oct 2018 16:27:40 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: cem@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc dependson blocked Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Oct 2018 16:27:42 -0000 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 on the CC list for the bug.=