Yes, we implement a vfs module which has cache. And we want to get attributes from cache when samba calls openat. On Thu, Jun 23, 2022 at 9:37 PM Ralph Boehme <slow at samba.org> wrote:> Hi, > > On 6/23/22 13:25, jie wang via samba wrote: > > I'm curious about how samba guarantee close-to-open consistency, > does > > it need to get all newest attributes from backend storage, when samba > call > > vfs_{vfs module}_openat, rather than use the cache in vfs module. > > oh, that's simple, there is no cache. :) At least not in upstream Samba. > The question kind of implies you're using a non upstream VFS module that > implements caching? > > -slow > > -- > Ralph Boehme, Samba Team https://samba.org/ > SerNet Samba Team Lead https://sernet.de/en/team-samba >
On 6/23/22 15:54, jie wang wrote:> Yes, we implement a vfs module which has cache. And we want to get > attributes from cache when samba calls openat.well, I guess the correct way to tackle this would be to let the *clients* do the caching with leases for file data and with directory leases for file metadata. But if you really want to cache on the server side, you could signal all other smbds with a message to drop the cache when you process the close in your VFS module. Another question would be which metadata your shooting for? stat info? DOS attributes? For the latter we have some design ideas to avoid the need to store an xattr with the DOS attributes for the default case. Cheers! -slow -- Ralph Boehme, Samba Team https://samba.org/ SerNet Samba Team Lead https://sernet.de/en/team-samba -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20220623/82d0f56f/OpenPGP_signature.sig>