Date: Thu, 08 Dec 2022 01:06:47 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 268157] /etc/rc.d/zpool runs too early, before usb disks available Message-ID: <bug-268157-3630-88cESDD7tS@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268157-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-268157-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268157 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #11 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Daniel Engberg from comment #8) Possibly: # sysctl -d kern.cam.boot_delay kern.cam.boot_delay: Bus registration wait time I generally have /boot/loader.conf contain: kern.cam.boot_delay=3D10000 because of some history of running into an issue that it avoided. Too bad no units for the time are indicated. ms if I infer correctly. I also use: vfs.mountroot.timeout=3D10 vfs.root_mount_always_wait=3D1 but those would only be indirectly useful for other media -- and possibly only if the root mount was the slowest. # sysctl -d vfs.root_mount_always_wait vfs.root_mount_always_wait: Wait for root mount holds even if the root device already exists vfs.mountroot.timeout is not in sysctl. Again no time-unit indication. Seconds if I infer correctly. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268157-3630-88cESDD7tS>