SMB issues

This topic describes SMB-related issues that you might come across while using the IBM Storage Scale system.

Determining the health of integrated SMB server
There are some IBM Storage Scale commands to determine the health of the SMB server.
File access failure from an SMB client with sharing conflict
The SMB protocol includes sharemodes, which are locks that can be held on the whole file while a SMB client has the file open. The IBM Storage Scale file system also enforces these sharemode locks for other access.
SMB client on Linux fails with an "NT status logon failure"
This topic describes how to verify and resolve an NT status logon failure on the SMB client on Linux®.
SMB client on Linux fails with the NT status password must change error message
This topic describes how to verify and resolve an NT status password must change error on the SMB client on Linux.
SMB mount issues
This topic describes how to verify and resolve SMB mount errors.
Net use on Windows fails with "System error 86"
This topic describes how to verify and solve a System error 86 when the user is attempting to access net use on Windows.
Net use on Windows fails with "System error 59" for some users
This topic describes how to resolve a System error 59 when some users attempt to access /usr/lpp/mmfs/bin/net use on Windows.
Winbindd causes high CPU utilization
This topic describes the issues that can happen due to the winbindd component.
SMB error events
This topic describes how to verify and resolve SMB errors.
SMB access issues
This topic describes how to analyze and resolve SMB access issues.
Slow access to SMB caused by contended access to files or directories
This topic describes the reason behind the slow access to SMB server and the troubleshooting steps to handle it.
CTDB issues
CTDB is a database layer for managing SMB and Active Directory specific information and provides it consistently across all CES nodes.
smbd start issue
In a configuration where the current LDAP server is decommissioned, but the mmuserauth was not changed to remove the service, smbd does not start because it cannot contact the decommissioned LDAP server. smbd only starts when it can reach the LDAP server. Authentication also cannot be removed because it requires a healthy samba.

Parent topic: Protocol issues