rac8006 wrote:
Ralphael
Check your var/log/user.log. Grep for Tally. You should see the following message.
“Tally daemon not installed, exiting tally function”. Checking for new files is only
done if $iow_datavol ne $iow_datavol2 or new df size greater than a threshold value.
Which means writes were done to the data volume.
I didn’t say that the samba problem caused wakeup problems. It caused the disk not to sleep.
Don’t know why moving the date line seems to eliminate the 8 second wakeup. But I have not
had a short wakeup time since Jun 12. Since Jun 12 its basically sleep until 03:00AM sleep until
I login sleep until 03:00AM.
What do you mean reading the epub directory?
In conclusion monitorio.sh is not waking up the disk.
RAC
Rac8006, seriously dood…
Its not that I’m pointing fingers at you but I am pointing at least one finger…
Remember how I woke up one night at 3:00 to find my cloud playing solitaire with my cron off? and I posted up to WD to complain about it.
http://community.wd.com/t5/WD-My-Cloud/The-Reason-why-your-WD-Cloud-ain-t-getting-no-sleep-and-We/m-p/872849#M33993
Within that thread you told me to turn off Samba…
Then you posted up this hopeful post for everyone to hope on… You even got 3 Kudos for that post!!
Here is where you said WD has your Samba fix… so the whole community is waiting with baited breath for WD to release this sleep time fix someday
http://community.wd.com/t5/WD-My-Cloud/Sleep-time-fix/m-p/873340#M34082
We all went “OH… its a Samba thing” and probably WD thought oh great, we got a sleep fix finally!!
--------- feeling sheepish yet? -----------
ok about that Tally thing, yeah I saw that message a year back but that message doesn’t appear in mine anymore in version 3.04. As I said I really don’t want to go tracing through monitorio.sh to see which code gets executed and which doesn’t.
In my monitorio.sh that line of code does run becuase I replaced it with a dummy line and it does get executed; perhaps not the Tally thing but something else.
Yes of course it checks if the volume size has grown and it writes to the hard drive the last changes to keep track. Flags are set to indicate that the media scan should run. Now if our media scan programs are turned off, flags are not reset and the volume size will still indicate that your hd has changed since the last time it was scanned. This flag may be set everytime your hard drive is on thereby causing perhaps logs to grow, flags and other indicators to be written. It is trying to tell your media scan program to run but we the hackers have turned it off, thereby it perpetuates this change in volume size continuously.
The only way to know for sure that the hard drive isn’t being monitored for size change is what I did a year ago, that is to rewrite monitorio.sh without those lines that tries to figure out if the volume has increased above a threshold number.
if moving the sync to after the date line eliminates the 8 second wakeup… yay!!! then I’ll move it after the date line…
Lastly epub directory. I use calibre to organize my epub (ebooks) and my library is quite large. The first level after you navigate into the epub directory is all the folders organized by author; somewhere in the neighborhood of 10,000 or more. So as soon as you navigate into epub, it takes several minutes before the directory pops up. With Samba before 3.04 firmware, it would pop up in a few minutes. After upgrading to 3.04 firmware, it would not return with a directory listing. At first I thought it hung, but after switching to AFP I realize that it just took time to read in all the entries.
Your Conclusion should be modified to: after moving the syncs after the dateline fixes the 8 second wake up, monitorio.sh is no longer waking up the disk.
For what it is worth Rac8006, the few findings that lead up to a 28 hour continuous sleep is well worth the effort; I can live with the occasional wakeup and I doubt that I would ever upgrade my firmware again.
Good job on your persistence Rac8006…
