> On Jan 30, 2023, at 5:11 PM, Andrew J. Romero <romero@xxxxxxxx> wrote: > > Hi > > This is a quick general NFS server question. > > Does the NFSv4x specification require or recommend that: the NFS server, after some reasonable time, > should / must close orphan / zombie open files ? No it does not. A server is supposed to leave open state alone if the client continues to renew its lease. A server has some recourse, though. It can recall delegations to free up resources. We have some patches for v6.2 that do that. Servers can also free state where subsequent accesses by a client indicate that the server administrator has revoked that state. I don't believe the spec makes any statement about when to use this facility or how to choose state to purge, and I'm pretty sure Linux NFSD does not implement it. A heavyweight tool would be to simulate a server reboot to force clients to acknowledge which state they are still using, via state recovery. > On several NAS platforms I have seen large numbers of orphan / zombie open files "pile up" > as a result of Kerberos credential expiration. > > Does the Red Hat NFS server "deal with" orphan / zombie open files ? Not currently, nor does the upstream server. Purging state is not terribly good for data integrity guarantees, and I'm not sure how the server would make fair choices about what OPEN stateids to purge. So before going down that path I would like to see if the file leakage might be the result of aberrant client behavior, and try to address the issue from that side first. Do you have a simple reproducer for this issue? How do you observe the orphaned files? -- Chuck Lever
