March 7, 201214 yr Here is my line in go script >>> /usr/local/sbin/cache_dirs -w -m 1 -M 10 -d 9999 I noticed that when i browsed a share, share/folder/folder/file... i didnt actually click the file or execute it but i noticed the drive had spun up just to go into the second folder, is this wrong ?..i was just seeing what was inside folder as opposed to executing or actually accessing the file..from what i can see the depth is set to 9999 so it shouldnt be spinning the drive up ?
March 7, 201214 yr Here is my line in go script >>> /usr/local/sbin/cache_dirs -w -m 1 -M 10 -d 9999 I noticed that when i browsed a share, share/folder/folder/file... i didnt actually click the file or execute it but i noticed the drive had spun up just to go into the second folder, is this wrong ?..i was just seeing what was inside folder as opposed to executing or actually accessing the file..from what i can see the depth is set to 9999 so it shouldnt be spinning the drive up ? The -d 9999 is doing nothing to help, or harm you... unless you really do have directory paths deeper than that. Other than that, a disk will spin up if something on it is accessed that is not in the disk buffer cache. To know exactly what is being accessed, you can use the inotify tools package. Odds are it is your file browser inspecting the contents of the files to show you thumbnails, etc.
March 7, 201214 yr Author Hmm...that makes sense...those darn background processes..sort of defeats the object..ill certainly install that and see.
Archived
This topic is now archived and is closed to further replies.