Date: Fri, 6 Nov 2020 21:58:14 +0100 From: Mateusz Guzik <mjguzik@gmail.com> To: Andriy Gapon <avg@freebsd.org> Cc: freebsd-current@freebsd.org, freebsd-fs@freebsd.org Subject: Re: panic: VERIFY(ZFS_TEARDOWN_READ_HELD(zfsvfs)) failed Message-ID: <CAGudoHHmBW64HsKq8h8y4_8e9WMqpFgzx2XikpcRCz9=EmRwEQ@mail.gmail.com> In-Reply-To: <98c87b4f-4327-8a19-cf51-f3a14e42edf4@FreeBSD.org> References: <98c87b4f-4327-8a19-cf51-f3a14e42edf4@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Note the underlying primitive was recently replaced. One immediate thing to check would be exact state of the lock. READ_HELD checks for reading only, fails if you have this write-locked, which is a plausible explanation if you are coming in from less likely codepath. iow what's the backtrace and can you print both rms->readers and rms->owner (+ curthread) On 11/6/20, Andriy Gapon <avg@freebsd.org> wrote: > > The subject panic happens for me with r367410 when mounting root > filesystem. > The panic is in zfs_freebsd_cached_lookup -> zfs_lookup -> zfs_dirlook. > I have a picture of the screen with a little bit more details, I'll share it > later. > > -- > Andriy Gapon > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Mateusz Guzik <mjguzik gmail.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGudoHHmBW64HsKq8h8y4_8e9WMqpFgzx2XikpcRCz9=EmRwEQ>