Devel March 2021

devel@lists.nfs-ganesha.org

8 participants
32 discussions

Change in ...nfs-ganesha[next]: GLUSTER: Add debug to open2

by Frank Filz (GerritHub)

Frank Filz has uploaded this change for review. ( https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/511645 ) Change subject: GLUSTER: Add debug to open2 ...................................................................... GLUSTER: Add debug to open2 Change-Id: I06c12e20b011c332b7d9a25981969c31513db1fc Signed-off-by: Frank S. Filz <ffilzlnx(a)mindspring.com> --- M src/FSAL/FSAL_GLUSTER/handle.c 1 file changed, 51 insertions(+), 5 deletions(-) git pull ssh://review.gerrithub.io:29418/ffilz/nfs-ganesha refs/changes/45/511645/1 -- To view, visit https://review.gerrithub.io/c/ffilz/nfs-ganesha/+/511645 To unsubscribe, or for help writing mail filters, visit https://review.gerrithub.io/settings Gerrit-Project: ffilz/nfs-ganesha Gerrit-Branch: next Gerrit-Change-Id: I06c12e20b011c332b7d9a25981969c31513db1fc Gerrit-Change-Number: 511645 Gerrit-PatchSet: 1 Gerrit-Owner: Frank Filz <ffilzlnx(a)mindspring.com> Gerrit-MessageType: newchange

3 years, 1 month

1
0
0 / 0

unlink of one dirent could invalidate all.

by Pradeep

Hello, In mdcache_unlink, ganesha removes the dirent from its parent by calling mdcache_dirent_remove(). It also clears MDCACHE_TRUST_ATTRS. So, if a subsequent GETATTR comes for the parent (which can happen in the same compound from nfs4_op_remove), it frees all entries at the end of mdcache_refresh_attrs(). In this scenario, isn't it possible to keep the rest of dirents intact? I'm thinking if we update parents attrs in unlink itself, would it prevent any further refreshes? The use case here is large directories with frequent additions/deletions/enumerations. Thanks, Pradeep

3 years, 1 month

2
4
0 / 0

← Newer
1
2
3
4
Older →

2024

2023

2022

2021

2020

2019

2018

Devel March 2021