Re: local-unbound stopped working after upgrade to 13.2

2023-09-18 Thread Cy Schubert
In message , Yuri writes: > Chris wrote: > > On 2023-09-18 08:26, Yuri wrote: > >> Chris wrote: > >>> On 2023-09-17 11:15, Alain Zscheile wrote: > Hi, > > After upgrading from FreeBSD-13.1 to 13.2 I noticed that local-unbound > doesn't > appear to work anymore > (doesn

Re: vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available)

2023-09-18 Thread Kyle Evans
On 9/18/23 16:37, Tomoaki AOKI wrote: At least, if I read the code correctly, "com.fudosecurity:block_cloning", should be added to array *features_for_read[] of stand/libsa/zfs/zfsimpl.c. There are check codes like below, so without it, boot codes would reject to boot from any pool hav

Re: vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available)

2023-09-18 Thread Tomoaki AOKI
At least, if I read the code correctly, "com.fudosecurity:block_cloning", should be added to array *features_for_read[] of stand/libsa/zfs/zfsimpl.c. There are check codes like below, so without it, boot codes would reject to boot from any pool having block_cloning feature enabled. Am I mi

Re: local-unbound stopped working after upgrade to 13.2

2023-09-18 Thread Yuri
Chris wrote: > On 2023-09-18 08:26, Yuri wrote: >> Chris wrote: >>> On 2023-09-17 11:15, Alain Zscheile wrote: Hi, After upgrading from FreeBSD-13.1 to 13.2 I noticed that local-unbound doesn't appear to work anymore (doesn't return DNS responses for anything, although

Re: local-unbound stopped working after upgrade to 13.2

2023-09-18 Thread Chris
On 2023-09-18 08:26, Yuri wrote: Chris wrote: On 2023-09-17 11:15, Alain Zscheile wrote: Hi, After upgrading from FreeBSD-13.1 to 13.2 I noticed that local-unbound doesn't appear to work anymore (doesn't return DNS responses for anything, although I don't have network traces). For now, I just

Re: local-unbound stopped working after upgrade to 13.2

2023-09-18 Thread Yuri
Chris wrote: > On 2023-09-17 11:15, Alain Zscheile wrote: >> Hi, >> >> After upgrading from FreeBSD-13.1 to 13.2 I noticed that local-unbound >> doesn't >> appear to work anymore >> (doesn't return DNS responses for anything, although I don't have >> network traces). >> >> For now, I just disabled

Re: local-unbound stopped working after upgrade to 13.2

2023-09-18 Thread Chris
On 2023-09-17 11:15, Alain Zscheile wrote: Hi, After upgrading from FreeBSD-13.1 to 13.2 I noticed that local-unbound doesn't appear to work anymore (doesn't return DNS responses for anything, although I don't have network traces). For now, I just disabled it on all my systems, but I believ

Re: local-unbound stopped working after upgrade to 13.2

2023-09-18 Thread Michael Proto
On Sun, Sep 17, 2023 at 2:15 PM Alain Zscheile wrote: > Hi, > > After upgrading from FreeBSD-13.1 to 13.2 I noticed that local-unbound > doesn't appear to work anymore > (doesn't return DNS responses for anything, although I don't have network > traces). > > For now, I just disabled it on all my

Re: vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available)

2023-09-18 Thread Alexander Motin
block_cloning feature is marked as READONLY_COMPAT. It should not require any special handling from the boot code. On 18.09.2023 07:22, Tomoaki AOKI wrote: Really OK? I cannot find block_cloning in array *features_for_read[] of stand/libsa/zfs/zfsimpl.c, which possibly mean boot codes (includ

Re: vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available)

2023-09-18 Thread Tomoaki AOKI
(Intentionally dropped @gmail.com recipients, as gmail refuses to accept emaif from my email domain, unfortunately.) Really OK? I cannot find block_cloning in array *features_for_read[] of stand/libsa/zfs/zfsimpl.c, which possibly mean boot codes (including loader) cannot boot from Root-on-ZFS po

Re: vfs.zfs.bclone_enabled (was: FreeBSD 14.0-BETA2 Now Available)

2023-09-18 Thread Mark Johnston
On Mon, Sep 18, 2023 at 07:31:46AM +0200, Martin Matuska wrote: > I vote for enabling block cloning on main :-) Have you or anyone else run through the test suite with block cloning enabled? > On 16. 9. 2023 19:14, Alexander Motin wrote: > > On 16.09.2023 01:25, Graham Perrin wrote: > > > On 16/0