From nobody Fri May 3 21:55:35 2024 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VWPkN2LsHz5JcDH for ; Fri, 3 May 2024 21:55:40 +0000 (UTC) (envelope-from SRS0=a8w7=MG=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4VWPkM4w3cz4YZk for ; Fri, 3 May 2024 21:55:39 +0000 (UTC) (envelope-from SRS0=a8w7=MG=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Fri, 3 May 2024 23:55:35 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1714773336; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=QmMne/HEgV5l2e76dpBY8jD6dkWyTm7OLSQKynDb0V8=; b=TtPVDgJYhfSTgSNJrVyaQ1Mq25JQ1g8IoWQjJqt3wCaX95TwOMbLeEhlwaWXR7KIPxeuIt eXLqTlM4D/maumWL+ap/8tmHDjga99E44Piz616mk4vaWDL71rysj27aHXkxJ/hJEhaZ5B lxx7jd3uKuW5R0UKHs+KPxG4FhbFGYz3URd2qla+A3Etu5l4w/2Ab+JQo2RXvtNM3J47yY yOGp3d4GROdGBGA6RnM1meC0c0DeYNcuuPsJdF8AP0MLFX/QxkKGhtEwUQ9/7eUpvMh9bU Xt0Yg83qXxLx2wbbHBbKQF9hwrh5QhTdtt+dwQXs4sU0XA0WRXsLT19LUljZcQ== From: Ronald Klop To: Garrett Wollman Cc: freebsd-stable@freebsd.org Message-ID: <727612068.8243.1714773335920@localhost> In-Reply-To: <26165.22926.598276.904906@hergotha.csail.mit.edu> Subject: Re: ZFS property inheritance broken for `readonly`? List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_8242_1432664771.1714773335864" X-Mailer: Realworks (701.18) Importance: Normal X-Priority: 3 (Normal) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL] X-Rspamd-Queue-Id: 4VWPkM4w3cz4YZk ------=_Part_8242_1432664771.1714773335864 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Van: Garrett Wollman Datum: 3 mei 2024 23:39 Aan: freebsd-stable@freebsd.org Onderwerp: ZFS property inheritance broken for `readonly`? >=20 >=20 > I've noticed recently (not sure when this started, maybe on the 12->13 > transition, which would be the same as the old ZFS to OpenZFS > transition for us) that inheritance for the `readonly` property is > broken. >=20 > Here is an example: >=20 > [root@nfs-prod-11 /home/wollman]# zfs set readonly=3Don export/cl > [root@nfs-prod-11 /home/wollman]# zfs get readonly export/cl/u > NAME PROPERTY VALUE SOURCE > export/cl/u readonly off temporary >=20 > The child filesystem `export/cl/u` should have inherited the readonly > setting from `export/cl` but instead it (and all other children) have > overridden it, and I have to manually `zfs inherit readonly` on all of > the children to get the proper behavior. This is quite surprising, > and the first time it happened I was sure that something had gone > wrong. >=20 > -GAWollman >=20 >=20 >=20 >=20 >=20 >=20 How did you mount the fs? Could it be that the =E2=80=9Ctemporary=E2=80=9D source of the setting had = to do with it? See man zfs.=20 Regards,Ronald ------=_Part_8242_1432664771.1714773335864 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Van: Garrett Wollma= n <wollman@bimajority.org>
Datum: 3 mei 2024 23:3= 9
Aan: freebsd-stable@freebsd.org
Onderwerp:= ZFS property inheritance broken for `readonly`?

<= !-- P -->
I've noticed recently (not sure when this started, maybe on the 12-&g= t;13
transition, which would be the same as the old ZFS to OpenZFS
transition for us) that inheritance for the `readonly` property is
broken.

Here is an example:

[root@nfs-prod-11 /home/wollman]# zfs set readonly=3Don export/cl
[root@nfs-prod-11 /home/wollman]# zfs get readonly export/cl/u
NAME         PROPERTY  VALUE &= nbsp; SOURCE
export/cl/u  readonly  off     temporary

The child filesystem `export/cl/u` should have inherited the readonly
setting from `export/cl` but instead it (and all other children) have
overridden it, and I have to manually `zfs inherit readonly` on all of
the children to get the proper behavior.  This is quite surprising, and the first time it happened I was sure that something had gone
wrong.

-GAWollman




How did you mount the fs?

Co= uld it be that the =E2=80=9Ctemporary=E2=80=9D source of the setting had to= do with it?
See man zfs. 

Regards,
Ronald

------=_Part_8242_1432664771.1714773335864--