Am 2024-01-02 00:40, schrieb Lexi Winter:
hello,
i'm having an issue with bridge(4) and IPv6, with a configuration which
is essentially identical to a working system running releng/14.0.
ifconfig:
lo0: flags=1008049 metric 0 mtu
16384
options=680003
inet 127.0.0.1 netmask 0xf
Hi!
> Am 2023-12-31 19:34, schrieb Kurt Jaeger:
> > I already have
> >
> > vfs.zfs.dmu_offset_next_sync=0
> >
> > which is supposed to disable block-cloning.
>
> It isn't. This one is supposed to fix an issue which is unrelated to block
> cloning (but can be amplified by block cloning). This is
Am 2023-12-31 19:34, schrieb Kurt Jaeger:
I already have
vfs.zfs.dmu_offset_next_sync=0
which is supposed to disable block-cloning.
It isn't. This one is supposed to fix an issue which is unrelated to
block cloning (but can be amplified by block cloning). This issue is
fixed since some week
On Mon, Jan 01, 2024 at 02:27:17PM +0100, Kurt Jaeger wrote:
> > On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote:
> > > markj@ pointed me in
> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039
> > > to
> > > https://github.com/openzfs/zfs/pull/15719
> > >
> > > So it will p
hello,
i'm having an issue with bridge(4) and IPv6, with a configuration which
is essentially identical to a working system running releng/14.0.
ifconfig:
lo0: flags=1008049 metric 0 mtu 16384
options=680003
inet 127.0.0.1 netmask 0xff00
inet6 ::1 prefixlen 128
On Mon, Jan 01, 2024 at 08:42:26AM -0800, John Kennedy wrote:
> Applying the two ZFS kernel patches fixes that issue:
commit 09af4bf2c987f6f57804162cef8aeee05575ad1d (zfs: Fix SPA sysctl handlers)
landed too.
root@bsd15:~ # sysctl -a | grep vfs.zfs.zio
vfs.zfs.zio.deadman_log_a
On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote:
> > > I can crash mine with "sysctl -a" as well.
>
> markj@ pointed me in
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039
> to
> https://github.com/openzfs/zfs/pull/15719
>
> So it will probably be fixed sooner or later.
>
On Mon, Jan 01, 2024 at 02:27:17PM +0100, Kurt Jaeger wrote:
> Do you have
>vfs.zfs.dmu_offset_next_sync=0
I didn't initially, I do now. Like I said, I haven't been following that one
100%. I know it isn't block-clone per say, so much as some underlying problem
it pokes with a pointy s
Hi!
> On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote:
> > markj@ pointed me in
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039
> > to
> > https://github.com/openzfs/zfs/pull/15719
> >
> > So it will probably be fixed sooner or later.
> >
> > The other ZFS crashes I've
On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote:
> markj@ pointed me in
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039
> to
> https://github.com/openzfs/zfs/pull/15719
>
> So it will probably be fixed sooner or later.
>
> The other ZFS crashes I've seen are still an issue
10 matches
Mail list logo