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
Describe the bug
kernel SMB client does not automatically update IP address of the cifs mount after DNS update.
This is a known issue in some early versions of Linux kernel and should have been fixed. However i can still reproduce this issue on latest AzureLinux running 5.15+ kernel.
sudo mount -t cifs //f19b3e40c80e54919ae4890.file.core.windows.net/pvc-9717cacf-4c54-4341-b336-f5398bd41b38 /mnt/pvc-9717cacf-4c54-4341-b336-f5398bd41b38 -o credentials=/etc/smbcredentials/f19b3e40c80e54919ae4890.cred,dir_mode=0777,file_mode=0777,serverino,nosharesock,actimeo=30
After the Azure fileshare is mounted, take note of the IP address used by the mount. IP address used by the mount should match the IP address of the fileshare endpoint
On Azure storage account, initiate geographic failover which updates the fileshare DNS and point it to the IP address of the secondary site.
See error
Fileshare mount still uses the old IP address of the fileshare
trying to access the fileshare now get "Host is down" error
root [ /home/azureuser ]# ls /mnt/pvc-9717cacf-4c54-4341-b336-f5398bd41b38
ls: cannot access '/mnt/pvc-9717cacf-4c54-4341-b336-f5398bd41b38': Host is down
kernel error logged in syslog
2024-05-14T13:56:27.490067+00:00 aks-azurelinux-13697370-vmss000006 kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
2024-05-14T13:56:27.490233+00:00 aks-azurelinux-13697370-vmss000006 kernel: CIFS: VFS: \\f19b3e40c80e54919ae4890.file.core.windows.net Send error in SessSetup = -13
Expected behavior
SMB client should detect the DNS change and automatically update mount point to use the new IP address.
The text was updated successfully, but these errors were encountered:
The article linked at the top is nonsense.
It references kernel fixes from three years ago.
Then, says we need AzureLinux 2.0 with kernel version 5.15.159 to pick them up. 🤨
The article linked at the top is nonsense. It references kernel fixes from three years ago. Then, says we need AzureLinux 2.0 with kernel version 5.15.159 to pick them up. 🤨
Could this regression explain the behavior seen here? If so, it's fixed in 5.15.158.
this is fixed in 5.15.160.1-1.cm2 which was released a week ago or so. thanks for the link to the regression bug . later i realized that's the case too.
Describe the bug
kernel SMB client does not automatically update IP address of the cifs mount after DNS update.
This is a known issue in some early versions of Linux kernel and should have been fixed. However i can still reproduce this issue on latest AzureLinux running 5.15+ kernel.
To Reproduce
Steps to reproduce the behavior:
After the Azure fileshare is mounted, take note of the IP address used by the mount. IP address used by the mount should match the IP address of the fileshare endpoint

On Azure storage account, initiate geographic failover which updates the fileshare DNS and point it to the IP address of the secondary site.

See error

Fileshare mount still uses the old IP address of the fileshare
trying to access the fileshare now get "Host is down" error
kernel error logged in syslog
Expected behavior
SMB client should detect the DNS change and automatically update mount point to use the new IP address.
The text was updated successfully, but these errors were encountered: