- 7.3.0-beta.1
- Retest
- Minor
I followed the instructions to do a parity swap:
Nowhere in these instructions does it mention that I should disable the spin down delay, but when I woke up this morning I found this in the logs:
Dec 15 00:38:05 Media emhttpd: spinning down /dev/sdd
Dec 15 00:38:05 Media emhttpd: spinning down /dev/sde
Dec 15 00:38:44 Media emhttpd: spinning down /dev/sdc
Dec 15 00:38:47 Media emhttpd: read SMART /dev/sdc
Dec 15 00:38:48 Media emhttpd: spinning down /dev/sdb
Dec 15 00:38:50 Media emhttpd: read SMART /dev/sdb
Dec 15 00:39:10 Media emhttpd: read SMART /dev/sdd
Dec 15 01:21:14 Media monitor_nchan: Stop running nchan processes
Dec 15 02:38:47 Media emhttpd: spinning down /dev/sdc
Dec 15 02:38:50 Media emhttpd: read SMART /dev/sdc
Dec 15 02:38:52 Media emhttpd: spinning down /dev/sdb
Dec 15 02:38:53 Media emhttpd: read SMART /dev/sdb
Dec 15 02:39:02 Media emhttpd: spinning down /dev/sdd
Dec 15 02:39:12 Media emhttpd: spinning down /dev/sde
Dec 15 02:40:10 Media emhttpd: read SMART /dev/sdd
Dec 15 02:40:18 Media emhttpd: read SMART /dev/sdeThe parity swap started 2 hours earlier (10:38pm on Dec 14). This repeated every 2 hours, which is my spin down delay, until I woke up and set spin down to Never.
I'm copying parity data from sdb to sdc but every drive is doing this, not just the two that are active, even though the array has not started. The swap is ongoing during the diagnostics (sdb is now inactive and it's writing zeros into the extra space).
I suggest either advise users to disable spin down during this process, or add some logic to avoid spinning down drives particularly the ones actively involved in a parity swap.