From owner-freebsd-fs@FreeBSD.ORG Tue Nov 4 14:42:10 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 58F8B480 for ; Tue, 4 Nov 2014 14:42:10 +0000 (UTC) Received: from mail-yh0-x22e.google.com (mail-yh0-x22e.google.com [IPv6:2607:f8b0:4002:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1194FCC8 for ; Tue, 4 Nov 2014 14:42:10 +0000 (UTC) Received: by mail-yh0-f46.google.com with SMTP id c41so2530916yho.5 for ; Tue, 04 Nov 2014 06:42:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8ikZRST7nuPm4rJvo5qglgMHXqxfpk6Mk3ANyQ9ujrU=; b=tokidzvOSMpoUZdTMNFc/r1vd4ZXH8lx19PWkVc4OmnUfIxsi+FJrwq8Gq/UDFkgIW XfcQUiANXY6B6hA1u1C/QLJB59Fr83f5HwqmqLKzg/QqnlxaYzRz2trWGOtB5EJxhNUZ XGekNNoAZFLAmNzROvhfrGl+raxCkIrfJfdsXPGvvJL9z6kbZkKZfSJ0jz/sFlwtl4Hp 1Oikqvvwwx4GXIrbpVEMFAB6XNiyT7sVhJd1kRVi8Ebog0V9UefuOILF/kmbSWu1yBFO zOaqVQFoKIm6qSkc5sFoVyIIrg9O3z0IgudPxLqQg7pwQXL8W6t9rTLjqtyS306KVDCG heGg== MIME-Version: 1.0 X-Received: by 10.236.230.40 with SMTP id i38mr34954294yhq.34.1415112129281; Tue, 04 Nov 2014 06:42:09 -0800 (PST) Received: by 10.170.156.139 with HTTP; Tue, 4 Nov 2014 06:42:09 -0800 (PST) In-Reply-To: <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> <5449152a2e174a81ae59cb36e7a9de7c@SERVER.ad.usd-group.com> Date: Tue, 4 Nov 2014 14:42:09 +0000 Message-ID: Subject: Re: why no automount for one zfs? From: krad To: Matt Churchyard Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-fs@freebsd.org" 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 14:42:10 -0000 i 2nd that, a zfs list output wouldnt go amiss either On 4 November 2014 10:26, Matt Churchyard wrote: > >Steven Hartland wrote: > > >> On 04/11/2014 09:17, Zeus Panchenko wrote: > >> > Steven Hartland wrote: > >> >> Missing zfs_enable="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 > root-on-zfs > > Just to be clear, the root filesystem is mounted slightly earlier in the > boot 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.conf) > > However, if you don't have zfs_enable="YES" in /etc/rc.conf, no *other* > ZFS 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="YES" > >... > >---[ quotation end ]------------------------------------------- > > > >> it will fix you mounting issue. > > >the problem exists only for this single fs, all other fs are automounted > correctly > > At the moment I'd look at the possibility of another ZFS dataset getting > mounted over the top. > > Regards, > Matt > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >