From 25ea50ccd8a02890e14c6d1f45b002a15ca7318f Mon Sep 17 00:00:00 2001 From: Richard Elling Date: Fri, 7 Jun 2019 10:24:29 -0700 Subject: [PATCH] added horizontal rules to try and reinforce the notion that each section is independent of others --- Troubleshooting.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Troubleshooting.md b/Troubleshooting.md index 103821c..3998c3e 100644 --- a/Troubleshooting.md +++ b/Troubleshooting.md @@ -1,5 +1,7 @@ # DRAFT This page contains tips for troubleshooting ZFS on Linux and what info developers might want for bug triage. + +*** ## About Log Files 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. @@ -12,6 +14,7 @@ Typically, Linux kernel log messages are available from `dmesg -T`, `/var/log/sy 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](https://github.com/zfsonlinux/zfs/wiki/ZFS-on-Linux-Module-Parameters#zfs_dbgmsg_enable) +*** ## Unkillable Process Symptom: `zfs` or `zpool` command appear hung, does not return, and is not killable @@ -22,6 +25,7 @@ Log files of interest: [Generic Kernel Log](#generic-kernel-log), [ZFS Kernel Mo Important information: if a kernel thread is stuck, then a backtrace of the stuck thread can be in the logs. In some cases, the stuck thread is not logged until the deadman timer expires. See also [debug tunables](https://github.com/zfsonlinux/zfs/wiki/ZFS-on-Linux-Module-Parameters#debug) +*** ## ZFS Events ZFS uses an event-based messaging interface for communication of important events to other consumers running on the system. The ZFS Event Daemon (zed) is a userland daemon that