From owner-freebsd-bugs@freebsd.org Fri Nov 22 00:56:13 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 EEBDD1CFD57 for ; Fri, 22 Nov 2019 00:56:13 +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 47Jyfj5zWtz4B3l for ; Fri, 22 Nov 2019 00:56:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id CD2251CFD56; Fri, 22 Nov 2019 00:56:13 +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 CCE1B1CFD55 for ; Fri, 22 Nov 2019 00:56:13 +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 47Jyfj4GtMz4B3k for ; Fri, 22 Nov 2019 00:56:13 +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 763ED1BDA4 for ; Fri, 22 Nov 2019 00:56:13 +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 xAM0uDgq049173 for ; Fri, 22 Nov 2019 00:56:13 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id xAM0uDuk049172 for bugs@FreeBSD.org; Fri, 22 Nov 2019 00:56:13 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: Fri, 22 Nov 2019 00:56:10 +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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rmacklem@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: 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.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Nov 2019 00:56:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242146 --- Comment #1 from Rick Macklem --- Well, the problem with setting a limit is "how long"? I know of a FreeBSD NFS server that exports over 72,000 file systems. I suspect that startup of a server like this can take a while and some systems would simply want to retry until the server is up, I think? I also don't see much use in a panic(), since a dump or stack trace isn't useful and another reboot cycle will presumably end up in the same state. I can see that spitting out a single message to the console along the lines of "Can't connect to NFS server" would be useful, so that sysadmins would know why the boot has wedged.=20 I'll have to take a look at the code to see if the mount root case can be identified where it loops attempting reconnects, so a message can be generated for that case. I think newnfs_connect() does the socreate() and returns an error when it fails. However, newnfs_request() ignores any error return, so a message could possibly be generated there. All of the above is just mho. I think you should ask on a mailing list (FreeBSD-fs@ maybe?) to see what others think is the correct behaviour for this case. --=20 You are receiving this mail because: You are the assignee for the bug.=