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

AKS Learn feedback: Explain why to specify nobrl in mountOptions of statically provisioned PersistentVolume #123601

Open
mloskot opened this issue Jul 2, 2024 · 1 comment

Comments

@mloskot
Copy link
Contributor

mloskot commented Jul 2, 2024

Type of issue

Missing information

Feedback

The PV example in the Statically provision a volume section displays the following mount options:

  mountOptions:
    - dir_mode=0777
    - file_mode=0777
    - uid=0
    - gid=0
    - mfsymlinks
    - cache=strict
    - nosharesock
    - nobrl

but there is no explanation on why the nobrl is needed or recomended?

The current official example in the azurefile-csi-driver repository does not present use of the nobrl option, see

I also found this interesting blog by @chenghui-lee at https://lchenghui.com/nobrl-for-mount-cifs, screenshot with the fragment pasted below

image

Next, I found the nobrl documented in https://learn.microsoft.com/en-us/troubleshoot/azure/azure-kubernetes/storage/mountoptions-settings-azure-files#other-useful-settings which says:

It's necessary for certain applications that break with cifs-style mandatory byte range locks.

It would be useful if the current article on the statically provisioned PV-s expands on that, e.g. what types of applications are meant, is this locking effective on Windows containers too, etc.

Page URL

https://learn.microsoft.com/en-us/azure/aks/azure-csi-files-storage-provision#statically-provision-a-volume

Content source URL

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/aks/azure-csi-files-storage-provision.md

Author

@tamram

Document Id

b95ca0b2-e809-a149-dec7-a15ac2146ee1


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

@TPavanBalaji
Copy link
Contributor

@mloskot
Thanks for your feedback! We will investigate and update as appropriate.

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

No branches or pull requests

3 participants