From owner-freebsd-stable@freebsd.org Fri Mar 2 20:25:28 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 5C88AF431EC; Fri, 2 Mar 2018 20:25:28 +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 ED76D76AEF; Fri, 2 Mar 2018 20:25:27 +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 6824520E0E; Fri, 2 Mar 2018 15:25:27 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 02 Mar 2018 15:25:27 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=1jB6Lkrayd+wLt+f2qTnvlmStt7Ra9SwdlQKMp2/sS8=; b=qWizx1+B T3E0YrYaBoHrCTHdgIdDotRHDsSCd5cyaYqTAjJHPTw59zW3yRfs9gfoRpNYhG8q hkJJd4DMxpU8SI5iJvRWNLXQJjNXmr7n3uGUbGabcyT2s5N5ecZp3P1rVX1MwrUw o4pH+PLIfKE2sjL4ND3CB5feI5EKIwm0WgzPr1SAm1HCb4Qw/5JIe46jj122eFoW Y/jCoI8VqyfjMNQ/NYber8qe7DtInFLVFJe9RNGCNR0CL96dlPxFUF/jBUJYkeMi ZzLlA8vSaR5DK2bq14C6NRJyhkaJIxKEVGAU8WP4pWS3R/iMSdQesrEjpLBIMjYK pkbaTNa30Yel4Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=1jB6Lkrayd+wLt+f2qTnvlmStt7Ra 9SwdlQKMp2/sS8=; b=UHOeCEfAy60fsw5eB38co+DdBl8dj/3CKtmbWfpJcMI+J 1xKS7HBa3snt/HG6b2yU5qzAeSkVoRjOscEpyh1UDAnI6MyJZ7LEefTBT0tA1rxR trD+vJ/WHIIvZUp4lJCyIyGxbII+nSBzmZ+Xhq6wf3Jy7XgYNtLoGej1b6CdjL3f YxzKFTBt/qxXXnVVgHi5C3mnZMupjvszn9n96EVtSpNzor/yfXVnim/lXkRltr38 0HzpzUG5aFM2sp8GzlvafCTpnU7jCcKCfLVKzuPEMgJ8r/ZGIkHt8rjBNGiKq00n kvzV9LUXPL4ZWPqWDnvpT6M5eY76a7XP3uy+2ZLZA== X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id D01B27E570; Fri, 2 Mar 2018 15:25:26 -0500 (EST) To: freebsd-fs@freebsd.org Cc: FreeBSD Stable From: tech-lists Subject: zfs problems after rebuilding system Message-ID: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> Date: Fri, 2 Mar 2018 20:25:25 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit 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: Fri, 02 Mar 2018 20:25:28 -0000 Hi, Importing two zpools after a hd crash, the first pool I imported auto-loads at boot. But the second one I'm always having to zfs mount (zpool name) then mount the zfs subdirs. The system was like this: ada0 (this had the OS on. It was replaced after it crashed. Not a member of any zpool, not zfs at all, no root-on-zfs). New freebsd-11-stable-snapshot was installed to this disk. ada1 \ ada2 -- these made up zpool0, a raidz pool. Each device is a 1TB disk. ada3 / zpool1 - this is striped, one 4TB disk, attached via usb3 zpool1/c - this is compressed with lz4 zpool1/important - this has copies=2 enabled I ran zpool import zpool0 and then zpool import zpool1 and both imported without error. However despite setting the mountpoint for zpool1 as /zpool1, on reboot I always have to: # zfs mount zpool1 or I won't see the drive in df -h or mount or zfs mount. But I *will* find it at its mountpoint /zpool1. If I do a ls -lah on that, I can see zpool1/c and zpool1/important as dirs but not in zfs mount or (normal) mount, nor can I see the other dirs that are not vdevs. If I then zfs mount zpool1 I can see all the dirs and vdevs on that disk off its root, in ls -lah. But I dont see the vdevs in zfs mount. I have to zfs mount zpool1/c and zfs mount zpool1/important to see the vdevs in zfs mount. Confusingly, I didn't need to and don't have to do any of that for zpool0. What am I doing wrong/what am I missing? Why is zpool0 automatically loading but zpool1 is not? Before ada0 (the failed disk) was replaced, both loaded on boot. thanks, -- J.