Date: Wed, 17 Aug 2022 12:16:49 -0400 From: Ryan Moeller <freqlabs@FreeBSD.org> To: freebsd-current@freebsd.org Subject: Re: Beadm can't create snapshot Message-ID: <db19e194-d6fa-7019-d9f1-a1e0587d42a2@FreeBSD.org> In-Reply-To: <2818f3da-3ae2-e6e3-9282-8b62263fb5f3@FreeBSD.org> References: <01000182ac3b8593-fb381303-5719-4863-8fda-2530efcab31b-000000@email.amazonses.com> <2818f3da-3ae2-e6e3-9282-8b62263fb5f3@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 beadm. It must be trying to set the > snapshots_changed property when cloning the snapshot for the BE, but > the property is of course readonly. > > -Ryan > I took a closer look at what beadm is doing and this appears to be a bug in the property after all. beadm filters by source "local" or "received" and for "snapshots_changed" the source is "local" when it should be "-" like other readonly properties. We'll get this fixed ASAP. -Ryan > >> >> My version info: >> >> 14.0-CURRENT FreeBSD 14.0-CURRENT #9 main-n257443-f7413197245: Wed >> Aug 17 08:15:27 EDT 2022 >> >> There was not any information in UPDATING about any required ZFS >> configuration changes required nor any ZFS flags that listed >> 'snapshots_changed' as something that needed a new value. There is >> actually a new snapshot created, but 'beadm list' does not show it >> and the boot menu does not have it listed. >> >> Tom >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?db19e194-d6fa-7019-d9f1-a1e0587d42a2>