idle/standby functionality of drives gone after upgrade from 9.2
After an upgrade from 9.2 to 184.108.40.206 none of my drives enters into the idle or standby mode.
I tried it manually with the command ataidle -s /dev/ada0.
The drive stops for about 1 second into the standby mode and starts again.
Thx and regards Mudi
#1 Updated by Josh Paetzel about 5 years ago
- Status changed from Unscreened to Screened
- Assignee set to Josh Paetzel
My suspicion is the system is logging to the system dataset which is waking up the drives.
In system -> settings -> advanced the last item is Use system dataset for syslog:
Is that checked?
#2 Updated by Frank Visser about 5 years ago
Because of recent implementation of .system dataset method, a data pool fails to spin down due to frequent writes to .system.
Unsetting "Use system dataset for syslog" doesn't solve it because only syslog is moved to /var/log.
Other logging from samba4/core is still on data pool.
Also old syslog data isn't removed after unsetting "Use system dataset for syslog".
A user should have the possibility in the GUI to choose where to log. Mixing system data with storage data is in my opinion illogical.
(using FreeNAS 220.127.116.11-RELEASE with 2x 500GB ZFS mirror + CF-card for OS)
#3 Updated by Mohammad Fakih about 5 years ago
Unchecking the "Use system dataset for syslog" box solved my problem.
Thank you Josh and sorry for the wrongly bug report.
You're right. With logged in clients and running services like CIFS or ISTGT the drives don't spin down. But that's okay for me.
I agree with you that this would be nicer and a better solution if the drives spins down indenpendently on logged in clients or running services.
So dear IX Systems Team if you got time ;)
Thanks to all and regards Mudi
#5 Updated by Frank Visser about 5 years ago
@Mohammed & Josh
You are missing both the point here; again unsetting "Use system dataset for syslog" doesn't solve it because only syslog is moved to /var/log. Other logging from samba4/core is still on data pool and also old syslog data isn't removed after unsetting "Use system dataset for syslog".
Ofcourse the data pool disks are spinning when running a service like CIFS and a client is using files on the data pool. That is suspected behavior.
But the drives won't spin down when nobody is using the drives in the connected network BECAUSE of logging in "samba4" and/or "core" dataset still remaining on the datapool.
So "Behaves correctly" isn't right...