summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorpjd <pjd@FreeBSD.org>2007-04-08 15:56:49 +0000
committerpjd <pjd@FreeBSD.org>2007-04-08 15:56:49 +0000
commitd5cb13779a69d4d5c087805b81b4a26dc8640657 (patch)
tree2a728d43f4aa1c0d3ebbca4a6c604ce936a0edb5
parent12036d2691118bddc5930ad0c068eedd6d73488e (diff)
downloadFreeBSD-src-d5cb13779a69d4d5c087805b81b4a26dc8640657.zip
FreeBSD-src-d5cb13779a69d4d5c087805b81b4a26dc8640657.tar.gz
Provide sample entries to handle ZFS problem reports.
It'd be nice to send them via e-mail...
-rw-r--r--etc/devd.conf31
1 files changed, 31 insertions, 0 deletions
diff --git a/etc/devd.conf b/etc/devd.conf
index 38be193..07c79c6 100644
--- a/etc/devd.conf
+++ b/etc/devd.conf
@@ -208,6 +208,37 @@ notify 10 {
action "logger -p kern.emerg 'WARNING: system temperature too high, shutting down soon!'";
};
+# Sample ZFS problem reports handling.
+notify 10 {
+ match "system" "ZFS";
+ match "type" "zpool";
+ action "logger -p kern.err 'ZFS: failed to load zpool $pool'";
+};
+
+notify 10 {
+ match "system" "ZFS";
+ match "type" "vdev";
+ action "logger -p kern.err 'ZFS: vdev failure, zpool=$pool'";
+};
+
+notify 10 {
+ match "system" "ZFS";
+ match "type" "data";
+ action "logger -p kern.warn 'ZFS: zpool I/O failure, zpool=$pool error=$zio_err'";
+};
+
+notify 10 {
+ match "system" "ZFS";
+ match "type" "io";
+ action "logger -p kern.warn 'ZFS: vdev I/O failure, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size error=$zio_err'";
+};
+
+notify 10 {
+ match "system" "ZFS";
+ match "type" "checksum";
+ action "logger -p kern.warn 'ZFS: checksum mismatch, zpool=$pool path=$vdev_path offset=$zio_offset size=$zio_size'";
+};
+
/* EXAMPLES TO END OF FILE
# The following might be an example of something that a vendor might
OpenPOWER on IntegriCloud