From owner-freebsd-current@FreeBSD.ORG Sat Aug 6 09:11:30 2011 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80068106564A for ; Sat, 6 Aug 2011 09:11:30 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 45F488FC0A for ; Sat, 6 Aug 2011 09:11:29 +0000 (UTC) Received: by gwb15 with SMTP id 15so2297232gwb.13 for ; Sat, 06 Aug 2011 02:11:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=a9TGi4+NTj2crkOqlnTz9z4HRMK6OPAGqCG5fo4kVK4=; b=j17hfz+TRQuz/B34+ypz9ygFQmdsInCqb/W5ZaJyg2r2RDjTWa+zbaAl+KhTkuMqqT THzGXZMqmz0Z/XL+iqSK+x0rGtkX8P8q+5WreJGyJXNS92nuDpX5zDXOrNC30uFgkoTv JWbMc/9r9QqxE5XIPJmmsg+M7rlonyQnCsB7k= MIME-Version: 1.0 Received: by 10.142.117.13 with SMTP id p13mr3020154wfc.286.1312620265109; Sat, 06 Aug 2011 01:44:25 -0700 (PDT) Received: by 10.68.43.133 with HTTP; Sat, 6 Aug 2011 01:44:25 -0700 (PDT) Date: Sat, 6 Aug 2011 04:44:25 -0400 Message-ID: From: "b. f." To: freebsd-current@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Recursive nullfs mounts and r224655 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bf1783@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Aug 2011 09:11:30 -0000 Recent changes to the kernel (sys/kern/vfs_mount.c, in r224655?) between r224550 and r224655 have broken my tinderbox setup. It had a tmpfs filesystem mounted at /T and a UFS filesystem mounted at /U, and, when setting up the tinderbox, performed: mkdir /U/u1 mkdir /U/u2 mkdir /T/t1 mount -t nullfs /T/t1 /U/u1 mkdir-p /U/u1/u3/u4 mount -t nullfs /U/u2 /U/u1/u3/u4 ... This worked at r224550 and before. It now fails at the second nullfs mount, with ENOENT("mount_nullfs: No such file or directory"). b.