hmmm ...
just having a look at sysstat on my F520's this morning:
CPU NFS CIFS HTTP Net kB/s Disk kB/s Tape kB/s Cache in out read write read write age 79% 1 0 0 2 0 11619 0 0 0 >60 79% 0 0 0 2 0 11314 52 0 0 >60 75% 1 0 0 2 0 11158 0 0 0 >60 76% 8 0 0 48 2 11517 0 0 0 >60 83% 17 0 0 6 3 11700 157 0 0 >60 76% 2 0 0 3 0 11199 0 0 0 >60 80% 12 0 0 4 15 11743 63 0 0 >60 74% 1 0 0 2 0 11329 0 0 0 >60 74% 1 0 0 3 0 10791 45 0 0 >60 72% 2 0 0 3 0 10904 1 0 0 >60 73% 1 0 0 2 0 11728 0 0 0 >60
seems like a lot of CPU and DISK IO for no nfs ops. any idea what could be going on here? thanks!
-- michael
Seems like you just had a disk failure, and this is just a result of the disk rebuild. 2nd option is that you're running a disk scrub now...
You can check the rebuild with "vol status" - you'll see "rebuilding" or something similar in one of the volumes...
Eyal.
mgx@ornl.gov wrote:
hmmm ...
just having a look at sysstat on my F520's this morning:
CPU NFS CIFS HTTP Net kB/s Disk kB/s Tape kB/s Cache in out read write read write age 79% 1 0 0 2 0 11619 0 0 0 >60 79% 0 0 0 2 0 11314 52 0 0 >60 75% 1 0 0 2 0 11158 0 0 0 >60 76% 8 0 0 48 2 11517 0 0 0 >60 83% 17 0 0 6 3 11700 157 0 0 >60 76% 2 0 0 3 0 11199 0 0 0 >60 80% 12 0 0 4 15 11743 63 0 0 >60 74% 1 0 0 2 0 11329 0 0 0 >60 74% 1 0 0 3 0 10791 45 0 0 >60 72% 2 0 0 3 0 10904 1 0 0 >60 73% 1 0 0 2 0 11728 0 0 0 >60
seems like a lot of CPU and DISK IO for no nfs ops. any idea what could be going on here? thanks!
-- michael
mgx@ornl.gov (michael) wrote:
just having a look at sysstat on my F520's this morning:
CPU NFS CIFS HTTP Net kB/s Disk kB/s Tape kB/s Cache in out read write read write age 79% 1 0 0 2 0 11619 0 0 0 >60 79% 0 0 0 2 0 11314 52 0 0 >60 75% 1 0 0 2 0 11158 0 0 0 >60
[...]
seems like a lot of CPU and DISK IO for no nfs ops. any idea what could be going on here? thanks!
and Eyal.Traitel@motorola.com responds:
< Seems like you just had a disk failure, and this is just a result of the disk < rebuild.
That would be showing much more disk write activity. Also, of course, one would expect to have been alerted by autosupport mail, etc.
< 2nd option is that you're running a disk scrub now...
Given the time of week when it was posted, this seems 99.9% certain!
I suppose that Michael has never been watching his filer early on Sunday morning before... Or was it Saturday evening carousing that resulted in a temporary loss of memory? :-)
The start and completion of raid scrubbing are recorded in /etc/messages (and on the console as well, if you haven't changed /etc/syslog.conf).
Chris Thompson University of Cambridge Computing Service, Email: cet1@ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, Phone: +44 1223 334715 United Kingdom.
hehehe ...
neither, meerly a bout of insomnia induced paranoia :-) we've been having power fulctuations/outages in the building all week and the filers recovered so well from them i've been waiting for something bad to happen, i guess. again, thanks for the sanity check!
-- michael
Given the time of week when it was posted, this seems 99.9% certain!
I suppose that Michael has never been watching his filer early on Sunday morning before... Or was it Saturday evening carousing that resulted in a temporary loss of memory? :-)
The start and completion of raid scrubbing are recorded in /etc/messages (and on the console as well, if you haven't changed /etc/syslog.conf).
Chris Thompson University of Cambridge Computing Service, Email: cet1@ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, Phone: +44 1223 334715 United Kingdom.
-
Bruce Sterling Woodcock -
Chris Thompson -
Eyal Traitel -
mgx＠ornl.gov