From owner-freebsd-stable@FreeBSD.ORG Sun Jan 5 22:26:33 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4650ECBF for ; Sun, 5 Jan 2014 22:26:33 +0000 (UTC) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 144D519B9 for ; Sun, 5 Jan 2014 22:26:32 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1Vzw9J-0005Q0-UD; Sun, 05 Jan 2014 22:26:26 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id s05MQNbl026711; Sun, 5 Jan 2014 15:26:23 -0700 (MST) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19UYRK1vC4NXzm5cDlw4O/E Subject: Re: How to make boot wait a few seconds more for device response? From: Ian Lepore To: kpneal@pobox.com In-Reply-To: <20140105221507.GA70312@neutralgood.org> References: <43.76.14229.524B7C25@cdptpa-oedge01> <52C7EC3E.6070709@grosbein.net> <20140104213749.GA60414@neutralgood.org> <1388873531.1158.306.camel@revolution.hippie.lan> <674003.48630.bm@smtp114.sbc.mail.gq1.yahoo.com> <1388936456.1158.308.camel@revolution.hippie.lan> <466613.61666.bm@smtp120.sbc.mail.bf1.yahoo.com> <1388956579.1158.326.camel@revolution.hippie.lan> <20140105221507.GA70312@neutralgood.org> Content-Type: text/plain; charset="us-ascii" Date: Sun, 05 Jan 2014 15:26:23 -0700 Message-ID: <1388960783.1158.328.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jan 2014 22:26:33 -0000 On Sun, 2014-01-05 at 17:15 -0500, kpneal@pobox.com wrote: > On Sun, Jan 05, 2014 at 02:16:19PM -0700, Ian Lepore wrote: > > On Sun, 2014-01-05 at 21:06 +0000, Thomas Mueller wrote: > > > > I don't know whether it's documented anywhere, I just remembered seeing > > > > it in the source when I was working on a change to nfs root filesystems, > > > > so I grepped and re-found it yesterday. I think it's set in terms of > > > > whole seconds. > > > > > > -- Ian > > > > > > This was for vfs.mountroot.timeout . > > > > > > There needs to be better documentation. I have already searched for too many needles in the haystack and lost a lot of time that way. > > > > > > I could type "show" at loader prompt, but figure only a small chance of finding everything, output may be sketchy. > > > > > > So I still don't know whether it should be seconds or milliseconds. > > > > > > Where did you find it in the source tree? I made another search, unsuccessful, for the needle in the haystack. > > > > > > Tom > > > > Yes, for vfs.mountroot.timeout the units are whole seconds. > > > > It's implemented in src/sys/kern/vfs_mountroot.c > > Is this in 9.2-RELEASE? I'm looking at that file myself and I can't see > where exactly that option is checked. I do see this: > > parse_dir_ask_printenv("vfs.root.mountfrom"); > parse_dir_ask_printenv("vfs.root.mountfrom.options"); > > I also see ".timeout" checked when parsing input from somewhere. I can't > tell where exactly it is coming from, though. But I can't see where it > checks specifically for "vfs.mountroot.timeout". > > Am I misreading it? Or is it not present in 9.2-RELEASE? > > Sorry to be a pain on this, but I'm looking to avoid trouble with a > machine I'm upgrading remotely. I want to be sure before I pull the > trigger. Hrm, it looks like in 9.2-RELEASE it's just hard-coded to 3 seconds and not tuneable. In 9-stable it's tuneable. -- Ian