On 20.05.2022 15:12, Bryan Drewery wrote:
On 5/20/2022 12:04 PM, Shawn Webb wrote:
On Wed, May 18, 2022 at 11:05:54PM +0000, Martin Matuska wrote:
The branch main has been updated by mm:
URL:https://cgit.FreeBSD.org/src/commit/?id=716fd348e01c5f2ba125f878a634a753436c2994
commit 716fd348e01c5f2ba125f878a634a753436c2994
Merge: 4e2d3f26bd12 c0cf6ed6792e
Author: Martin Matuska<m...@freebsd.org>
AuthorDate: 2022-05-18 22:54:40 +0000
Commit: Martin Matuska<m...@freebsd.org>
CommitDate: 2022-05-18 22:55:59 +0000
zfs: merge openzfs/zfs@c0cf6ed67
Notable upstream pull request merges:
#10662 zvol_wait: Ignore locked zvols
#12789 Improve log spacemap load time
#12812 Improved zpool status output, list all affected datasets
#13277 FreeBSD: Use NDFREE_PNBUF if available
#13302 Make zfs_max_recordsize default to 16M
#13311 Fix error handling in FreeBSD's get/putpages VOPs
#13345 FreeBSD: Fix translation from ABD to physical pages
#13373 zfs: holds: dequadratify
#13375 Corrected edge case in uncompressed ARC->L2ARC handling
#13388 Improve mg_aliquot math
#13405 Reduce dbuf_find() lock contention
#13406 FreeBSD: use zero_region instead of allocating a
dedicated page
Obtained from: OpenZFS
OpenZFS commit: c0cf6ed6792e545fd614c2a88cb53756db7e03f8
Hey Martin,
This may be the cause of recent ZFS-related kernel panics on the
HardenedBSD 14-CURRENT/amd64 package build server. I've uploaded the
core.txt file at [0].
[0]:https://hardenedbsd.org/~shawn/2022-05-20_core.txt.3.txt
[6710] panic: VERIFY(e->lse_mscount != 0) failed
I hit this just a few minutes ago too.
https://github.com/openzfs/zfs/issues/13486
I believe it is a wrong assertion, not a real bug:
https://github.com/openzfs/zfs/pull/13513
--
Alexander Motin
