- Platform information:
- Hardware: Standard x86-64 CPU (Intel)/16GB/Several SSD/HDDs
- OS: debian 9.5, openHAB is running in a Docker container, standard openHAB image 2.5.0
- Java Runtime Environment: from Docker container
- openHAB version: 2.5.0
Hi,
I recently discovered that my hard drives are always active and are not spinning down anymore.
I tried to investigate further: I manually spun down all my hard drives with hdparm -y /dev/sd*
and as soon as I restart the docker container, all my hard drives spun up again.
I tried to check the disks access with inotifywatch, but I was not able to find any event on the hard drives:
inotifywatch -v -e access -e modify -r /media/hdd1to
Establishing watches...
Setting up watch(es) on /media/hdd1to
OK, /media/hdd1to is now being watched.
Total of 279 watches.
Finished establishing watches, now collecting statistics.
^CNo events occurred.
In my openHAB docker-compose file, all the volumes that I use are either on an ssd, or in a ramdisk, no volume is using a hard disk.
openhab:
container_name: openhab
image: 'openhab/openhab:2.5.0'
restart: always
volumes:
- /etc/localtime:/etc/localtime:ro
- /etc/timezone:/etc/timezone:ro
- ./openHAB/volumes/addons:/openhab/addons
- ./openHAB/volumes/conf:/openhab/conf
- ./openHAB/volumes/userdata:/openhab/userdata
- /media/ramdisk/OpenhabLogs:/openhab/userdata/logs
- ./openHAB/volumes/socat/socat-ttyNET0.conf:/etc/supervisor/conf.d/socat-ttyNET0.conf
- ./openHAB/volumes/socat/socat-ttyNET1.conf:/etc/supervisor/conf.d/socat-ttyNET1.conf
- ./openHAB/volumes/socat/socat-ttyNET2.conf:/etc/supervisor/conf.d/socat-ttyNET2.conf
networks:
- domotique
- multimedia_multimedia
ports:
- "8080:8080"
- "5555:5555"
- "5007:5007"
- "8101:8101"
environment:
USER_ID: "472"
GROUP_ID: "472"
CRYPTO_POLICY: "unlimited"
EXTRA_JAVA_OPTS: "-Dgnu.io.rxtx.SerialPorts=/dev/ttyNET0:/dev/ttyNET1:/dev/ttyNET2"
mem_limit: 2048M
How can I find why my disks are spinning up when I use openhab, and why they do not spin down anymore when the openHAB container is active?