I've got an odd little OMV setup, with four HDD's.
Primarily, I've got an SSD, on which OMV lives, as well as the main download folders and such.
Next to that, I've got three HDD's, with different use cases. One is used perhaps twice a day, one is used once every couple of days, one is updated once a week (Friday backups).
The SSD is set to stay active at all times, but I'm not sure if this has any effect (it's an SSD, after all). All others are set to spin down after fifteen minutes, with the acoustic setting set to 'quiet, low performance'.
I've no problems with performance; everything works as intended. However, the disks don't always spin down. Right now, all three are active, and I do not know why. Sometimes all three are inactive, sometimes one starts up in the middle of the night and won't go back to sleep.
Is there another way to check if there are processes blocking them from spinning down?
Ideally, I would also love a logfile stating WHY disks spin up, but I'll settle for something that tells me why they don't spin down.
UPDATE:
What I've found out and messed with so far)
- Flipped acoustic power management to 'disabled'. Not sure what this does, exactly, but the sound seems the same, and power usage is either the same, or not different enough to be measured accurately.
- I've set commit to 60 in fstab. The audible click every five seconds is down to every minute or so, but the disks still don't spin down.
- I've addeed noatime to fstab. No effect.
- changed /etc/init.d/samba to work from ram, and not from a location on the hard drive in question.
- Got inotify-tools, and tried to use inotifywatch to figure out what happens. Not seeing a lot of actual activity, though.
- iotop tells me transmission jumps on the SSD during download, and a whole lot of other processes. It would seem the journaling process is active and doing IO, albeit a very small amount. Might this block spin down? I've got EXT4 for all drives, and there have been issues with the journaling blocking spin down...
- Used lsof | grep sd# (# as the hard drive identification), which tells me on all disks there are three commands running: all three named jbd2/sd#. They look like this:
root@cardboardbox:~# lsof | grep sda
COMMAND PID TID USER FD TYPE DEVICE SIZE/OFF NODE NAME # pasted for easy reading
jbd2/sda1 1929 root cwd DIR 8,33 4096 2 /
jbd2/sda1 1929 root rtd DIR 8,33 4096 2 /
jbd2/sda1 1929 root txt unknown /proc/1929/exe
^C
root@cardboardbox:~# lsof | grep sdb
jbd2/sdb1 1931 root cwd DIR 8,33 4096 2 /
jbd2/sdb1 1931 root rtd DIR 8,33 4096 2 /
jbd2/sdb1 1931 root txt unknown /proc/1931/exe
^C
root@cardboardbox:~# lsof | grep sdd
jbd2/sdd1 1933 root cwd DIR 8,33 4096 2 /
jbd2/sdd1 1933 root rtd DIR 8,33 4096 2 /
jbd2/sdd1 1933 root txt unknown /proc/1933/exe
^C
root@cardboardbox:~# lsof | grep sdc
jbd2/sdc1 342 root cwd DIR 8,33 4096 2 /
jbd2/sdc1 342 root rtd DIR 8,33 4096 2 /
jbd2/sdc1 342 root txt unknown /proc/342/exe
^C
Alles anzeigen
Is this indeed due to the EXT4 journaling, or should I keep looking?
If yes: is there some form of fix, aside from moving everything over to XFS?
If no: how do I keep looking? I've not enough knowledge to know further steps