JMoVS
JMoVS
@lundman Close this issue or is this still a thing we *could* have and maybe *should* have?
is the leak gone? :D
and another one of those I think: ``` *** Panic Report *** panic(cpu 2 caller 0xffffff7f9e92f6c9): avl_find() succeeded inside avl_add() Backtrace (CPU 2), Frame : Return Address 0xffffff91787bb680 : 0xffffff801b5ad6ed...
this kernel panic only happens for me if there are 2 imports going on of the same pool at the same time I think.
what is the ZVOL problem that has been reintroduced by this fix? What to be aware of?
@rottegift There was a pretty bad resilver/scrub commit in that was fixed by @lundman a while back that I hit with all kinds of funkyness regarding replacing and resilvering devices....
I tried to reproduce, this is what I get on a MacBook Air Core i7 and High Sierra 10.13.5 (that is with lz4 but without zfs encryption and instead on...
I recommend running `chown -r $user /path/to/dataset/mountpoint` to get rid of it ;-)
ah saw your edit. I'm sorry, don't know any other way, maybe @lundman has an idea?