August 18, 200916 yr I have 9 WD Green 1TB drives in my array (one for parity). Currently drive #8 has no data on it at all. This drive is included in a few shares, but it is completely empty. The strange thing is that this drive never spins down. The remainder of the drives do, but not this one. Can anyone think of a reason why this might be? Again, the only thing diferrent about this drive from the others is that all the others contain data.
August 18, 200916 yr Sometimes you need to initiate a manual spin down from web page first. After that the automated spin down timers start functioning.
August 19, 200916 yr Author Well, tried the manual spin-down a couple of ways and the darn thing keeps spinning back up! Just got home. Gone all day. All drives are spun down except for Drive 8 and Parity.
August 19, 200916 yr Well, tried the manual spin-down a couple of ways and the darn thing keeps spinning back up! Just got home. Gone all day. All drives are spun down except for Drive 8 and Parity. If it keeps spinning up, then the odds are something is accessing it.
August 19, 200916 yr Well, tried the manual spin-down a couple of ways and the darn thing keeps spinning back up! Just got home. Gone all day. All drives are spun down except for Drive 8 and Parity. If it keeps spinning up, then the odds are something is accessing it. Agreed, try clearing the counters to reveal writes. also you could try the fuser command. or use the following script. root@Atlas /tmp #cat ./fuser.sh #!/bin/bash for fs in /mnt/user /mnt/disk* do [ ! -d ${fs} ] && continue for pid in $(fuser -cu $fs 2>/dev/null) do ps --no-headers -fp ${pid} done done example output on my system root@Atlas /tmp #chmod u+rwx ./fuser.sh root@Atlas /tmp #./fuser.sh root 12106 12105 0 Aug16 pts/0 00:00:00 -bash root 13029 1 0 Aug16 ? 00:00:01 /usr/bin/SCREEN -T linux -dmUS rTorrent /mnt/disk1/bittorrent/bin//rc.rTorrent run root 13030 13029 0 Aug16 pts/3 00:08:17 /usr/bin/rtorrent -n -o import=/boot/custom/etc/rTorrent.rc root 13074 12106 0 Aug16 pts/0 00:00:00 /bin/bash /boot/custom/bin/screens root 13137 13074 0 Aug16 pts/0 00:00:00 screen -x 13029.rTorrent root 13558 13557 0 Aug16 pts/4 00:00:00 -bash
August 20, 200916 yr Or... if your array is otherwise not getting any other activity, you can try this command. It enables logging to the syslog all block device access. (Don't leave it enabled, as it will fill the syslog. Turn it off by assigning "0" as the value.) sysctl vm.block_dump=1 root@Tower:/boot# sysctl vm.block_dump=1 vm.block_dump = 1 root@Tower:/boot# tail -f /var/log/syslog Aug 19 20:56:01 Tower kernel: shfs(17671): READ block 637633248 on md11 Aug 19 20:56:09 Tower kernel: shfs(17671): READ block 641945696 on md11 Aug 19 20:58:15 Tower kernel: shfs(17668): READ block 908283400 on md3 Aug 19 20:58:29 Tower kernel: shfs(17668): READ block 809151064 on md3 Aug 19 20:58:29 Tower kernel: shfs(17668): READ block 914047120 on md3 Aug 19 20:58:29 Tower kernel: shfs(17668): READ block 921837968 on md3 Aug 19 20:59:49 Tower kernel: shfs(29884): READ block 921838936 on md3 Aug 19 20:59:49 Tower kernel: shfs(17673): READ block 921837880 on md3 Aug 19 20:59:49 Tower kernel: shfs(17673): READ block 921837592 on md3 Aug 19 20:59:49 Tower kernel: shfs(17674): READ block 921839000 on md3 Aug 19 20:59:49 Tower kernel: shfs(17670): READ block 921837632 on md3 Aug 19 20:59:49 Tower kernel: shfs(17668): READ block 921837656 on md3 Aug 19 20:59:49 Tower kernel: shfs(17668): READ block 914047152 on md3 Aug 19 20:59:50 Tower kernel: shfs(17669): READ block 914047200 on md3 Aug 19 20:59:50 Tower kernel: shfs(17669): READ block 914047456 on md3 Aug 19 20:59:50 Tower kernel: shfs(17669): READ block 914047712 on md3 Aug 19 20:59:50 Tower kernel: shfs(17678): READ block 914047968 on md3 Aug 19 20:59:50 Tower kernel: shfs(17678): READ block 914048224 on md3 Aug 19 20:59:50 Tower kernel: shfs(17678): READ block 914048480 on md3 Aug 19 20:59:50 Tower kernel: shfs(17678): READ block 914048736 on md3 Aug 19 20:59:51 Tower kernel: shfs(29884): READ block 914048992 on md3 Aug 19 20:59:51 Tower kernel: shfs(29884): READ block 914049248 on md3 Aug 19 20:59:51 Tower kernel: shfs(29884): READ block 914049504 on md3 Aug 19 20:59:51 Tower kernel: shfs(29884): READ block 914047136 on md3 Aug 19 20:59:51 Tower kernel: shfs(29884): READ block 914049672 on md3 Aug 19 20:59:51 Tower kernel: shfs(29884): READ block 914049928 on md3 Aug 19 20:59:51 Tower kernel: shfs(17669): READ block 914050016 on md3 Aug 19 20:59:51 Tower kernel: shfs(17669): READ block 914050272 on md3 Aug 19 20:59:51 Tower kernel: shfs(17669): READ block 914050528 on md3 Aug 19 20:59:51 Tower kernel: shfs(17669): READ block 914050784 on md3 Aug 19 20:59:51 Tower kernel: shfs(17674): READ block 914051040 on md3 Aug 19 20:59:51 Tower kernel: shfs(17674): READ block 914051296 on md3 Aug 19 20:59:51 Tower kernel: shfs(17674): READ block 914051552 on md3 Aug 19 20:59:51 Tower kernel: shfs(17674): READ block 914051808 on md3 Aug 19 20:59:52 Tower kernel: shfs(17671): READ block 914052064 on md3 Aug 19 20:59:52 Tower kernel: shfs(17671): READ block 914052320 on md3 Aug 19 20:59:52 Tower kernel: shfs(17671): READ block 914052576 on md3 Aug 19 20:59:52 Tower kernel: shfs(17671): READ block 914052832 on md3 Aug 19 20:59:52 Tower kernel: shfs(17673): READ block 914053088 on md3 Aug 19 20:59:52 Tower kernel: shfs(17673): READ block 914053344 on md3 Aug 19 20:59:52 Tower kernel: shfs(17673): READ block 914053600 on md3 Aug 19 20:59:52 Tower kernel: shfs(17673): READ block 914053816 on md3 Aug 19 20:59:52 Tower kernel: shfs(17673): READ block 914054072 on md3 Aug 19 20:59:53 Tower kernel: shfs(17671): READ block 914054120 on md3 Aug 19 20:59:53 Tower kernel: shfs(17671): READ block 914054376 on md3 Aug 19 20:59:53 Tower kernel: shfs(17671): READ block 914054632 on md3 Aug 19 20:59:53 Tower kernel: shfs(17671): READ block 914054888 on md3 Aug 19 20:59:53 Tower kernel: shfs(17668): READ block 914055144 on md3 Aug 19 20:59:53 Tower kernel: shfs(17668): READ block 914055400 on md3 Aug 19 20:59:53 Tower kernel: shfs(17668): READ block 914055656 on md3 Aug 19 20:59:53 Tower kernel: shfs(17668): READ block 914055912 on md3 Aug 19 20:59:53 Tower kernel: shfs(17669): READ block 914056168 on md3 Aug 19 20:59:53 Tower kernel: shfs(17669): READ block 914056424 on md3 Aug 19 20:59:53 Tower kernel: shfs(17669): READ block 914056680 on md3 Aug 19 20:59:53 Tower kernel: shfs(17669): READ block 914056936 on md3 Aug 19 20:59:54 Tower kernel: shfs(17671): READ block 914057192 on md3 Aug 19 20:59:54 Tower kernel: shfs(17671): READ block 914057448 on md3 Aug 19 20:59:54 Tower kernel: shfs(17671): READ block 914057704 on md3 Aug 19 20:59:54 Tower kernel: shfs(17671): READ block 914053808 on md3 Aug 19 20:59:54 Tower kernel: shfs(17671): READ block 914057776 on md3 Aug 19 20:59:54 Tower kernel: shfs(17671): READ block 914058032 on md3 Aug 19 20:59:55 Tower kernel: shfs(17675): READ block 914058216 on md3 Aug 19 20:59:55 Tower kernel: shfs(17675): READ block 914058472 on md3 Aug 19 20:59:55 Tower kernel: shfs(17675): READ block 914058728 on md3 Aug 19 20:59:55 Tower kernel: shfs(17675): READ block 914058984 on md3 Aug 19 20:59:56 Tower kernel: shfs(17675): READ block 914059240 on md3 Aug 19 20:59:56 Tower kernel: shfs(17675): READ block 914059496 on md3 Aug 19 20:59:56 Tower kernel: shfs(17675): READ block 914059752 on md3 Aug 19 20:59:56 Tower kernel: shfs(17675): READ block 914060008 on md3 Aug 19 20:59:56 Tower kernel: shfs(17678): READ block 914060264 on md3 Aug 19 20:59:56 Tower kernel: shfs(17678): READ block 914060520 on md3 Aug 19 20:59:56 Tower kernel: shfs(17678): READ block 914060776 on md3 Aug 19 20:59:56 Tower kernel: shfs(17678): READ block 914061032 on md3 Aug 19 20:59:57 Tower kernel: shfs(17673): READ block 914061288 on md3 Aug 19 20:59:57 Tower kernel: shfs(17673): READ block 914061544 on md3 Aug 19 20:59:57 Tower kernel: shfs(17673): READ block 914061800 on md3 Aug 19 20:59:57 Tower kernel: shfs(17673): READ block 914061984 on md3 Aug 19 20:59:57 Tower kernel: shfs(17673): READ block 914062240 on md3 Aug 19 20:59:58 Tower kernel: shfs(17668): READ block 914062320 on md3 Aug 19 20:59:58 Tower kernel: shfs(17668): READ block 914062576 on md3 Aug 19 20:59:58 Tower kernel: shfs(17668): READ block 914062832 on md3 Aug 19 20:59:58 Tower kernel: shfs(17668): READ block 914063088 on md3 Aug 19 20:59:58 Tower kernel: shfs(17670): READ block 914063344 on md3 Aug 19 20:59:58 Tower kernel: shfs(17670): READ block 914063600 on md3 Aug 19 20:59:58 Tower kernel: shfs(17670): READ block 914063856 on md3 Aug 19 20:59:58 Tower kernel: shfs(17670): READ block 914064112 on md3 Aug 19 20:59:59 Tower kernel: shfs(17668): READ block 914064368 on md3 Aug 19 20:59:59 Tower kernel: shfs(17668): READ block 914064624 on md3 Aug 19 20:59:59 Tower kernel: shfs(17668): READ block 914064880 on md3 Aug 19 20:59:59 Tower kernel: shfs(17668): READ block 914065136 on md3 Aug 19 21:00:00 Tower kernel: shfs(17672): READ block 914065392 on md3 Aug 19 21:00:00 Tower kernel: shfs(17672): READ block 914065648 on md3 Aug 19 21:00:00 Tower kernel: shfs(17672): READ block 914061976 on md3 Aug 19 21:00:00 Tower kernel: shfs(17672): READ block 914065880 on md3 Aug 19 21:00:00 Tower kernel: shfs(17672): READ block 914066136 on md3 Aug 19 21:00:00 Tower kernel: shfs(17672): READ block 914066392 on md3 Aug 19 21:00:01 Tower kernel: shfs(17675): READ block 914066416 on md3 Aug 19 21:00:01 Tower kernel: shfs(17675): READ block 914066672 on md3 Aug 19 21:00:01 Tower kernel: shfs(17675): READ block 914066928 on md3 Aug 19 21:00:01 Tower kernel: shfs(17675): READ block 914067184 on md3 Aug 19 21:00:01 Tower kernel: shfs(17678): READ block 914067440 on md3 Aug 19 21:00:01 Tower kernel: shfs(17678): READ block 914067696 on md3 Aug 19 21:00:01 Tower kernel: shfs(17678): READ block 914067952 on md3 Aug 19 21:00:01 Tower kernel: shfs(17678): READ block 914068208 on md3 Aug 19 21:00:02 Tower kernel: shfs(17669): READ block 914068464 on md3 Aug 19 21:00:02 Tower kernel: shfs(17669): READ block 914068720 on md3 Aug 19 21:00:02 Tower kernel: shfs(17669): READ block 914068976 on md3 Aug 19 21:00:02 Tower kernel: shfs(17669): READ block 914069232 on md3 Aug 19 21:00:03 Tower kernel: shfs(17674): READ block 914069488 on md3 Aug 19 21:00:03 Tower kernel: shfs(17674): READ block 914069744 on md3 Aug 19 21:00:03 Tower kernel: shfs(17674): READ block 914070000 on md3 Aug 19 21:00:03 Tower kernel: shfs(17674): READ block 914070256 on md3 Aug 19 21:00:03 Tower kernel: shfs(29884): READ block 914070512 on md3 Aug 19 21:00:03 Tower kernel: shfs(29884): READ block 914070768 on md3 Aug 19 21:00:03 Tower kernel: shfs(29884): READ block 914071024 on md3 Aug 19 21:00:03 Tower kernel: shfs(29884): READ block 914071280 on md3 Aug 19 21:00:06 Tower kernel: shfs(17675): dirtied inode 4762 (THE_SAINT.ISO) on md3 Aug 19 21:00:06 Tower kernel: pdflush(20264): WRITE block 39848 on md3 Aug 19 21:00:06 Tower kernel: pdflush(20264): WRITE block 39856 on md3 Aug 19 21:00:16 Tower kernel: emhttp(1628): dirtied inode 7370 (hdc) on sysfs Aug 19 21:00:16 Tower kernel: emhttp(1628): dirtied inode 6821 (hde) on sysfs Aug 19 21:00:16 Tower kernel: pdflush(20264): WRITE block 39864 on md3 Aug 19 21:00:16 Tower kernel: pdflush(20264): WRITE block 914047120 on md3 ^C <-- I typed control-C to get out of the tail -f root@Tower:/boot# sysctl vm.block_dump=0 vm.block_dump = 0 After I enabled the block access dump I accessed my Movies share from one of my media players and started playing a movie. I turned off the file-block-access debugging once I saw what was accessed on the disk to keep from filling the syslog. (and using all of my RAM) I was surprised to see "writes" to the disk... (possibly, to track the point at which I stopped the movie, so it can resume at the same point) In any case, you can see if "writes" or "reads" are keeping your disk busy, and spun up. Another possibility is to download and install the inotifywait program in the inotify-tools package. root@Tower:/boot/packages# installpkg inotify-tools-3.13-i486-1.tgz Installing package inotify-tools-3.13-i486-1... PACKAGE DESCRIPTION: inotify-tools: inotify-tools (command line utilities for inotify) inotify-tools: inotify-tools: inotify-tools is a set of command-line programs for Linux providing a inotify-tools: simple interface to inotify. These programs can be used to monitor inotify-tools: and act upon filesystem events. inotify-tools: inotify-tools: For more information see the inotifywait and inotifywatch man pages. inotify-tools: inotify-tools: inotify-tools home: http://inotify-tools.sourceforge.net/ inotify-tools: Executing install script for inotify-tools-3.13-i486-1... Then typing the following sets up a watch on all the ISO files on the disk. I then played the movie from one of my clients on the LAN.: inotifywait -m /mnt/disk3/Movies/*.ISO root@Tower:/boot/custom/bin# inotifywait -m /mnt/disk3/Movies/*.ISO Setting up watches. Watches established. /mnt/disk3/Movies/THE_SAINT.ISO OPEN /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS /mnt/disk3/Movies/THE_SAINT.ISO ACCESS ^C Again I typed control-C to get out of the "watch" of file-activity. You can do the same for the user-shares root@Tower:/boot# inotifywait -m /mnt/user/Movies/*.ISO Setting up watches. Watches established. /mnt/user/Movies/THE_SAINT.ISO OPEN /mnt/user/Movies/THE_SAINT.ISO CLOSE_NOWRITE,CLOSE /mnt/user/Movies/THE_SAINT.ISO OPEN /mnt/user/Movies/THE_SAINT.ISO CLOSE_NOWRITE,CLOSE ^C There you go, several additional ways to try to figure out what is accessing files, and what is being used for the access. Joe L.
Archived
This topic is now archived and is closed to further replies.