Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Nov 2019 08:24:43 -0500
From:      Mike Tancsa <mike@sentex.net>
To:        Borja Marcos <borjam@sarenet.es>
Cc:        Alan Somers <asomers@freebsd.org>, Jan Behrens <jbe-mlist@magnetkern.de>,  freebsd-fs <freebsd-fs@freebsd.org>
Subject:   Re: ZFS snapdir readability (Crosspost)
Message-ID:  <913f7040-6e38-452d-6187-e17fae63b652@sentex.net>
In-Reply-To: <261FE331-EC5C-48C8-9249-9BCBF887CE38@sarenet.es>
References:  <20191107004635.c6d2e7d464d3d556a0d87465@magnetkern.de> <CAOtMX2huHZcXHH%2B=3Bx7hX_p9udJ2acOX%2BZL8vW=pjqbe6mOAA@mail.gmail.com> <e2eecef7-21b6-0ff2-b259-71421b7d097c@sentex.net> <9B22AD46-BE87-4305-9638-74D23AD4C8CA@sarenet.es> <cfcc12dd-e9eb-5a98-a031-ab18436a2dd3@sentex.net> <261FE331-EC5C-48C8-9249-9BCBF887CE38@sarenet.es>

next in thread | previous in thread | raw e-mail | index | archive | help
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@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?913f7040-6e38-452d-6187-e17fae63b652>