From owner-freebsd-fs@freebsd.org Fri Mar 2 21:38:43 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 1EC07F47CF1; Fri, 2 Mar 2018 21:38:43 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 92E997A170; Fri, 2 Mar 2018 21:38:42 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x235.google.com with SMTP id 70so15294660lfw.2; Fri, 02 Mar 2018 13:38:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=LM+ScmQrm9TjddlNzwQuussyt7YnNQZ7ayRh7ieiNAo=; b=Lq4fLwpzSoUe3GxH4s17Ny6f2GgEat92dOuZdJz4NkcNF3/uI+GbL7TnuOGgj+ba16 lIqnjJ7Md4VcqgSYXQRBDjylzogHHL7n1rP+JnvF2Th/En5TDkdsFQUTYGdOH6BbfEa3 jqVgU8D+ESEowyvPTUpyyfMb993NiDDF7HZgDPnmcl3WfCbPBS1JkDk5pfQytP1AJ6Qx ZRouwsH7Mx4N4ASWPzl2+TfAYND+G/Osy7AcUA30H3AZXRtiqiONKrNpwUNb3VaAIvRT BlaISg7UsvktdunMQIXx358jt6KzPJWT4GkRnneMN8SGdkZ8aBxgom1xY1SCg3MD8+hj /8Lw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=LM+ScmQrm9TjddlNzwQuussyt7YnNQZ7ayRh7ieiNAo=; b=WSw7lE5XEv+OX+XS2epFXDUCdhKv5WB2agBVIW3dGzymDA8euLWB6E1n1GTF3FeIuK E3ZlR5+pEKdJiDng069RuAGaG9664mplEQ85rlMdmAUN9gafqBRhqZMMMdDiTJUnwwmw 5ezNuX6pysOfVaybdswa9qbPXq96NAit53u34kM60qtIXYACsGJ00krm3WSazvjYM9Qj v9Wgf+rxzbNEFRY8JWYTD6RcR8XxIv62gLXv3z88Glml9hB3N4Vmpr1Gdf1A6NEvJ9Kc AZHGu8Hg9y6NvZkFx/fzUAWgRqGbZkNEI0RDVYP8kIH5cHFWasxGIXAfnSG0I49TjCJ2 VKKw== X-Gm-Message-State: AElRT7GGbLaWuVyUtTFV9rB3hBJDRbWhjACiFcOSAjEuGxNDxlaFQPsg 7LIe68khc0FfWao/+RGrs930lnJJGT8Gs5gyhME= X-Google-Smtp-Source: AG47ELsLEVGJJePQN4loGs+2biVjsFUniKcZQ5IrBDybjdZxfotItgPAXsCEG6OZwviYGoBdKA02hBu6SlTTJVzkRuA= X-Received: by 10.25.157.80 with SMTP id g77mr4712467lfe.142.1520026720710; Fri, 02 Mar 2018 13:38:40 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.2.195 with HTTP; Fri, 2 Mar 2018 13:38:40 -0800 (PST) In-Reply-To: <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> From: Alan Somers Date: Fri, 2 Mar 2018 14:38:40 -0700 X-Google-Sender-Auth: bwbAbXGWsbOn5iwXj5HwjfWRpTw Message-ID: Subject: Re: zfs problems after rebuilding system To: tech-lists Cc: freebsd-fs , FreeBSD Stable Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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:38:43 -0000 On Fri, Mar 2, 2018 at 2:26 PM, tech-lists wrote: > 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. > The relevant code is in /etc/rc.d/zfs, and it already uses "-a". Have you checked if /etc/rc.d/zfs is printing any errors to the console during boot? -Alan