Resolving stale NFS file systems
You can resolve problems with stale NFS file systems on Storwize V7000 Unified
file modules. A file module might have the file system mounted, but the file
system remains inaccessible due to a stale NFS file handle.
To identify and resolve stale file handle problems, perform this procedure:
1. To identify stale NFS file handle problems, log in as the root user to the active
management node, then enter the onnode all df | grep NFS command:
# onnode all df | grep NFS
df: `/ibm/gpfs0’: Stale NFS file handle
2. If the command reports a stale NFS file handle on a particular file system, see
“Working with file modules that report a stale NFS file handle” on page 258 for
instructions on file system recovery.
Checking user and server authentication issues
Issues with logging on as a user or a lack of connection between servers might be
tied to authentication problems.
With regard to user authentication issues, if you are sure that you have used the
correct logon ID and password, your user account might have been deleted or
corrupted.
Refer to these topics in the IBM Storwize V7000 Unified Information Center “Planning
for user authentication”, “Verifying the authentication configuration”, “Establishing
user and group mapping for client access”, and “chkauth”.
If you cannot resolve the issue, contact your authentication server administrator to
validate or reestablish your account.
With regard to server configuration issues, refer to “Managing authentication
server integration” and the authentication topics available there.
Error for “Missing SRV record in DNS”
If you encounter a “Missing SRV record in DNS” error similar to the following
when configuring the active directory (AD) with the cfgad command, verify that
entries for DNS Domain Name, DNS Server, and DNS Search Domains are correct.
Also, verify that the DNS server has valid SRV records for that domain.
$ cfgad -s 9.9.9.9 -u admin -p ****
(1/9) Fetching the list of cluster file modules.
(2/9) Check if cfgcluster has done the basic configuration successfully.
(3/9) Check whether file modules are
reachable from management file module.
(4/9) Detection of AD server and fetching domain information from AD server.
Missing SRV record in DNS : _ldap._tcp.xxxxx.COM
Missing SRV record in DNS : _ldap._tcp.dc._msdcs.xxxxx.COM
Missing SRV record in DNS : _kerberos._tcp.xxxxx.COM
Missing SRV record in DNS : _kerberos._tcp.dc._msdcs.xxxxx.COM
Necessary DNS entries are missing, the domain join step might fail.
(5/9) Check whether AD server is reachable
from file modules.
(6/9) Joining the domain of the specified ADS.
EFSSG0110C Configure AD failed on cluster. Cause: Error encountered while
executing netjoinAD.sh. Output till failure is :Join to Active Directory
164 Storwize V7000 Unified: Problem Determination Guide Version
To Next Page
Loading...
Need help?
General