Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure ceph-lock is always released when staging encrypted cephfs volume #4715

Closed
NymanRobin opened this issue Jul 16, 2024 · 4 comments · Fixed by #4725
Closed

Ensure ceph-lock is always released when staging encrypted cephfs volume #4715

NymanRobin opened this issue Jul 16, 2024 · 4 comments · Fixed by #4725
Assignees

Comments

@NymanRobin
Copy link
Contributor

Issue:

The current implementation of unlocking an encrypted filesystem in the NodeServer leaves a "hanging lock" (timeout duration will eventually clean this) if fscrypt fails to unlock. This causes unnecessary delays and negatively impact performance as this could be easily be avoided by pushing the unlocking of the lock directly to the defer stack after the lock has been acquired.

Solution:

For more information on the issue and potential solution please see this comment chain in the original PR: #4697 (review)

@NymanRobin
Copy link
Contributor Author

I have not tested yet the new implementation but I have a tingling feeling from earlier testing that this might be occurring here and there. If it is the cases the root-cause could of course be narrowed down in addition to this change.

Copy link

Thanks for taking this issue! Let us know if you have any questions!

@Sunnatillo
Copy link
Contributor

/assign

Copy link

Thanks for taking this issue! Let us know if you have any questions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants