From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 10:36:03 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 72573471 for ; Tue, 4 Nov 2014 10:36:03 +0000 (UTC) Received: from smtp-outbound.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.userve.net", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F3CA5943 for ; Tue, 4 Nov 2014 10:36:02 +0000 (UTC) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) by smtp-outbound.userve.net (8.14.7/8.14.7) with ESMTP id sA4AQKYU011585 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 4 Nov 2014 10:26:20 GMT (envelope-from matt.churchyard@userve.net) Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.516.32; Tue, 4 Nov 2014 10:26:20 +0000 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0516.029; Tue, 4 Nov 2014 10:26:20 +0000 From: Matt Churchyard To: "freebsd-fs@freebsd.org" Subject: RE: why no automount for one zfs? Thread-Topic: why no automount for one zfs? Thread-Index: AQHP9/CkHtLge5shq0aIgpTMgNTLnpxQLdsAgAACtFSAAAN9AIAABHJsgAAJfSA= Date: Tue, 4 Nov 2014 10:26:19 +0000 Message-ID: <5449152a2e174a81ae59cb36e7a9de7c@SERVER.ad.usd-group.com> References: <20141104072923.79140@smtp.new-ukraine.org> <54589780.7020303@multiplay.co.uk> <20141104111704.91939@smtp.new-ukraine.org> <54589CB2.5090105@multiplay.co.uk> <20141104114540.94096@smtp.new-ukraine.org> In-Reply-To: <20141104114540.94096@smtp.new-ukraine.org> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Nov 2014 10:36:03 -0000 >Steven Hartland wrote: >> On 04/11/2014 09:17, Zeus Panchenko wrote: >> > Steven Hartland wrote: >> >> Missing zfs_enable=3D"YES" in /etc/rc.conf? >> > no, it is on it's place (I run root-on-zfs) >> > >> Add it, >the option *is* in /etc/rc.conf, otherwise I couldn't boot since I run roo= t-on-zfs Just to be clear, the root filesystem is mounted slightly earlier in the bo= ot process, regardless of rc.conf settings. (Obviously the root filesystem = has to be mounted before the system can read what you've got in /etc/rc.con= f) However, if you don't have zfs_enable=3D"YES" in /etc/rc.conf, no *other* Z= FS filesystems will be mounted. This is a very common problem that catches = quite a few people out, which is why you were asked to confirm. >> cat /etc/rc.conf >---[ quotation start ]------------------------------------------- >#-*- conf -*- ># >zfs_enable=3D"YES" >... >---[ quotation end ]------------------------------------------- >> it will fix you mounting issue. >the problem exists only for this single fs, all other fs are automounted c= orrectly At the moment I'd look at the possibility of another ZFS dataset getting mo= unted over the top. Regards, Matt