Analyzing Gpfs Logs; Synchronizing Time On The File Modules - IBM Storwize V7000 Unified Problem Determination Manual

Analyzing GPFS logs

Use this procedure when reviewing GPFS log entries.
About this task
Note: Contact IBM support if you want to analyze GPFS log entries.
Procedure
1. Log in to the appropriate file module using root privileges.
2. Review the log file /var/adm/ras/mmfs.log.latest. The details in the log are

Synchronizing time on the file modules

Use this information to synchronize the time on all Storwize V7000 Unified file
module.
About this task
Synchronizing the time on all the file module can help as you start troubleshooting
because the timestamps on the logs then indicate whether you have concurrent,
legitimate results.
You can ensure that the Storwize V7000 Unified, Active Directory (AD), Kerberos,
and other servers are synchronized with a valid Network Time Protocol (NTP)
source. This is important both for log checking and because if the cluster falls
behind the correct time, Kerberos tickets, for example, can expire and then no one
can access the cluster. For the Storwize V7000 Unified file module, the ntpq –p
command shows you which server is used for synchronization and any peers and
a set of data about their status. The * in the first column indicates that the local
clock is used for synchronization.
# ntpq -p
==============================================================================
*machine.domain.i 9.19.0.220 2 u 269 1024 377
+machine.domain.i 9.19.0.220 2 u 992 1024 377
Note: If free space exists in the mdiskgroup then you can modify the file
system by editing it in the GUI or simply running the command: mkdisk
fileSystem size mdiskgroup
For example:
[root@kd01gln.mgmt002st001 ~]# mkdisk gpfs0 10GB 0
(1/4) Creating Storage System volumes
(2/4) Scanning for new devices
(3/4) Creating NSDs
(4/4) Adding disks to filesystem
Successfully created disk
b. If there is no storage space available, contact IBM support.
listed from oldest to newest, so you can find the latest GPFS information at the
end.
Note: The GPFS log is a complex raw log file for GPFS. If you do not
understand the conditions listed in the log, contact IBM support for assistance
remote refid
LOCAL(0) .LOCL.
st t when poll reach delay
0.659
1.380
10 l 50 64 377
offset jitter
-0.115 0.164
0.337 0.564
0.000 0.000 0.001
Chapter 4. File module
181