Howdy Neil- > On Oct 31, 2023, at 5:57 PM, NeilBrown <neilb@xxxxxxx> wrote: > > Revoking state through 'unlock_filesystem' now revokes any delegation > states found. When the stateids are then freed by the client, the > revoked stateids will be cleaned up correctly. Here's my derpy question of the day. "When the stateids are then freed by the client" seems to be a repeating trope, and it concerns me a bit (probably because I haven't yet learned how this mechanism /currently/ works)... In the case when the client has actually vanished (eg, was destroyed by an orchestrator), it's not going to be around to actively free revoked state. Doesn't that situation result in pinned state on the server? I would expect that's a primary use case for "unlock_filesystem." Maybe I've misunderstood something fundamental. -- Chuck Lever
