From owner-freebsd-fs@freebsd.org Sat Mar 3 12:28:59 2018 Return-Path: Delivered-To: freebsd-fs@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 CF4AFF37A88; Sat, 3 Mar 2018 12:28:59 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 6869E7F053; Sat, 3 Mar 2018 12:28:59 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id CF98920BE0; Sat, 3 Mar 2018 07:28:58 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Sat, 03 Mar 2018 07:28:58 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=DURPaCa293hbkyyfUw2BjXEpOCYmE HQAwRvUbi5wRsU=; b=hugGkg1rPH6yfz18+SgDjuO1fiH+n6NUoZtzqvO0oEq95 gRvFicMCpU73mKaf1byOX1ZfxwSwn/f28LFl7iIeg6jj1u/W+IHVDGfOY65cEvYp mnISI9HzfhCGxU6eecrvieuJernf0gpvmNpIt3fKZO91s6Px1pZu4ke3ZavsllPa y6+wl5pu4CgqPyIlOyVEhM0oA2zqtIPrs/QAl4KNCTNUSamxcb0n6jxwapuTPwWi Re6c98QkyWa0fRDp+dhvilRH+gssOUmsIHFrnIe/7iTIP00AcAwvONMEGmiuDUGx P2qSe6MFN7WrqhU6eQOBWZk/zRen9t3ZEJKt5LrZw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=DURPaC a293hbkyyfUw2BjXEpOCYmEHQAwRvUbi5wRsU=; b=QpiEE6jxNydaHcMPo71MID rJUC6u4pJaoA234dapewBoKNqqLU7YP76cUwVswsXaSk+GiJsCyUOILa7grvhf4j A37j0Ob8sS4zI+0XEJCgBsTCcdDQusG3xJ+l6jqvyeEk/S/KR/cQ/sDvV4yx+4U+ R3AaQ9I3iQoxwashYeeKIULd6ptyxZKr/a5Y3ySt/YmUxK2jQ4tRMFaHF7V3VGIV hXUwmuhdjHZRtpT5VDHogtlLZ5t+qyGO5L26UiU/iKQ/QHAg7C9ur4vKH/Hwr/h0 VI7HBlTkeUYRin3IoVJMB5utifDjXPz2Vzise/lI/ZfYKSXEqrYGOnaLC5xl4gMA == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 428BA243C4; Sat, 3 Mar 2018 07:28:58 -0500 (EST) Subject: Re: zfs problems after rebuilding system [SOLVED] To: Dimitry Andric Cc: FreeBSD Filesystems , FreeBSD Stable 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> From: tech-lists Message-ID: Date: Sat, 3 Mar 2018 12:28:57 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <5CFC89E9-57BE-4CB7-9C55-0D3CCF1E8D3D@FreeBSD.org> Content-Type: text/plain; charset=windows-1252 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2018 12:29:00 -0000 On 03/03/2018 00:23, Dimitry Andric wrote: > Indeed. I have had the following for a few years now, due to USB drives > with ZFS pools: > > --- /usr/src/etc/rc.d/zfs 2016-11-08 10:21:29.820131000 +0100 > +++ /etc/rc.d/zfs 2016-11-08 12:49:52.971161000 +0100 > @@ -25,6 +25,8 @@ > > zfs_start_main() > { > + echo "Sleeping for 10 seconds to let USB devices settle..." > + sleep 10 > zfs mount -va > zfs share -a > if [ ! -r /etc/zfs/exports ]; then > > For some reason, USB3 (xhci) controllers can take a very, very long time > to correctly attach mass storage devices: I usually see many timeouts > before they finally get detected. After that, the devices always work > just fine, though. > > Whether this is due to some sort of BIOS handover trouble, or due to > cheap and/or crappy USB-to-SATA bridges (even with brand WD and Seagate > disks!), I have no idea. I attempted to debug it at some point, but > a well-placed "sleep 10" was an acceptable workaround... :) That fixed it, thank you again :D -- J.