December 26, 200916 yr Sooo....if lsof shows there's no files open and there's been no activity for well over an hour wouldn't that be an indication that it isn't spinning down correctly like I think it should be? If lsof shows no files currently open, it does not infer no file was open 5 seconds ago. It simply indicated no file is currently open. To monitor the activity at a lower level you need a different tool that is not normally part of unRAID. Download inotifytools from http://www.slackware.org.il/slackware/slackware-12.2/slackware/a/inotify-tools-3.13-i486-1.tgz Install it, by typing: installpkg inotify-tools-3.13-i486-1.tgz then invoke it by typing (using the correct disk) inotifywait -r -m /mnt/disk1 It will show all activity, as it occurs. Joe L.
December 26, 200916 yr Sooo....if lsof shows there's no files open and there's been no activity for well over an hour wouldn't that be an indication that it isn't spinning down correctly like I think it should be? If lsof shows no files currently open, it does not infer no file was open 5 seconds ago. It simply indicated no file is currently open. To monitor the activity at a lower level you need a different tool that is not normally part of unRAID. Download inotifytools from http://www.slackware.org.il/slackware/slackware-12.2/slackware/a/inotify-tools-3.13-i486-1.tgz Install it, by typing: installpkg inotify-tools-3.13-i486-1.tgz then invoke it by typing (using the correct disk) inotifywait -r -m /mnt/disk1 It will show all activity, as it occurs. Joe L. Fair enough, thanks! I'll grab it and install it later but my READ/WRITE counter hasn't moved for well over an hour? Shouldn't that also show activity or am I misunderstanding what the READ/WRITE counters do? ETA: My assumption is based on the READ/WRITE counters being the same for well over an hour and lsof showing no file being open.
January 29, 201016 yr I am having the same problem. My disk1 isn't showing as being spun down even though it hasn't been accessed for 8000 seconds (over 2 hours). I have the spin down time set to 15 minutes. During the last two hours I've been using disk2 constantly. If I let it sit long enough so that disk2 sits for 15 min, then the web interface shows both as being spun down.
January 29, 201016 yr I am having the same problem. My disk1 isn't showing as being spun down even though it hasn't been accessed for 8000 seconds (over 2 hours). I have the spin down time set to 15 minutes. During the last two hours I've been using disk2 constantly. If I let it sit long enough so that disk2 sits for 15 min, then the web interface shows both as being spun down. It sounds as if they are in the same spinup group. See here for an explanation: http://lime-technology.com/forum/index.php?topic=4782.msg43821#msg43821 If not, are you running any other programs or processes, or add-ons that might be scanning your directories? cache_dirs.sh (for example) In that case, you might be using the buffer cache faster than it can scan the folders, and therefor the blocks in memory representing the directories are re-used for data, since they were the least recently used, and then need to be re-read from the disks themselves. Can you post the contents of your config/disk.cfg file? (It shows the spinup groups) and a syslog. (It shows hardware details) Joe L.
January 29, 201016 yr It sounds as if they are in the same spinup group. See here for an explanation: http://lime-technology.com/forum/index.php?topic=4782.msg43821#msg43821 Joe L. That was exactly my problem, thanks.
January 29, 201016 yr That was exactly my problem, thanks. Just to clarify something so others don't get the wrong idea. the Spin up groups that was implemented is not a "problem." It was introduced and turned on by default to solve a problem that was evident when IO requests were made to a drive that was sleeping that is on the same "controller" (<- wrong choice of words but hopefully you get the idea). This would cause a stutter in video and "Spin up groups" was introduced to fix the problem. In general I suggest it be left on as it makes the viewing experience better when the problem is present.
January 30, 201016 yr That was exactly my problem, thanks. Just to clarify something so others don't get the wrong idea. the Spin up groups that was implemented is not a "problem." It was introduced and turned on by default to solve a problem that was evident when IO requests were made to a drive that was sleeping that is on the same "controller" (<- wrong choice of words but hopefully you get the idea). This would cause a stutter in video and "Spin up groups" was introduced to fix the problem. In general I suggest it be left on as it makes the viewing experience better when the problem is present. Correct. It was a problem for me because I was trying to spin down drives to save energy (my drives aren't on the same controller).
Archived
This topic is now archived and is closed to further replies.