- Permissions checks when using the DFS API are only done on the pool and container ACLs during dfs_mount().
- The DAOS/DFS client does not cache any data on the client side. So if you lookup a full path every time you are going to do the path traversal for each lookup. In DAOS master, we have
added a new API (dfs_sys) where a DFS mountpoint can be done with a caching option to cache the looked up path of parent directories to avoid such overhead:
email@example.com <firstname.lastname@example.org> on behalf of
Date: Saturday, July 3, 2021 at 3:44 AM
To: email@example.com <firstname.lastname@example.org>
Subject: [daos] Questions about DFS
Hi~, I have two questions about DFS metadata:
1. When the client opens a file or directory, will it check the permissions for each directory on the path, or will it only check at dfs_mount()?
2. Will the client cache the metadata of the directory to speed up path traversal? Or the metadata of this directory will be saved on the client after the directory is opened until it is closed?