From owner-freebsd-bugs@freebsd.org Fri Apr 29 23:24:18 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E0276B2164C for ; Fri, 29 Apr 2016 23:24:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B684B1DDF for ; Fri, 29 Apr 2016 23:24:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u3TNOIRS091755 for ; Fri, 29 Apr 2016 23:24:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 209112] /usr/sbin/jail jails fail to launch with possible race when jails mount common dir with nullfs Date: Fri, 29 Apr 2016 23:24:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jamie@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2016 23:24:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209112 Jamie Gritton changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jamie@FreeBSD.org --- Comment #1 from Jamie Gritton --- There are a couple problems with the jail startup script, neither of which = is exactly at the center of this complaint. The first is the lack of logging in case of failure. The $_tmp file is rem= oved (after printing only the last line), which it should be preserved somehow. = I don't know if printing the whole thing out is the right answer, or appendin= g it to some long file, but removing it is problematic. The second is the parallel start. There is a jail_parallel_start flag, but it's only checked when starting a subset of jails (i.e. "service jail start= foo bar") and not when starting all jails. Both of these should be fixed, but they're not the source of your problem, = only something that makes it harder to solve. Unfortunately, I wasn't able to recreate your issue, and was in fact able to create 100 jails each with a nullfs-mount directory, in a setup based on your noted jail.conf file. Still, I have a guess: the nullfs module. The error you're getting is ENOD= EV, is given when mounting a filesystem type that depends on a kernel module and loading that module fails. Now there's some kernel locking around the modu= le load that should make it so different mounts tying to load the same module = at the same time don't run into each other, and like I mentioned it worked out= for me. But of the places where ENODEV was mentioned, that seemed the most lik= ely. I'll leave this bug open, but I'll only be looking at the jail part of it, = not at the central issue. That's out of my area and what I failed to duplicate. --=20 You are receiving this mail because: You are the assignee for the bug.=