Re: crash zfs_clone_range()

Response below Van: Konstantin Belousov Datum: zondag, 12 november 2023 19:47 Aan: Alexander Motin CC: Ronald Klop , curr...@freebsd.org Onderwerp: Re: crash zfs_clone_range() On Sun, Nov 12, 2023 at 11:51:40AM -0500, Alexander Motin wrote: > Hi Ronald, > > As I can see, the clone request to

Re: crash zfs_clone_range()

Van: Ronald Klop Datum: dinsdag, 14 november 2023 13:59 Aan: Konstantin Belousov CC: Alexander Motin , curr...@freebsd.org Onderwerp: Re: crash zfs_clone_range() Response below Van: Konstantin Belousov Datum: zondag, 12 november 2023 19:47 Aan: Alexander Motin CC: Ronald Klop ,

Re: crash zfs_clone_range()

On 11/14/23, Ronald Klop wrote: > Response below > > Van: Konstantin Belousov > Datum: zondag, 12 november 2023 19:47 > Aan: Alexander Motin > CC: Ronald Klop , curr...@freebsd.org > Onderwerp: Re: crash zfs_clone_range() >> >> On Sun, Nov 12, 2023 at 11:51:40AM -0500, Alexander Motin wrote: >>

Re: crash zfs_clone_range()

On Tue, Nov 14, 2023 at 06:47:46PM +0100, Mateusz Guzik wrote: > On 11/14/23, Alexander Motin wrote: > > On 14.11.2023 12:39, Mateusz Guzik wrote: > >> One of the vnodes is probably not zfs, I suspect this will do it > >> (untested): > >> > >> diff --git

Re: crash zfs_clone_range()

On Tue, Nov 14, 2023 at 07:51:39PM +0100, Mateusz Guzik wrote: > On 11/14/23, Alexander Motin wrote: > > On 14.11.2023 12:44, Alexander Motin wrote: > >> On 14.11.2023 12:39, Mateusz Guzik wrote: > >>> One of the vnodes is probably not zfs, I suspect this will do it > >>> (untested): > >>> > >>>

Re: crash zfs_clone_range()

On 14.11.2023 12:39, Mateusz Guzik wrote: One of the vnodes is probably not zfs, I suspect this will do it (untested): diff --git a/sys/contrib/openzfs/module/os/freebsd/zfs/zfs_vnops_os.c b/sys/contrib/openzfs/module/os/freebsd/zfs/zfs_vnops_os.c index 107cd69c756c..e799a7091b8e 100644 ---

Re: crash zfs_clone_range()

On 11/14/23, Alexander Motin wrote: > On 14.11.2023 12:39, Mateusz Guzik wrote: >> One of the vnodes is probably not zfs, I suspect this will do it >> (untested): >> >> diff --git a/sys/contrib/openzfs/module/os/freebsd/zfs/zfs_vnops_os.c >>

Re: crash zfs_clone_range()

On 14.11.2023 12:44, Alexander Motin wrote: On 14.11.2023 12:39, Mateusz Guzik wrote: One of the vnodes is probably not zfs, I suspect this will do it (untested): diff --git a/sys/contrib/openzfs/module/os/freebsd/zfs/zfs_vnops_os.c b/sys/contrib/openzfs/module/os/freebsd/zfs/zfs_vnops_os.c

Re: crash zfs_clone_range()

On 11/14/23, Alexander Motin wrote: > On 14.11.2023 12:44, Alexander Motin wrote: >> On 14.11.2023 12:39, Mateusz Guzik wrote: >>> One of the vnodes is probably not zfs, I suspect this will do it >>> (untested): >>> >>> diff --git a/sys/contrib/openzfs/module/os/freebsd/zfs/zfs_vnops_os.c >>>

Re: [HEADS-UP] Quick update to 14.0-RELEASE schedule

On Tue, Nov 14, 2023 at 08:36:54PM +, Glen Barber wrote: > We are still waiting for a few (non-critical) things to complete before > the announcement of 14.0-RELEASE will be ready. > > It should only be another day or so before these things complete. > > Thank you for your understanding. >

Re: [HEADS-UP] Quick update to 14.0-RELEASE schedule

On Tue, Nov 14, 2023 at 05:15:48PM -0700, The Doctor wrote: > On Tue, Nov 14, 2023 at 08:36:54PM +, Glen Barber wrote: > > We are still waiting for a few (non-critical) things to complete before > > the announcement of 14.0-RELEASE will be ready. > > > > It should only be another day or so

Re: crash zfs_clone_range()

On 11/14/23, Rick Macklem wrote: > On Tue, Nov 14, 2023 at 10:46 AM Alexander Motin wrote: >> >> On 14.11.2023 12:44, Alexander Motin wrote: >> > On 14.11.2023 12:39, Mateusz Guzik wrote: >> >> One of the vnodes is probably not zfs, I suspect this will do it >> >> (untested): >> >> >> >> diff

Re: crash zfs_clone_range()

On Tue, Nov 14, 2023 at 1:20 PM Konstantin Belousov wrote: > > On Tue, Nov 14, 2023 at 06:47:46PM +0100, Mateusz Guzik wrote: > > On 11/14/23, Alexander Motin wrote: > > > On 14.11.2023 12:39, Mateusz Guzik wrote: > > >> One of the vnodes is probably not zfs, I suspect this will do it > > >>

[HEADS-UP] Quick update to 14.0-RELEASE schedule

We are still waiting for a few (non-critical) things to complete before the announcement of 14.0-RELEASE will be ready. It should only be another day or so before these things complete. Thank you for your understanding. Glen On behalf of: re@ signature.asc Description: PGP signature

Re: crash zfs_clone_range()

On Tue, Nov 14, 2023 at 01:30:25PM -0800, Rick Macklem wrote: > On Tue, Nov 14, 2023 at 1:20 PM Konstantin Belousov > wrote: > > > > On Tue, Nov 14, 2023 at 06:47:46PM +0100, Mateusz Guzik wrote: > > > On 11/14/23, Alexander Motin wrote: > > > > On 14.11.2023 12:39, Mateusz Guzik wrote: > > >

Re: crash zfs_clone_range()

On Tue, Nov 14, 2023 at 10:46 AM Alexander Motin wrote: > > On 14.11.2023 12:44, Alexander Motin wrote: > > On 14.11.2023 12:39, Mateusz Guzik wrote: > >> One of the vnodes is probably not zfs, I suspect this will do it > >> (untested): > >> > >> diff --git

Re: crash zfs_clone_range()

On Tue, Nov 14, 2023 at 1:15 PM Mateusz Guzik wrote: > > On 11/14/23, Rick Macklem wrote: > > On Tue, Nov 14, 2023 at 10:46 AM Alexander Motin wrote: > >> > >> On 14.11.2023 12:44, Alexander Motin wrote: > >> > On 14.11.2023 12:39, Mateusz Guzik wrote: > >> >> One of the vnodes is probably not

Re: [HEADS-UP] Quick update to 14.0-RELEASE schedule

On Tue, Nov 14, 2023 at 08:10:23PM -0700, The Doctor wrote: > On Wed, Nov 15, 2023 at 02:27:01AM +, Glen Barber wrote: > > On Tue, Nov 14, 2023 at 05:15:48PM -0700, The Doctor wrote: > > > On Tue, Nov 14, 2023 at 08:36:54PM +, Glen Barber wrote: > > > > We are still waiting for a few

Re: [HEADS-UP] Quick update to 14.0-RELEASE schedule

On Wed, Nov 15, 2023 at 02:27:01AM +, Glen Barber wrote: > On Tue, Nov 14, 2023 at 05:15:48PM -0700, The Doctor wrote: > > On Tue, Nov 14, 2023 at 08:36:54PM +, Glen Barber wrote: > > > We are still waiting for a few (non-critical) things to complete before > > > the announcement of

Re: uname -KU 1500001 1500000

On Mon, 2 Oct 2023 at 08:33, Mark Millard wrote: > Or file and ls results for the amd64.amd64/usr.bin/uname/uname.o ? > (Just checking for if there are surprises.) Please, where would I find that file? I'm lost

Re: uname -KU 1500001 1500000

> On 15 Nov 2023, at 08:09, Graham Perrin wrote: > > On Mon, 2 Oct 2023 at 08:33, Mark Millard wrote: > >> Or file and ls results for the amd64.amd64/usr.bin/uname/uname.o ? >> (Just checking for if there are surprises.) > > Please, where would I find that file? I'm lost Under

FreeBSD user environment repeatedly inferior to kernel (was: uname -KU 1500001 1500000)

On Sun, 1 Oct 2023 at 20:28, Graham Perrin wrote: > User environment (150) inferior to kernel (151). > > … I discovered a comparable mismatch from build and installation on 9th November. Any ideas? I use devel/ccache4 4.8, if that's relevant. Copied from : % uname -KU 153 151

Re: uname -KU 1500001 1500000

On Wed, 15 Nov 2023 07:09:39 + Graham Perrin wrote: > On Mon, 2 Oct 2023 at 08:33, Mark Millard wrote: > > > Or file and ls results for the amd64.amd64/usr.bin/uname/uname.o ? > > (Just checking for if there are surprises.) > > Please, where would I find that file? I'm lost > Assuming that

Re: [HEADS-UP] Quick update to 14.0-RELEASE schedule

On Wed, 15 Nov 2023 04:52:31 + Glen Barber wrote: > > > Ok. I do not know what exactly is your point, but releases are > > > never official until there is a PGP-signed email sent. The email > > > is intended for the general public of consumers of official > > > releases, not "yeah, but"s.