Tracing is logging at a high level. The mmprotocoltrace command that
is used for starting and stopping tracing supports SMB, Winbind, Network, and Object
tracing.
NFS tracing can be done with a combination of commands.
- NFS
- NFS tracing is achieved by increasing the log level, repeating the issue, capturing the log
file, and then restoring the log level.
- To increase the log level, use the command
mmnfs config change
LOG_LEVEL=FULL_DEBUG. The mmnfs config change command
restarts the server on all nodes. You can increase the log level by using
ganesha_mgr. This command takes effect without restart, only on the node on which
the command is run.
- You can set the log level to the following values:
NULL,FATAL,
MAJ, CRIT, WARN, EVENT,
INFO, DEBUG, MID_DEBUG, and
FULL_DEBUG.
- FULL_DEBUG is the most useful for debugging purposes. This command collects large amount of
data, straining disk usage and affecting performance.
- After the issue is re-created by running the gpfs.snap command either with no
arguments or with the --protocol nfs argument, the NFS logs are captured. The
logs can then be used to diagnose any issues.
- To return the log level to normal, use the same command but with a lower logging level. The
default value is
EVENT.
- HDFS
- CES also supports HDFS protocols. For more information, see CES HDFS troubleshooting under IBM
Storage Scale support for Hadoop in Big data and
analytics support documentation.