Date: Fri, 1 Apr 2022 13:40:39 +1000 From: George Michaelson <ggm@algebras.org> To: Warner Losh <imp@bsdimp.com> Cc: FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: CAM timeouts on boot (13.0-p8, Dell R730xd, mrsas controller) Message-ID: <CAKr6gn05CLzYE-%2BnJScsSUqZHTZ%2B21f%2BGRUcXa%2BC8isPypV7bw@mail.gmail.com> In-Reply-To: <CAKr6gn3dh_Os9-hWjOk_qgWdUHwjfdN1MSFQLqz-3zuHn0SegQ@mail.gmail.com> References: <CAKr6gn1KEk5T0W6yJniKKSfHYaNdGh=BhS5LUJ=Htg2mWeTR5g@mail.gmail.com> <CANCZdfryHTfA0gTs6eEkMG9x6WxDo%2BsMijQqJuUbEdaO%2B546pA@mail.gmail.com> <CAKr6gn3dh_Os9-hWjOk_qgWdUHwjfdN1MSFQLqz-3zuHn0SegQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I checked /boot/zfs/zpool.cache and /etc/zfs/zpool.cache both have the tank in question, zdb agrees, they are identical, multiple reboots re-tested: without a manual zpool import tank, only the zfs zroot which is magically mounted appears. The other tank does not unless you call it into being. Doing that after multiuser/daemon is bad if your daemons work in it. (and bad for NFS exports) The zfs pages are a bit cryptic about altroot and other zpool get all values, but the basics seem to be that if you do zpool import, and its in cache, then it should be detected during zfs/zpool activation. People expect that once you import, it will re-import automatically thereafter unless you tell it not to. I checked zpool values on a system which doesnt have the problem and I don't see any variance for zpool params. zpool.cache was the recommended "have you checked" reference. Not that this can't be PBCAK, but I have tried not to be the root cause here. It happened across my upgrade, and the CAM timeout intruded in the same window. G On Fri, Apr 1, 2022 at 1:31 PM George Michaelson <ggm@algebras.org> wrote: > > Thanks for the cluestick. I don't disagree with anything you said btw. > > Here's the dmesg. (attachment, can in-line if thats better)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKr6gn05CLzYE-%2BnJScsSUqZHTZ%2B21f%2BGRUcXa%2BC8isPypV7bw>