Date: Fri, 3 May 2024 23:55:35 +0200 (CEST) From: Ronald Klop <ronald-lists@klop.ws> To: Garrett Wollman <wollman@bimajority.org> Cc: freebsd-stable@freebsd.org Subject: Re: ZFS property inheritance broken for `readonly`? Message-ID: <727612068.8243.1714773335920@localhost> In-Reply-To: <26165.22926.598276.904906@hergotha.csail.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_8242_1432664771.1714773335864 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Van: Garrett Wollman <wollman@bimajority.org> 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 <html><head></head><body><br><p><small><strong>Van:</strong> Garrett Wollma= n <wollman@bimajority.org><br><strong>Datum:</strong> 3 mei 2024 23:3= 9<br><strong>Aan:</strong> freebsd-stable@freebsd.org<br><strong>Onderwerp:= </strong> ZFS property inheritance broken for `readonly`?<br></small></p><b= lockquote style=3D"margin-left: 5px; border-left: 3px solid #ccc; margin-ri= ght: 0px; padding-left: 5px;"><div class=3D"MessageRFC822Viewer" id=3D"P"><= !-- P --> <!-- processMimeMessage --><div class=3D"TextPlainViewer" id=3D"P.P"><!-- P= .P -->I've noticed recently (not sure when this started, maybe on the 12-&g= t;13<br> transition, which would be the same as the old ZFS to OpenZFS<br> transition for us) that inheritance for the `readonly` property is<br> broken.<br> <br> Here is an example:<br> <br> [root@nfs-prod-11 /home/wollman]# zfs set readonly=3Don export/cl<br> [root@nfs-prod-11 /home/wollman]# zfs get readonly export/cl/u<br> NAME PROPERTY VALUE &= nbsp; SOURCE<br> export/cl/u readonly off temporary<br> <br> The child filesystem `export/cl/u` should have inherited the readonly<br> setting from `export/cl` but instead it (and all other children) have<br> overridden it, and I have to manually `zfs inherit readonly` on all of<br> the children to get the proper behavior. This is quite surprising,<br= > and the first time it happened I was sure that something had gone<br> wrong.<br> <br> -GAWollman<br> <br> <br> </div><!-- TextPlainViewer --> <hr> </div><!-- MessageRFC822Viewer --> </blockquote><br><br>How did you mount the fs?<br class=3D"rw_extra"><br>Co= uld it be that the =E2=80=9Ctemporary=E2=80=9D source of the setting had to= do with it?<div>See man zfs. <br class=3D"rw_extra"><br>Regards,<br c= lass=3D"rw_extra">Ronald<br><br></div></body></html> ------=_Part_8242_1432664771.1714773335864--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?727612068.8243.1714773335920>