From owner-freebsd-stable@freebsd.org Sat Mar 3 16:19:12 2018 Return-Path: Delivered-To: freebsd-stable@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 3B37CF249B6 for ; Sat, 3 Mar 2018 16:19:12 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C9B53683BD for ; Sat, 3 Mar 2018 16:19:11 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from cpc73666-dals20-2-0-cust303.20-2.cable.virginm.net ([82.47.237.48] helo=foula.drayhouse.twisted.org.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1es9sM-0008gR-1v for freebsd-stable@freebsd.org; Sat, 03 Mar 2018 16:19:10 +0000 Subject: Re: zfs problems after rebuilding system [SOLVED] To: freebsd-stable@freebsd.org References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> <65372449-53f1-8002-981a-e20f4a592e26@zyxst.net> <5CFC89E9-57BE-4CB7-9C55-0D3CCF1E8D3D@FreeBSD.org> <20180303234236.M3811@besplex.bde.org> From: Pete French Message-ID: <9b3cd942-347c-44a2-60d6-0b3c4a45552f@ingresso.co.uk> Date: Sat, 3 Mar 2018 16:19:09 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180303234236.M3811@besplex.bde.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2018 16:19:12 -0000 > That won't work for the boot drive. > > When no boot drive is detected early enough, the kernel goes to the > mountroot prompt.  That seems to hold a Giant lock which inhibits > further progress being made.  Sometimes progress can be made by trying > to mount unmountable partitions on other drives, but this usually goes > too fast, especially if the USB drive often times out. We have this problem in Azure with a ZFS root, was fixed by the pacth in this bug report, which actually starts off being about USB. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208882 You can then set the mountroot timeout as normal and it works. I wold really like this patch to be applied, but it seems to have languished since last summer. We use this as standard on all our cloud machines now, and it works very nicely. -pete.