From owner-freebsd-bugs@freebsd.org Thu Nov 21 19:10:24 2019 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 0A9D31C83A5 for ; Thu, 21 Nov 2019 19:10:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 47Jpzg6bJfz3Jjq for ; Thu, 21 Nov 2019 19:10:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id E066D1C83A4; Thu, 21 Nov 2019 19:10:23 +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 E02381C83A3 for ; Thu, 21 Nov 2019 19:10:23 +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) server-signature RSA-PSS (4096 bits) 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 47Jpzg5jTpz3Jjn for ; Thu, 21 Nov 2019 19:10:23 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id A8055FCD4 for ; Thu, 21 Nov 2019 19:10:23 +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 xALJANbS029216 for ; Thu, 21 Nov 2019 19:10:23 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id xALJANtm029215 for bugs@FreeBSD.org; Thu, 21 Nov 2019 19:10:23 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 242146] nfs root mount may loop endlessly without hint on console Date: Thu, 21 Nov 2019 19:10:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: bz@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: 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.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Nov 2019 19:10:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242146 Bug ID: 242146 Summary: nfs root mount may loop endlessly without hint on console Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: bz@FreeBSD.org CC: rmacklem@FreeBSD.org If we are trying to mount the root file system over NFS and cannot establis= h a connection we do never give up. TCP/2049 packets arrive at the server, RST comes back. The reason is in newnfs_request() which seems to jump back to tryagain; at least that is my guess for the loop as I couldn't spot it earlier and the socreate() is part of the loop: 1599 XXX-BZ socreate:553^M 1600 XXX-BZ tcp_usr_attach:155 fff 4^M 1601 XXX-BZ tcp_usr_attach:161^M 1602 XXX-BZ tcp_usr_attach:171 error 0^M 1603 XXX-BZ socreate:553^M 1604 XXX-BZ tcp_usr_attach:155 fff 5^M 1605 XXX-BZ tcp_usr_attach:161^M 1606 XXX-BZ tcp_usr_attach:171 error 0^M 1607 XXX-BZ socreate:553^M 1608 XXX-BZ tcp_usr_attach:155 fff 6^M 1609 XXX-BZ tcp_usr_attach:161^M 1610 XXX-BZ tcp_usr_attach:171 error 0^M 1611 XXX-BZ socreate:553^M 1612 XXX-BZ tcp_usr_attach:155 fff 7^M 1613 XXX-BZ tcp_usr_attach:161^M 1614 XXX-BZ tcp_usr_attach:171 error 0^M I added a panic if I come by 15 times to get a backtrace. panic() at panic+0x43/frame 0xfffffe00acf58b70 tcp_usr_attach() at tcp_usr_attach+0x2b7/frame 0xfffffe00acf58be0 socreate() at socreate+0x1ce/frame 0xfffffe00acf58c30 __rpc_nconf2socket() at __rpc_nconf2socket+0x3f/frame 0xfffffe00acf58c60 clnt_reconnect_call() at clnt_reconnect_call+0x3b6/frame 0xfffffe00acf58d10 newnfs_request() at newnfs_request+0x90b/frame 0xfffffe00acf58e80 nfsrpc_getattrnovp() at nfsrpc_getattrnovp+0xeb/frame 0xfffffe00acf59020 mountnfs() at mountnfs+0x6b6/frame 0xfffffe00acf591c0 nfs_mount() at nfs_mount+0x11d3/frame 0xfffffe00acf59500 vfs_mount_sigdefer() at vfs_mount_sigdefer+0x24/frame 0xfffffe00acf59520 vfs_domount() at vfs_domount+0x7f9/frame 0xfffffe00acf59750 vfs_donmount() at vfs_donmount+0x911/frame 0xfffffe00acf597f0 kernel_mount() at kernel_mount+0x57/frame 0xfffffe00acf59840 parse_mount() at parse_mount+0x4a1/frame 0xfffffe00acf59990 vfs_mountroot() at vfs_mountroot+0x53b/frame 0xfffffe00acf59b10 start_init() at start_init+0x28/frame 0xfffffe00acf59bb0 I would suggest we'd rather really timeout / error after retries and possibly reboot or fail mountroot or whatever it'll be, rather than being s= tuck in a loop without letting the user know that "NFS server not reachable: connection refused". --=20 You are receiving this mail because: You are the assignee for the bug.=