Alexander Motin
Alexander Motin
I've noticed that it works as a pool property (i.e. without "all-vdevs"), but not for individual vdevs.
Log and cache removal are a very different beasts. They do not use the device removal code, not moving any data, etc. Though may be possible to document in better...
For the first, this has nothing to do with scrub. Read back would have to happen similar to writing of l2arc_feed_thread, matching its speed. But since the logic of L2ARC...
We can not keep all the old metadata, if not for other reasons, then just because current persistent L2ARC implementation during replay often resurrects blocks there were deleted earlier until...
The panic was introduced in #17078. @asomers ^^^ FYI.
I think I might have an idea what's going on, but please answer one question: what recordsize do you have on that dataset and was it the same in 2018...
I don't know if it will be enough for your case, but this should be a step in the right direction: https://github.com/openzfs/zfs/pull/17431 .
Huh. Thanks for the update. I've suspected that change, even while being right, might be not enough.
> well at least on Arch 6.15.2 there were quite a few fails [archzfs/archzfs#594 (comment)](https://github.com/archzfs/archzfs/pull/594#issuecomment-2984907171) I have some doubts about validity of the test. Too many errors at once, while...
It crashes on `VERIFY(!dmu_objset_is_dirty(dp->dp_meta_objset, txg))`.