On 04/03/2019 22:35, Nick Rogers wrote:
> v_lock = {lock_object = {lo_name =
> 0xffffffff8144af45 "zfs", lo_flags = 117112840, lo_data = 0, lo_witness =
> 0x0}, lk_lock = 18446744073709551605, lk_exslpfail = 0, lk_timo = 51,
> lk_pri = 96}Hmm, lk_lock looks bogus. 18446744073709551605 == 0xfffffffffffffff5 and it's LK_SHARE | LK_EXCLUSIVE_WAITERS with 0xfffffffffffffff shared owners. Perhaps, this is a result of LK_SHARERS_LOCK(-1). Is your kernel compiled with INVARIANTS and INVARIANT_SUPPORT? I suspect that the vnode was accessed (unlocked?) through a stale pointer after it was recycled. -- Andriy Gapon _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
