You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Type of issue
Missing information
Feedback
The PV example in the Statically provision a volume section displays the following mount options:
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, seeI also found this interesting blog by @chenghui-lee at https://lchenghui.com/nobrl-for-mount-cifs, screenshot with the fragment pasted below
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 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.
The text was updated successfully, but these errors were encountered: