From owner-freebsd-fs@freebsd.org Fri Mar 2 21:26:17 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 9A535F47049; Fri, 2 Mar 2018 21:26:17 +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 40AF779517; Fri, 2 Mar 2018 21:26:17 +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 5719020DDF; Fri, 2 Mar 2018 16:26:16 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 02 Mar 2018 16:26:16 -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=AhbiV2Qf0gbf9C89mMs2jl2jdaNOp q757cPUpjywZLY=; b=P4Qi82ggQOCmnuEcEi5CJaCYa+s4IwWeJNFOKzhNyGMzi OiWJ80WxLvG8/FmgdncbU/Dy6XEXNDBAUAH6oO8TpcjxPCYDiqUPfQq7FxSzFPe1 lYvr+HfIp3iVKKLEa/mn5VSXnOo8HVZ4mWgs5SeGV/xYzUmorfSslDTVa/8FQCz7 Yy+7yOXMVZpJWd+o19D+VUpTXgtJ+A39G5ud1uzboVlnQjSDpJ/8/7IbARm2PgTG u3Dl74V6AGWIcX9fEspOfdDQfPMVIWpRx2U6HY5SdhyiUWQjxWNZhHyxLai4EkFH /UGEAOpeWCgqyvv7tz08tG2pKjF3EkhItzoC6CXHA== 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=AhbiV2 Qf0gbf9C89mMs2jl2jdaNOpq757cPUpjywZLY=; b=lANL1kHtFteeg3A7qfUVEx mlds0JnuB3g0jgaCQciiSLMX+pjYA1en1v/GLLjPWLUVkMp0GNcio2BXmxj2mbpl skmVCe01wb75MzUuff6SMcFY8uh/vxue4/CmOWmEXLnl1Bto4R5LSR9nBLEOnvbn Ui6Qf3w2yLsWosS1ARkIpbfghWRC468KMfwVhAxFRUP1Ms2hxJPYKs797PXGw758 NsEq2mB6+X6T/CKnUyqDI57zY4uS62X/oHFxr6tdX3XL+v/QgOMW0TrTwmMakv29 tstUAFb7JQJtD4FiatNXzlnTMEkHo7aEoI8cMTPq8vVqA4zuEKFsHVHBKuCeZdtw == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id A76BA7E6BC; Fri, 2 Mar 2018 16:26:15 -0500 (EST) Subject: Re: zfs problems after rebuilding system To: Alan Somers Cc: freebsd-fs , FreeBSD Stable References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> From: tech-lists Message-ID: <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> Date: Fri, 2 Mar 2018 21:26:14 +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: Content-Type: text/plain; charset=utf-8 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: Fri, 02 Mar 2018 21:26:17 -0000 Hi, thanks for looking at this, On 02/03/2018 20:39, Alan Somers wrote: > This doesn't make sense. vdevs have nothing to do with mounting. You see > your vdevs by doing "zpool status". What are you expecting to see that you > don't? sorry, I was confusing terms. I was expecting to see similar to output of zfs list from both zpools instead of just zpool0. (just rebooted the system.) OK here's zpool status: # zpool status pool: zpool1 state: ONLINE scan: scrub repaired 0 in 0h39m with 0 errors on Mon Feb 5 22:55:31 2018 config: NAME STATE READ WRITE CKSUM zpool1 ONLINE 0 0 0 diskid/DISK-NA7DKXXF ONLINE 0 0 0 errors: No known data errors pool: zpool0 state: ONLINE scan: scrub repaired 0 in 3h46m with 0 errors on Thu Mar 1 23:01:29 2018 config: NAME STATE READ WRITE CKSUM zpool0 ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada1 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 > >> 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. >> > Please post the output of "zfs list -r -o name,mountpoint,canmount,mounted" > and also the contents of /etc/fstab. # zfs list -r -o name,mountpoint,canmount,mounted NAME MOUNTPOINT CANMOUNT MOUNTED zpool1 /zpool1 on no zpool1/compressed /zpool1/compressed on no zpool1/important /zpool1/important on no zpool0 /zpool0 on yes zpool0/home /zpool0/home on yes zpool0/usr /zpool0/usr on yes zpool0/usr/local /zpool0/usr/local on yes zpool0/usr/oldsrc /usr/oldsrc on yes zpool0/usr/ports /usr/ports on yes zpool0/usr/src /usr/src on yes zpool0/vms /zpool0/vms on yes # cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/ada0s1a / ufs rw 1 1 /dev/ada0s1b none swap sw 0 0 linprocfs /compat/linux/proc linprocfs rw 0 0 tmpfs /compat/linux/dev/shm tmpfs rw,mode=1777 0 0 fdescfs /dev/fd fdescfs rw,late 0 0 > Also, have you set "zfs_enable=YES" in /etc/rc.conf? yes. If I run zfs mount -a, everything zfs is mounted as expected. I'm wondering if at bootup, when zfs mount is called (I suppose it must be called from somewhere), whether it needs to specify -a. I would not know the first place to look though. thanks, -- J.