Tore Hammervoll

Not sure what sort of details you're looking for, but I have 5 xfs formatted array disks and a single parity. Looking at the source code, I think this is the offending line: https://github.com/jcofer555/automover/blob/99b4d474624474e28378b818d83c2fb2d2758a0b/src/usr/local/emhttp/plugins/automover/helpers/automover.sh#L984 It doesn't have the same alternate logic for zfs as the other usages of `df`, and it fits with the log message where I see it reports 1% usage.

It looks to me like the stop threshold check still reports 1% for zfs pools. It starts moving due usage of 96%, but then immediately stops due a usage of 1%: Session finished - 2026-01-17 01:34:45 Duration: 4m 44s No files moved — skipping jdupes step Finished move process Skipped 5 in-use file(s) Finished move of 0 file(s) for share: data Move stopped — pool usage reached stop threshold: 1% (<= 50%) Starting move of 1149 file(s) for share: data Enabled reconstructive write mode (turbo write) Skipping appdata (array → pool moves not allowed) Starting move process cache_nvme usage:96% Threshold:80% Stop Threshold:50% Session started - 2026-01-17 01:30:01