ZFS snapdir readability (Crosspost)

Mike Tancsa mike at sentex.net
Wed Nov 20 13:24:48 UTC 2019


On 11/20/2019 5:07 AM, Borja Marcos wrote:
> The problem is, snapshot access breaks the semantics of chown() and
> chmod().
>> As the snapshots are always readonly, I think chown and chmod dont
>> really apply in this use case. Also, the fact that the mounts can be set
>> to be "visibile" or "invisible" has its own, different convention from
>> UFS/NFS who dont have that "invisibility" feature (that I know of anyway).
> That’s what I mean with breaking the semantics.
>
> When you change permissions on a file they apply to open() operations attempted after the
> permissions/ownership change. 

> You could make snapshots not mounted, period, requiring administrator’s actions to mount them. But you
> would lose convenience for common users. 

Actually, thats all I am advocating for-- settings perms on the
accessibility of the snapshot. ie instead of the "invisibility" feature,
change it to an "inaccessible" feature.


    ---Mike


-- 
-------------------
Mike Tancsa, tel +1 519 651 3400 x203
Sentex Communications, mike at sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   



More information about the freebsd-fs mailing list