From owner-freebsd-fs@FreeBSD.ORG Mon Sep 19 20:43:57 2011 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DC51106566B for ; Mon, 19 Sep 2011 20:43:57 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 99C158FC17 for ; Mon, 19 Sep 2011 20:43:56 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id XAA17466; Mon, 19 Sep 2011 23:43:53 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1R5kgz-000I2S-Gn; Mon, 19 Sep 2011 23:43:53 +0300 Message-ID: <4E77A988.30905@FreeBSD.org> Date: Mon, 19 Sep 2011 23:43:52 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.2) Gecko/20110907 Thunderbird/6.0.2 MIME-Version: 1.0 To: Rotate 13 References: <4E776352.30702@FreeBSD.org> In-Reply-To: X-Enigmail-Version: undefined Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org Subject: Re: ZFS: deferring automounts/mounting root without bootfs [9.0-BETA2] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2011 20:43:57 -0000 on 19/09/2011 19:15 Rotate 13 said the following: > On Mon, 19 Sep 2011 11:44:18 -0400, Andriy Gapon wrote: > >> on 19/09/2011 18:29 Rotate 13 said the following: >>> 9.0-BETA2 system is booted off removable UFS volume, but root is >>> mounted from ZFS. I try to meet the following two goals: >>> >>> 1. Not use bootfs property (too many limitations mentioned in docs) >> >>> 2. Use ZFS inheritable mountpoints and management (not clutter up >>> /etc/fstab... and not set mountpoint= on each child dataset!) >>> >>> Config info is below. Result: System boots, but hangs with >>> >>> init: can't exec getty '/usr/libexec/getty' for port /dev/ttyv0: No >>> such file or directory >> >> This looks like devfs (/dev) is either not mounted or something is >> mounted over >> it. I think that you should check if any other auto-mountable dataset >> in your >> pool has a mountpoint of '/'. Or the root dataset of tank is till >> mounted for >> some reason or something like that. > > Thanks for quick reply. No /dev was my first thought too. But I also > saw other messages scroll by of unable to write in /var, which is on > ZFS itself. So I think the "No such file or directory" probably for > /usr/libexec/getty (cannot read /usr). Note also, root dataset is > canmount=off - should not be ever mounted to begin with - and nothing > except root dataset and tank/root have / mountpoint. > > I will see what I can do to verify devfs is being mounted, but > definitely at least some ZFS dataset(s) are problem. Which brings me > back my original question. Difficult to diagnose when system won't > write logs to /var - could be very simple misconfiguration, could be > bug. Manuals don't say a lot about mount order on boot, and that > remains my suspicion due to behavior when zpool import -f from rescue > shell: Can't mount /usr, /var, etc. until after tank/root is manually > mounted, but after, zfs mount -a is magic. You can try to enter ddb (if you have that in your kernel and also have the magic ddb key enabled) and issue 'show mount' command to see some details. -- Andriy Gapon