From owner-freebsd-fs@freebsd.org Fri Mar 2 20:39:06 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 6CC13F44228; Fri, 2 Mar 2018 20:39:06 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (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 B7598773AA; Fri, 2 Mar 2018 20:39:05 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22a.google.com with SMTP id y19so15112444lfd.4; Fri, 02 Mar 2018 12:39:05 -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=VXraBL3RG+g5rY5mKLCpY6LxeNtQhcLfUXjwzoQHd/I=; b=Imr2uKR9J7GxVLolt0jE0Ce5igkO96ejDzaEBsabkwR+a2SVWn4c8mM0Ub+sqKa++C Sl+R/rhocYIzGvtbTkLodcuKpT7PvhK2priRuBv4U5aPK4QGDPWIpu3Cali5P+nRolu6 S4yfEt+d9H3l2XshqeVV01Jh7+H6eDJ5OnS30NAhcy3o0wGgjZ4nm7hNW82SOdkToWWO BrU7+NtxzU6DPTlFwzI6RLsEiZTnFrsD5C5qp1JCocRxAKU2j2NJSnCdgoGx0MtVzY55 N6xJYt7fKdepCKcjrzdLkwRyBIOlOjcZydMDciRfO8Q3ppW8a4DxhZTlEDsKhxxiQ1Qa wzCQ== 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=VXraBL3RG+g5rY5mKLCpY6LxeNtQhcLfUXjwzoQHd/I=; b=fm4U75sdWKQNZGi49O+yMwiMe5jkKv77euoNgnwLiGPik+ATBxu16StLibFKmj0p55 ive4RUChRoVZrZlmTw64XJcpdMkSzefGRr3NgG6YyBUZPhhT/Disz+plvvGcjKn0oKGu u3r3xi2egsdtHx3h4JhvR5eowGJQigjkOm7RtuDB0xz/KoK7IYzFNCWleQIh5akxbZDH l2Il9NtTfMBbj2/9IiOJsE/JZ9yi18LuHyrMasR3SMutcIA770F+iL4HQDXppN1cwSJK JORzF+MHTrQI/ly/ZRPZTzcacwJjxf5U8dRQCfE3ibglZ76ae5g5pL0D8lHT4H5TsI53 X2uA== X-Gm-Message-State: APf1xPBBsSCkQOxFdiQ3x6b8TIPnvQBtmSWpwFOwt974bqFJmcE/5kRy rNHSkhAvt+VFlIMZSsvQGXA7uflrqpsJ8RhzL/GP0w== X-Google-Smtp-Source: AG47ELtw9QOPvwd8kV8g10a485EVZ6TYKjkh4h3QwqhA6K+xaUhoy5uoCVoYUyO2fLXiVHparhtVbN/Vfm2CnVpdmvg= X-Received: by 10.46.9.150 with SMTP id 144mr4892119ljj.117.1520023144139; Fri, 02 Mar 2018 12:39:04 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.2.195 with HTTP; Fri, 2 Mar 2018 12:39:03 -0800 (PST) In-Reply-To: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> From: Alan Somers Date: Fri, 2 Mar 2018 13:39:03 -0700 X-Google-Sender-Auth: kmiTTnzIJQu-r9rK3S9IXOPoM5o 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 20:39:06 -0000 On Fri, Mar 2, 2018 at 1:25 PM, tech-lists wrote: > 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. > 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? > > 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. Also, have you set "zfs_enable=YES" in /etc/rc.conf? -Alan