I'm configuring a new server with 2 SSDs and 2 HDDs. The HDDs are only used once every 6 hours and I need them to spindown when not in use in order to save energy. Initially these drives were not configured as Proxmox storage. The server does not yet have any VMs or containers. To test spindown, I ran the following commands:
The behavior is as expected and the drives spin down after 60s.
I then configured the drives as a ZFS pool as follows:
From this moment onwards, the drives refuse to spindown. Here's what I tried:
What am I missing or doing wrong? Any help will be much appreciated.
Bash:
/usr/sbin/hdparm -S 12 /dev/sda
/usr/sbin/hdparm -S 12 /dev/sdb
/usr/sbin/hdparm -B 127 /dev/sda
/usr/sbin/hdparm -B 127 /dev/sdb
/dev/sda:
setting standby to 12 (1 minutes)
/dev/sdb:
setting standby to 12 (1 minutes)
/dev/sda:
setting Advanced Power Management level to 0x7f (127)
APM_level = 127
/dev/sdb:
setting Advanced Power Management level to 0x7f (127)
APM_level = 127
The behavior is as expected and the drives spin down after 60s.
I then configured the drives as a ZFS pool as follows:
Bash:
root@nea[~] cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content vztmpl,iso,backup
zfspool: local-zfs
pool rpool/data
content rootdir,images
sparse 1
nfs: nea
export /lpool/backup/ultima/pve
path /mnt/nea/pve
server nea
content backup,images
nodes ultima
options noatime,nodiratime,norelatime
prune-backups keep-all=1
From this moment onwards, the drives refuse to spindown. Here's what I tried:
- add the following code to /etc/pve/storage.cfg:
Code:devices {# changed on 2023-02-16 to prevent wakeup of HDDs global_filter=["r|/dev/zd.*|", "r|/dev/sda|", "r|/dev/sdb|"] }
After editing /etc/pve/storage.cfg I ran "proxmox-boot-tool refresh" although I'm not sure if this is required. - disabled the pool in the Proxmox GUI and checked if the pool was dismounted client-side.
- from the syslog: Feb 15 15:12:16 nea lvm[1079116]: pvscan[1079116] /dev/zd16p3 excluded by filters: device is rejected by filter config.
NOTE: /dev/sda, /dev/sdb never appear as being excluded by the global filter. -
Bash:
root@nea[~] smartctl -n standby /dev/sda smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.19.17-2-pve] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org Device is in IDLE mode
Code:
proxmox-ve: 7.3-1 (running kernel: 5.19.17-2-pve)
pve-manager: 7.3-6 (running version: 7.3-6/723bb6ec)
pve-kernel-helper: 7.3-4
pve-kernel-5.15: 7.3-2
pve-kernel-5.19: 7.2-15
pve-kernel-5.19.17-2-pve: 5.19.17-2
pve-kernel-5.19.17-1-pve: 5.19.17-1
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.3
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.3-1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-2
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.3-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-1
lxcfs: 5.0.3-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.3.3-1
proxmox-backup-file-restore: 2.3.3-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.1-1
proxmox-widget-toolkit: 3.5.5
pve-cluster: 7.3-2
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.6-3
pve-ha-manager: 3.5.1
pve-i18n: 2.8-2
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1
What am I missing or doing wrong? Any help will be much appreciated.
Last edited: