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_at_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_at_freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" > -- Mateusz Guzik <mjguzik gmail.com>Received on Fri Nov 06 2020 - 19:58:20 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:25 UTC