From owner-freebsd-jail@FreeBSD.ORG Sun Oct 5 01:18:49 2014 Return-Path: Delivered-To: freebsd-jail@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 8D58956A for ; Sun, 5 Oct 2014 01:18:49 +0000 (UTC) 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 75B58BCC for ; Sun, 5 Oct 2014 01:18:49 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s951InLN044693 for ; Sun, 5 Oct 2014 01:18:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-jail@FreeBSD.org Subject: [Bug 186360] [jail] jail using nullfs and unionfs doesn't mount devfs Date: Sun, 05 Oct 2014 01:18:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: johannes@jo-t.de X-Bugzilla-Status: In Discussion X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-jail@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Oct 2014 01:18:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186360 johannes@jo-t.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |johannes@jo-t.de --- Comment #5 from johannes@jo-t.de --- I have the same problem on: FreeBSD fred 9.3-STABLE FreeBSD 9.3-STABLE #0 r272448: Fri Oct 3 19:02:13 BST 2014 root@fred:/usr/obj/usr/src/sys/FRED amd64 By the looks of it, something deletes the stuff in the to-be-jailed /dev after devfs is mounted there. Unmounting and remount it makes it work properly. Also, mounting devfs from a prestart script (and preventing jail start up by returning exit code 1), makes devfs behave well. So I'd suspect when jail(8) goes about starting up everything it messes up the device nodes. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-jail@FreeBSD.ORG Sun Oct 5 12:34:16 2014 Return-Path: Delivered-To: freebsd-jail@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 A4CF69FC; Sun, 5 Oct 2014 12:34:16 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (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 7D615129; Sun, 5 Oct 2014 12:34:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=jAcTV5aO3UurYVUkMwF3k61Xnhst4RsFxb7XySD7YdU=; b=dU0v3UTJVX/+wNCrIQGRi2uNaKsOewliTe5HZSFylCL/N6EhWUU8JgowBnX9Z17k9mbMq2dsv8qIF3trS/FEkwYrvoJs8f7EahW5uFGWXCicvIyJhCkORm3WjfWadNmAHyJFDUSVYqLDcEQ58nm3C53pQwCX2cc7M9ClqAp6T9s=; Received: from [182.1.193.13] (port=14242 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1Xal0w-004KbJ-4P; Sun, 05 Oct 2014 06:34:14 -0600 Date: Sun, 5 Oct 2014 20:34:01 +0800 From: Erich Dollansky To: Glen Barber Subject: Re: FreeBSD 10.1-RC1 Now Available --- lagg disables network inside jails Message-ID: <20141005203401.440afc31@X220.alogt.com> In-Reply-To: <20141005013247.GH1171@hub.FreeBSD.org> References: <20141005013247.GH1171@hub.FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: FreeBSD Release Engineering Team , freebsd-jail@freebsd.org, freebsd-stable@FreeBSD.org, freebsd-net@freebsd.org X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Oct 2014 12:34:16 -0000 Hi, On Sat, 4 Oct 2014 21:32:47 -0400 Glen Barber wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > The first RC build of the 10.1-RELEASE release cycle is now available I installed this shortly after your e-mail came. The result was the same as with BETA3. If you remember, I have had the problem that the network inside jails stopped working after I installed BETA3. The upgrade to RC1 did not change anything. I took now the time to investigate a bit. The result is simple. All works as expected until lagg becomes enabled. If I remember right, BETA1 was my last working version. I have an em and an iwn interface in the machine. I can use both of them without any problems. As I can reproduce this problem 100%, it might be a good idea if I help you to find the source of the problem. My problem would be: how. If somebody could tell me where to start looking for the error, we might find it soon. Erich From owner-freebsd-jail@FreeBSD.ORG Sun Oct 5 16:38:50 2014 Return-Path: Delivered-To: freebsd-jail@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 6FFB7B0A; Sun, 5 Oct 2014 16:38:50 +0000 (UTC) Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) (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 7082ABEE; Sun, 5 Oct 2014 16:38:49 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id z12so4812345wgg.1 for ; Sun, 05 Oct 2014 09:38:47 -0700 (PDT) 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=FXt2vO22Acd9nfQmxJwlvWo7CLSREI/mZ1swBTNyGCo=; b=Bf4IIFWRxhpJTvAGdQA4aXw3diAAPbhTdyCqpJJ0xjcO0rr/8m3qvRcYj7XIOfkGh1 Ta0+WKZ+qGB9AhprIDiVO6HEtXiLyLLbp2uzM0hG9QWhhMc4m39jBBDagoOlH1yM8Fwf 8XkqypGk8TIkrb6cnn3lvhlnwefdgy5s2mlW7mc8oPecFAYZ/hKoAM93EC+ukj2wDj6v CgzFoomUlNL28+E69awjvPVwLQ7jbI1lE+ZtMLfMCaH5I5AA4mXC3HGlSeC0MmH5uu2s qL1ZoT9KG6hOeyvQ8+K2BTQ0czCbJkA4jOYXyh/hYFLoeq6Pmra7ofXnkbUBDcHbsSR3 op3w== MIME-Version: 1.0 X-Received: by 10.194.57.237 with SMTP id l13mr24066398wjq.102.1412527127747; Sun, 05 Oct 2014 09:38:47 -0700 (PDT) Received: by 10.27.46.14 with HTTP; Sun, 5 Oct 2014 09:38:47 -0700 (PDT) In-Reply-To: <20141005203401.440afc31@X220.alogt.com> References: <20141005013247.GH1171@hub.FreeBSD.org> <20141005203401.440afc31@X220.alogt.com> Date: Sun, 5 Oct 2014 11:38:47 -0500 Message-ID: Subject: Re: FreeBSD 10.1-RC1 Now Available --- lagg disables network inside jails From: Scot Hetzel To: Erich Dollansky Content-Type: text/plain; charset=ISO-8859-1 Cc: Glen Barber , freebsd-jail@freebsd.org, FreeBSD Release Engineering Team , FreeBSD Stable , freebsd-net@freebsd.org X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Oct 2014 16:38:50 -0000 On Sun, Oct 5, 2014 at 7:34 AM, Erich Dollansky wrote: > Hi, > > On Sat, 4 Oct 2014 21:32:47 -0400 > Glen Barber wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> The first RC build of the 10.1-RELEASE release cycle is now available > > I installed this shortly after your e-mail came. The result was the > same as with BETA3. If you remember, I have had the problem that the > network inside jails stopped working after I installed BETA3. The > upgrade to RC1 did not change anything. > > I took now the time to investigate a bit. The result is simple. All > works as expected until lagg becomes enabled. > > If I remember right, BETA1 was my last working version. > > I have an em and an iwn interface in the machine. I can use both of them > without any problems. > > As I can reproduce this problem 100%, it might be a good idea if I help > you to find the source of the problem. My problem would be: how. > > If somebody could tell me where to start looking for the error, we > might find it soon. > You'll need to identify where in the src caused the issue for you. To do this, you will need to identify where it was working (BETA1?). You would then have to step thru the sources until you find the point where it breaks. The easiest way would be to take the svn revision that is half way between BETA1 and BETA3, compile and install it and see if it works. You keep halving the result until you identify the commit that broke it. Once the offending commit is identified, email the list. -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised. From owner-freebsd-jail@FreeBSD.ORG Mon Oct 6 00:56:25 2014 Return-Path: Delivered-To: freebsd-jail@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D85BF8E9; Mon, 6 Oct 2014 00:56:25 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (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 AEA7330C; Mon, 6 Oct 2014 00:56:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=+7UMKAiqJFV/RI4PZZYQ3LYPK9zcLgFryw4O2OrKgkg=; b=Y23houYCS4Ge/Sxi0zPkFSNDWeAqfB3usm6TTkJAr3eflXs7Qz2LlA7FZ2YaJoXW03JqkCwJ3PkA67/AZPPoXej6JUKFSnmmh/GjIPeyxVuZ8YdmiMTQAq7vLt3j6jfXp8xVPGQ89tYtuwlkLkqaezPVagVSs5D0p/qd1kNXPII=; Received: from [182.1.193.13] (port=23547 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1Xawb4-003GY4-JX; Sun, 05 Oct 2014 18:56:19 -0600 Date: Mon, 6 Oct 2014 08:56:06 +0800 From: Erich Dollansky To: Scot Hetzel Subject: Re: FreeBSD 10.1-RC1 Now Available --- lagg disables network inside jails Message-ID: <20141006085606.1d55fe5e@X220.alogt.com> In-Reply-To: References: <20141005013247.GH1171@hub.FreeBSD.org> <20141005203401.440afc31@X220.alogt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: Glen Barber , freebsd-jail@freebsd.org, FreeBSD Release Engineering Team , FreeBSD Stable , freebsd-net@freebsd.org X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Oct 2014 00:56:26 -0000 Hi, On Sun, 5 Oct 2014 11:38:47 -0500 Scot Hetzel wrote: > On Sun, Oct 5, 2014 at 7:34 AM, Erich Dollansky > wrote: > > On Sat, 4 Oct 2014 21:32:47 -0400 > > Glen Barber wrote: > > > >> The first RC build of the 10.1-RELEASE release cycle is now > >> available > > > > I installed this shortly after your e-mail came. The result was the > > same as with BETA3. If you remember, I have had the problem that the > > network inside jails stopped working after I installed BETA3. The > > upgrade to RC1 did not change anything. > > > You'll need to identify where in the src caused the issue for you. To > do this, you will need to identify where it was working (BETA1?). > You would then have to step thru the sources until you find the point > where it breaks. > > The easiest way would be to take the svn revision that is half way > between BETA1 and BETA3, compile and install it and see if it works. > You keep halving the result until you identify the commit that broke > it. > > Once the offending commit is identified, email the list. > this is what I wanted to avoid. A shame that -Dno_clean will not work here. It would save a lot of compile time without running the risk missing out some files. Anyway, I compile world and kernel just to make sure that the problem is caught. This will take some time. Erich From owner-freebsd-jail@FreeBSD.ORG Wed Oct 8 00:34:33 2014 Return-Path: Delivered-To: freebsd-jail@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DAB5DEB7; Wed, 8 Oct 2014 00:34:32 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (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 B07A1965; Wed, 8 Oct 2014 00:34:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=oKGaD4bnX6AWf2IeWTMIIbtUu9CmWuPHCo2V532FS0w=; b=WeGbWp08JcbGTZfEN5bnN5dgcM/FQkLz3dsT4rzLTgg61SHy4126RIPo5q4gLQREiDMV0gizgssAGIzalWntuJKt/RdXxihK2CYmVKAXM6B1o54jdNCl/Suz0PlaZoF1ZzfUyejnl0wBWJuP57tVXIEIYX0te14Y+/0PmEuB/FU=; Received: from [182.9.144.112] (port=47866 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1XbfD4-003JJO-K1; Tue, 07 Oct 2014 18:34:31 -0600 Date: Wed, 8 Oct 2014 08:34:24 +0800 From: Erich Dollansky To: Scot Hetzel Subject: Re: FreeBSD 10.1-RC1 Now Available --- lagg disables network inside jails Message-ID: <20141008083424.354b9d7c@X220.alogt.com> In-Reply-To: References: <20141005013247.GH1171@hub.FreeBSD.org> <20141005203401.440afc31@X220.alogt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: Glen Barber , freebsd-jail@freebsd.org, FreeBSD Release Engineering Team , FreeBSD Stable , freebsd-net@freebsd.org X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Oct 2014 00:34:33 -0000 Hi, jails work now with lagg0 again on my machine. It seems to me that it was a specific problem of this one machine. I installed the following revisions: 272555 starting point which failed 272400 failed 272000 works 272200 works 272300 works 272400 test again and it works 272400 installing world inside the jail and it works I then went to 272672 and it also works. It might was the sequence, it might was a configuration error on my side, all I know is that it works again. I also cross-compiled a kernel for the Raspberry which also works when using the latest firmware as YAMAMOTO Shigeru suggested. Erich On Sun, 5 Oct 2014 11:38:47 -0500 Scot Hetzel wrote: > On Sun, Oct 5, 2014 at 7:34 AM, Erich Dollansky > wrote: > > Hi, > > > > On Sat, 4 Oct 2014 21:32:47 -0400 > > Glen Barber wrote: > > > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA256 > >> > >> The first RC build of the 10.1-RELEASE release cycle is now > >> available > > > > I installed this shortly after your e-mail came. The result was the > > same as with BETA3. If you remember, I have had the problem that the > > network inside jails stopped working after I installed BETA3. The > > upgrade to RC1 did not change anything. > > > > I took now the time to investigate a bit. The result is simple. All > > works as expected until lagg becomes enabled. > > > > If I remember right, BETA1 was my last working version. > > > > I have an em and an iwn interface in the machine. I can use both of > > them without any problems. > > > > As I can reproduce this problem 100%, it might be a good idea if I > > help you to find the source of the problem. My problem would be: > > how. > > > > If somebody could tell me where to start looking for the error, we > > might find it soon. > > > You'll need to identify where in the src caused the issue for you. To > do this, you will need to identify where it was working (BETA1?). > You would then have to step thru the sources until you find the point > where it breaks. > > The easiest way would be to take the svn revision that is half way > between BETA1 and BETA3, compile and install it and see if it works. > You keep halving the result until you identify the commit that broke > it. > > Once the offending commit is identified, email the list. >