This topic describes the logging and tracing capabilities available on SAN File System Linux clients.
Configure the syslog facility and select one or more SAN File System classes to enable tracing and logging on the SAN File System Linux client.
The SAN File System client generates both log and trace messages, which are routed through the syslog facility on the Linux operating system. The syslog facility captures log and trace output from the kernel as well as other operating system services.
kern.debug /var/log/messages
/sbin/service syslog restartRefer to the Linux Commands Reference for more information about the syslogd daemon.
kern.debug /dev/console
/sbin/service syslog restartRefer to the Linux Commands Reference for more information about the syslogd daemon.
When you specify kern.debug as shown in the previous examples, all levels of kernel output are routed because debug is the lowest priority level of kernel output. You could specify a different level of output, such as kern.info to show just informational messages.
Tracing in the SAN File System is controlled according to components called classes. A class loosely corresponds to a file system operation such as mounting or reading.
$ cat /proc/fs/stfs/debug INIT OFF MOUNT OFF DISK OFF PAGER OFF IO OFF INODE OFF FILEHAND OFF RNGLOCK OFF RDWR OFF CLEANER OFF PROC OFF FILEOP OFF INODEOP OFF SUPEROP OFF CSM OFF
$ cat /proc/fs/stfs/csmdebug TM_LEASE OFF TM_XMIT_RECV OFF MC_OBJECT OFF CACHE_MANAGER OFF MC_SESSIONLOCK OFF CSM_SESSIONLOCK OFF MC_DATALOCK OFF CSM_DATALOCK OFF MC_RANGELOCK OFF CSM_RANGELOCK OFF BLKDISK OFF OBJATTR OFF NET_SOCKET OFF MISC OFF
$ cat /proc/fs/stfs/csmdebuglevel 5To change the verbosity level:
The following example messages show the format of log messages:
Apr 21 07:43:50 linuxclient1 unix: STFS: disk configuration process created with PID = 13348 Apr 21 07:43:50 linuxclient1 unix: STFS: cleaner process created with PID 12028 Apr 21 07:43:50 linuxclient1 unix: STFS: CSM process created with PID 10860
The following example messages show the format of trace messages:
Apr 28 13:17:09 linuxclient1 unix: STFS: 1051550182.439290 50337 STFS traceBuf_daemonize: going to sleep till shutdown Apr 28 13:17:09 linuxclient1 unix: STFS: 1051550182.448769 196267 STFS CSM OS-dependent services initialized. Apr 28 13:17:09 linuxclient1 unix: STFS: 1051550182.448827 196267 STFS Pager Strategy initialized. Apr 28 13:17:09 linuxclient1 unix: STFS: 1051550182.448875 196267 STFS GFS hooks initialized. Apr 28 13:17:09 linuxclient1 unix: STFS: 1051550182.448969 196267 STFS doInit(): system Initialized
Parent topic: Client diagnostic tools