Date: Mon, 05 Dec 2022 16:52:19 +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-f5oxlYYaaw@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 --- Comment #6 from Barney Wolff <barneywolff@gmail.com> --- Does appear to be the same problem. As I read the zpool_main code, import -a processes cache file entries sequentially, so if one import fails badly, others will not get done. One brute-force fix for that would be to fork for each one. Presumably there is already code to serialize updates to the cache file, as potentially multiple root processes could do imports simultaneously. I think it's an open question what import should do if a vdev doesn't exist (yet). It might wait forever. I don't know how usb signals that it's done, = or whether zpool import can know if there are any usb vdevs, so always waiting= for usb to finish doesn't seem right. In my own case waiting for root mount would not help, as root is on the sd = card while I want usr, var, home on a usb disk pool. --=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-f5oxlYYaaw>