- Annoyance
At first I wrote a bug report then deleted it as saw a few posts in which folks say the smart report happens after an IO report.
But right now my system is doing a parity check. Docker is turned off. There is NOTHING accessing the sata-cache yet it keeps 'spinning' up when I try to power it down.
I'd expect the Sata-cache to power down & also really the NVME cache's to power down during parity check as docker is turned off and nothing is accessing the drives...?
When the parity check is done the same will happen to my array. It won't stay asleep for longer than 1m. Two of the drives spins up do a little read then write a few Kb of data.
It's like it writing a small log file or something strange.
Is there something in the ZFS filesystem that has to write a little bit of data every few minutes?
Also noticed the manual set 15min spin down time on each drive is being changed to 'default' which should equal 15mins. Similar happens for any custom smart settings per drive or temperature warnings per drive. They all get over written by the 'default' even if you change them manually in each drive.
The array is 4 disks.
Parity
disk 1 - xfs
disk 2 - xfs
disk 4 - zfs single drive
Cache - zfs
cache mirror - zfs
sata-cache - zfs
sata-cache mirror - zfs
There's nothing in the file activity plugin under share or disk to account for this.
It happens if the cache plugin is installed or uninstalled.
Only happening since updating to 6.12.2
