-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Troubleshooting
This page contains tips for troubleshooting ZFS on Linux and what info developers might want for bug triage.
Log files can be very useful for troubleshooting. In some cases, interesting information is stored in multiple log files that are correlated to system events.
Pro tip: logging infrastructure tools like elasticsearch, fluentd, influxdb, or splunk can simplify log analysis and event correlation.
Typically, Linux kernel log messages are available from dmesg -T
, /var/log/syslog
, or where kernel log messages are sent (eg by rsyslogd
).
The ZFS kernel modules use an internal log buffer for detailed logging information.
This log information is available in the pseudo file /proc/spl/kstat/zfs/dbgmsg
for ZFS builds where ZFS module parameter zfs_dbgmsg_enable = 1
Symptom: zfs
or zpool
command appear hung, does not return, and is not killable
Likely cause: kernel thread hung or panic
Log files of interest: Generic Kernel Log, ZFS Kernel Module Debug Messages
Important information: if a kernel thread is stuck, then a backtrace of the stuck thread can be in the logs.