[Bug 275764] `uniq -D -c` gives wrong values of repeat counts

2023-12-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275764 Daniel Tameling changed: What|Removed |Added CC||tamelingdan...@gmail.com --- Com

[Bug 261538] zfs panic: VERIFY3(l->blk_birth == r->blk_birth) failed

2023-12-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261538 Kurt Jaeger changed: What|Removed |Added Assignee|b...@freebsd.org|f...@freebsd.org -- You are receivi

Re: [Bug 275943] PF Ether Rules : High Cpu Usage

2023-12-26 Thread Oleksandr Kryvulia
26.12.23 13:34, bugzilla-nore...@freebsd.org: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275943 Bug ID: 275943 Summary: PF Ether Rules : High Cpu Usage Product: Base System Version: 14.0-RELEASE Hardware: amd64 O

[Bug 275943] PF Ether Rules : High Cpu Usage

2023-12-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275943 Bug ID: 275943 Summary: PF Ether Rules : High Cpu Usage Product: Base System Version: 14.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Aff

[Bug 261538] zfs panic: VERIFY3(l->blk_birth == r->blk_birth) failed

2023-12-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261538 --- Comment #6 from Kurt Jaeger --- (In reply to Kurt Jaeger from comment #5) zfs destroy on one of those will cause the crash. Rebooting with the patch crashes (commented-out assert in with: panic: VERIFY(BP_GET_DEDUP(bp)) failed There

[Bug 261538] zfs panic: VERIFY3(l->blk_birth == r->blk_birth) failed

2023-12-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261538 --- Comment #5 from Kurt Jaeger --- (In reply to Kurt Jaeger from comment #4) It looks like I have some zfs clones left over from the first crash: zroot/pou/jails/150-default-ref/01 569M 252G 2.80G /pou/data/.m/150-default/01 zroot/po

[Bug 261538] zfs panic: VERIFY3(l->blk_birth == r->blk_birth) failed

2023-12-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261538 --- Comment #4 from Kurt Jaeger --- After updating my ports builder to HEAD around 23th of December 2023, I ran into the same problem. -- You are receiving this mail because: You are the assignee for the bug.