On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote:
> On 01.01.2024 08:59, John Kennedy wrote:
> > ...
> >My poudriere build did eventually fail as well:
> > ...
> > [05:40:24] [01] [00:17:20] Finished devel/gdb@py39 | gdb-13.2_1: Success
> > [05:40:24] Stopping 2
On 01.01.2024 08:59, John Kennedy 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 probably be fixed sooner or later.
The other ZFS crashes
Hi all,
> Am 02.01.2024 um 13:56 schrieb Jan Bramkamp :
>
> IPv6 enabled interfaces need a link-local address for normal operation.
> Please set the auto-linklocal flag on the bridge and try again.
And remove the link-local address from alc0. A bridge member must not have
any layer 3 addresses
On 02.01.24 00:40, Lexi Winter wrote:
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
Am 2024-01-02 08:22, schrieb Kurt Jaeger:
Hi!
The sysctl for block cloning is vfs.zfs.bclone_enabled.
To check if a pool has made use of block cloning:
zpool get all poolname | grep bclone
One more thing:
I have two pools on that box, and one of them has some bclone files:
# zpool get
Hi!
> The sysctl for block cloning is vfs.zfs.bclone_enabled.
> To check if a pool has made use of block cloning:
> zpool get all poolname | grep bclone
One more thing:
I have two pools on that box, and one of them has some bclone files:
# zpool get all ref | grep bclone
ref bcloneused
