This is where rac8006 “Mount” command helps a little. I’m not too sure if it helps a lot, but I’ll give him the credit of it helping “a little”.
I’ve been trying to get rid of that 5-7 second wake up and it has been illusive, but if you are up to it… here it is…
I’ve modified monitor.sh under “/usr/local/sbin”
cd /usr/local/sbin
vi monitorio.sh
at the bottom of the file… it touches files in order to set the date time for counter. This is one of the problems of 5 to 7 seconds wakeups. What happens, I believe, is that the drive is put to sleep and the touches triggers the fact that the drive has more data to write. Back a year ago, I agonized over the fact that it always wait for the 10 minutes is up, drive goes to sleep, then 2 seconds later it wakes up to write again? it made no sense. Thus I put in the syncs… more than enough to flush out the data.
You will have to figure out where I inserted the Syncs.
ior_datavol=$ior_datavol2
iow_datavol=$iow_datavol2
iow_root=$iow_root2
smartTestStatus=`getSmartTestStatus.sh | awk '{print $1}'`
if [ "$standby_enable" == "enabled" ] && [ "$sleepcount" -eq "$standby_time" ] && [ "$smartTestStatus" != "inprogress" ]; then
touch /tmp/standby
sync
sleep 5
enterStandbyTime=`date +%s`
echo "Enter standby"
if [ "$1" == "debug" ]; then
echo "`date`: Enter standby "
dmesg -c > /dev/null
fi
sync
sleep 5
sync
sleep 5
sync
sleep 5
for i in ${drivelist[@]}; do
hdparm -y $i >/dev/null
done
# turn on solid blue if applicable
# ledCtrl.sh LED_EV_DISK_STBY LED_STAT_IN_PROG
ledCtrl.sh LED_EV_HALT LED_STAT_OK
sleep 5
break
fi
done
fi
done
Yes I have the led set to turn off when it goes to sleep rather than the slow blink.
Last but not least… Yup I also shut down Cron for almost a year except once in awhile I notice that you have to turn it on for a few days to clear out the logs.
/etc/init.d/cron stop
I would not recommend disabling the cron permanently.
I have all the tricks of the trade operating on my ArchiveServer and it sleeps for up to 3 days without waking up. The actual system is still awake, thus pings and other network functions doesn’t wake up the hard drive but yes I still get the occasional 73 second wake ups.
2016-02-17T19:20:39.638313-08:00 di=tHvaf6FVzn notice logger: exit standby after 73 (since 2016-02-17 19:19:21.624665001 -0800)
2016-02-19T09:56:50.731742-08:00 di=tHvaf6FVzn notice logger: exit standby after 138660 (since 2016-02-17 19:25:45.944665001 -0800)
2016-02-23T10:20:03.458390-08:00 di=tHvaf6FVzn notice logger: exit standby after 346681 (since 2016-02-19 10:01:57.094665001 -0800)
2016-02-24T00:18:58.716538-08:00 di=tHvaf6FVzn notice logger: exit standby after 50024 (since 2016-02-23 10:25:09.834665001 -0800)
2016-02-25T21:01:42.642397-08:00 di=tHvaf6FVzn notice logger: exit standby after 160652 (since 2016-02-24 00:24:04.974665001 -0800)
2016-02-26T10:23:35.816007-08:00 di=tHvaf6FVzn notice logger: exit standby after 47617 (since 2016-02-25 21:09:53.044665001 -0800)
2016-02-27T08:03:09.988500-08:00 di=tHvaf6FVzn notice logger: exit standby after 76438 (since 2016-02-26 10:49:06.604665001 -0800)