Splunk Linux Use Case

Storage Pool Integrity Watch

Silent pool rot (ZFS / md / btrfs)

The scenario

md RAID rebuilds itself at 1 % and nobody notices for a week. A btrfs checksum error lands in dmesg where nobody reads dmesg. The "mirrored" pool has had one leg missing since the day it was commissioned. ZFS is honest about corruption, md is shy, btrfs is optimistic - none of them have a dashboard. Data loss doesn't announce itself; it accumulates.

The app recipe

TA-zfspool Unified pool state across ZFS, md, btrfs: degraded/failed devices, uncorrectable/corrupted read counters, resync/scrub %, spares
TA-sanpath The paths into the pool: multipath topology, failed paths, iSCSI sessions
TA-disk The members underneath it: SMART per physical disk
TA-hwraid Pools you don't own: hardware RAID controllers behind which the above are blind

Problems this kills

Killer searches

Who this is for

Everyone with mirrors or parity between them and their data, especially the ones who have never looked at `/proc/mdstat` voluntarily.

Next

All Use Cases Browse All Apps