From owner-freebsd-bugs@freebsd.org Thu Nov 26 00:48:18 2020 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 356E9478FCD for ; Thu, 26 Nov 2020 00:48:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4ChJyp0rWWz4hPK for ; Thu, 26 Nov 2020 00:48:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 1B4B44792C8; Thu, 26 Nov 2020 00:48:18 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1B142478F5C for ; Thu, 26 Nov 2020 00:48:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ChJyn5gwFz4hPH for ; Thu, 26 Nov 2020 00:48:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B4D331A7AC for ; Thu, 26 Nov 2020 00:48:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 0AQ0mHUA020701 for ; Thu, 26 Nov 2020 00:48:17 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 0AQ0mH7a020700 for bugs@FreeBSD.org; Thu, 26 Nov 2020 00:48:17 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 251347] NFS hangs on client side when mounted from outside in Jail Tree (BROKEN NFS SERVER OR MIDDLEWARE) Date: Thu, 26 Nov 2020 00:48:17 +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: 12.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: arne@Steinkamm.COM X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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.34 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Nov 2020 00:48:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251347 --- Comment #7 from Arne Steinkamm --- (In reply to Rick Macklem from comment #6) Thanks Rick, as said before: Using NFSv4 changes nothing :-( I'm unable to change the wiring because the complete setup is in a computer center 600km from here but I have access to all lights out service processo= rs, the switches, etc. I have the same problem now with a Linux NFS server so I think the problem = is not on the server side. To make the picture clearer: two main administrative servers: adm001 and adm002 Both have a couple of VNET jails (if_bridge, not netgraph) running nameserv= er etc. And both have so called login server jails. Just a jail where the people can ssh too and jump (ssh) inside the development networks. Two fileserver, one Linux one FreeBSD share the $HOMEs and a pool share. These are mounted at adm001 and amd002 to /l/home and /l/pool. NULLFS mounts forward these in the two login jails: /l/home --> /l/prison/login1/l/home and /l/pool --> /l/prison/login1/l/pool. Same procedure on adm002 with login002. After 30 seconds to 60 minutes one of the two NFS mounts freezes. df, ls, umount etc. hang. And now the strange part: "sh /etc/rc.d/jail stop login1" immediately unfreezes the NFS mount and everything is working normal again = but, of course, without the jail. In the second the Jail is dead the "BROKEN NFS..." text is displayed only on the console, not in dmesg buffer or log files and, this is strange, only on adm001. adm001 and adm002 are different hardware (other CPU) but there are clones, = real clones made with zfs send/receive. Of course the hostids are different. The workaround is to allow the users to use adm001 and adm002 directly. But this is not the way we want to have it. When I don't use the NULLFS and make two independent NFS mounts to /l/home = and /l/prison/login1/l/home then only the second freezes. I guess this is not normal and a real bug...=20 Any help? Thanks in advance .//. Arne --=20 You are receiving this mail because: You are the assignee for the bug.=