From owner-freebsd-questions@FreeBSD.ORG Mon Nov 7 20:08:44 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0610F106566C for ; Mon, 7 Nov 2011 20:08:44 +0000 (UTC) (envelope-from moritz@wzff.de) Received: from barfooze.de (barfooze.de [78.46.117.212]) by mx1.freebsd.org (Postfix) with ESMTP id C3C8B8FC15 for ; Mon, 7 Nov 2011 20:08:43 +0000 (UTC) Received: from localhost.localdomain ([127.0.0.1] helo=barfooze.de) by barfooze.de with smtp (Exim 4.76) (envelope-from ) id 1RNVRc-00065z-1o for freebsd-questions@freebsd.org; Mon, 07 Nov 2011 21:05:33 +0100 Date: Mon, 7 Nov 2011 21:05:24 +0100 From: Moritz Wilhelmy To: freebsd-questions@freebsd.org Message-ID: <20111107200523.GY16096@barfooze.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Problems with nullfs on 9.0-RC1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Nov 2011 20:08:44 -0000 Good evening, I have been experiencing problems with accessing a nullfs which has been mounted inside a nullfs. This is meant to be a very elaborate way to exchange files between my jails :-) I have following entries in /etc/fstab on the host system, which runs FreeBSD 9.0-RC1 from a few days ago: /usr/jails/foo/share /shares/foo nullfs ro 0 0 /shares /usr/jails/foo/shares nullfs ro 0 0 /usr/jails/bar/share /shares/bar nullfs ro 0 0 /shares /usr/jails/bar/shares nullfs ro 0 0 etc. If I create a file in the bar jail in /share, let's call it zot, it is available on the host system in /shares/bar, but not inside /usr/jails/foo/shares/bar or /usr/jails/bar/shares/bar. My syslog is full of messages like these: Nov 7 16:44:15 machine kernel: null_bypass: vop_getattr Nov 7 16:44:15 machine kernel: null_bypass: vop_readdir Nov 7 16:44:15 machine kernel: null_bypass: vop_readdir Nov 7 16:44:15 machine kernel: null_bypass: vop_close Nov 7 16:44:15 machine kernel: null_bypass: vop_access Nov 7 16:44:15 machine kernel: null_bypass: vop_open Nov 7 16:44:15 machine kernel: null_bypass: vop_getattr Nov 7 16:44:15 machine kernel: null_bypass: vop_read Nov 7 16:44:15 machine kernel: null_bypass: vop_close Nov 7 16:44:15 machine kernel: null_bypass: vop_access Nov 7 16:44:15 machine kernel: null_bypass: vop_open Nov 7 16:44:15 machine kernel: null_bypass: vop_getattr Nov 7 16:44:15 machine kernel: null_bypass: vop_read Nov 7 16:44:15 machine kernel: null_bypass: vop_close Nov 7 16:44:15 machine kernel: null_bypass: vop_getattr Nov 7 16:44:15 machine kernel: null_bypass: vop_access Nov 7 16:44:15 machine kernel: null_bypass: vop_open Nov 7 16:44:15 machine kernel: null_bypass: vop_getattr Nov 7 16:44:15 machine kernel: null_bypass: vop_readdir Nov 7 16:44:15 machine kernel: null_bypass: vop_readdir Nov 7 16:44:15 machine kernel: null_bypass: vop_close Nov 7 16:44:15 machine kernel: null_bypass: vop_getattr Nov 7 16:44:15 machine last message repeated 2 times Nov 7 16:44:15 machine kernel: null_bypass: vop_access I guess I'm either doing something very stupid here, or this is a bug? The manpage doesn't mention anything about nullfs still being unstable (I read it used to be, with a huge bugs section in the manpage, which read like this: "SLIPPERY WHEN WET, BEWARE OF DOG"). Has anyone run into similar problems? Best regards, Moritz