On 9/12/22 05:29, Ryan Moeller wrote:
Here's the patch for the kernel and brief instructions:
https://reviews.freebsd.org/P547
That worked. I was not familiar with patching a file using git. My
experience has always used the 'patch' utility and a unified diff. I
just made a backup of the
On 8/29/22 11:28 AM, Ryan Moeller wrote:
On 8/29/22 10:14 AM, Thomas Laus wrote:
On 8/17/22 10:35, Thomas Laus wrote:
I attempted to create a ZFS snapshot after upgrading this morning
and received this error
After all of the discussion to compare and contrast beadm vs. bectl
my read only
On 8/29/22 10:14 AM, Thomas Laus wrote:
On 8/17/22 10:35, Thomas Laus wrote:
I attempted to create a ZFS snapshot after upgrading this morning and
received this error
After all of the discussion to compare and contrast beadm vs. bectl my
read only bit is still set as of this morning 29-AUG-
On 8/17/22 10:35, Thomas Laus wrote:
I attempted to create a ZFS snapshot after upgrading this morning and
received this error
After all of the discussion to compare and contrast beadm vs. bectl my
read only bit is still set as of this morning 29-AUG-2022.
# beadm create n257658
cannot creat
On Tue, Aug 23, 2022 at 2:44 PM Peter Jeremy wrote:
>
> On 2022-Aug-23 15:19:34 +0200, Ronald Klop wrote:
> >Van: Kyle Evans
> >> I was not aware that beadm touches loader.conf, but I find that
> >> slightly horrifying. I won't personally make bectl do that, but I
> >> guess I could at least doc
Now fixed as of
https://github.com/openzfs/zfs/commit/518b4876022eee58b14903da09b99c01b8caa754
-Ryan
Whoops, here's the correct link
https://cgit.freebsd.org/src/commit/?id=08aba0aec7b7f676ccc3f7886f59f277d668d5b4
On 08/28/2022 2:28 pm, Ryan Moeller wrote:
On 8/17/22 12:16 PM, Ryan Moeller wrote:
On 8/17/22 12:05 PM, Ryan Moeller wrote:
On 8/17/22 10:35 AM, Thomas Laus wrote:
I attempted to create a ZFS snapshot after upgrading this morning
and received this error
# beadm create n257443
cannot creat
On 8/17/22 12:16 PM, Ryan Moeller wrote:
On 8/17/22 12:05 PM, Ryan Moeller wrote:
On 8/17/22 10:35 AM, Thomas Laus wrote:
I attempted to create a ZFS snapshot after upgrading this morning
and received this error
# beadm create n257443
cannot create 'zroot/ROOT/n257443': 'snapshots_changed
On 2022-Aug-23 15:19:34 +0200, Ronald Klop wrote:
>Van: Kyle Evans
>> I was not aware that beadm touches loader.conf, but I find that
>> slightly horrifying. I won't personally make bectl do that, but I
>> guess I could at least document that it doesn't...
>
>Today I looked up something for boot
Van: Kyle Evans
Datum: maandag, 22 augustus 2022 17:11
Aan: Ronald Klop
CC: Peter Jeremy , freebsd-current@freebsd.org, Ryan Moeller
, "Patrick M. Hausen"
Onderwerp: Re: Beadm can't create snapshot
On Mon, Aug 22, 2022 at 5:10 AM Ronald Klop wrote:
>
>
>
>
On 2022-08-22 12:29, Peter Jeremy wrote:
On 2022-Aug-22 10:56:51 +0200, "Patrick M. Hausen" wrote:
Am 22.08.2022 um 10:45 schrieb Peter Jeremy :
On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" wrote:
Isn't beadm retired in favour of bectl?
2) "bectl activate" doesn't update /boot/loader.
On Mon, Aug 22, 2022 at 5:10 AM Ronald Klop wrote:
>
>
>
> Van: Peter Jeremy
> Datum: maandag, 22 augustus 2022 10:45
> Aan: "Patrick M. Hausen"
> CC: Ryan Moeller , freebsd-current@freebsd.org
> Onderwerp: Re: Beadm can't create snapshot
>
> On 2
Van: Peter Jeremy
Datum: maandag, 22 augustus 2022 10:45
Aan: "Patrick M. Hausen"
CC: Ryan Moeller , freebsd-current@freebsd.org
Onderwerp: Re: Beadm can't create snapshot
On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" wrote:
>Isn't beadm retired in fa
On 2022-Aug-22 10:56:51 +0200, "Patrick M. Hausen" wrote:
>> Am 22.08.2022 um 10:45 schrieb Peter Jeremy :
>> On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" wrote:
>>> Isn't beadm retired in favour of bectl?
>>
>> 2) "bectl activate" doesn't update /boot/loader.conf so the wrong
>> root fi
Hi,
> Am 22.08.2022 um 10:45 schrieb Peter Jeremy :
>
> On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" wrote:
>> Isn't beadm retired in favour of bectl?
>
> bectl still has a number of bugs:
> 1) The output from "bectl list" is in filesystem/bename order rather
> than creation date order.
On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" wrote:
>Isn't beadm retired in favour of bectl?
bectl still has a number of bugs:
1) The output from "bectl list" is in filesystem/bename order rather
than creation date order. This is an issue if you use (eg) git
commit hashes as the name
On 8/17/22 12:05 PM, Ryan Moeller wrote:
On 8/17/22 10:35 AM, Thomas Laus wrote:
I attempted to create a ZFS snapshot after upgrading this morning and
received this error
# beadm create n257443
cannot create 'zroot/ROOT/n257443': 'snapshots_changed' is readonly
#
This looks like a bug in
Hi all,
> Am 17.08.2022 um 18:05 schrieb Ryan Moeller :
>
>
> On 8/17/22 10:35 AM, Thomas Laus wrote:
>> I attempted to create a ZFS snapshot after upgrading this morning and
>> received this error
>>
>> # beadm create n257443
>> cannot create 'zroot/ROOT/n257443': 'snapshots_changed' is reado
On 8/17/22 10:35 AM, Thomas Laus wrote:
I attempted to create a ZFS snapshot after upgrading this morning and
received this error
# beadm create n257443
cannot create 'zroot/ROOT/n257443': 'snapshots_changed' is readonly
#
This looks like a bug in beadm. It must be trying to set the
snaps
I attempted to create a ZFS snapshot after upgrading this morning and
received this error
# beadm create n257443
cannot create 'zroot/ROOT/n257443': 'snapshots_changed' is readonly
#
My version info:
14.0-CURRENT FreeBSD 14.0-CURRENT #9 main-n257443-f7413197245: Wed Aug
17 08:15:27 EDT 2022
20 matches
Mail list logo
