Have you killed search indexing yet? :-) Also, ethereal should help looking for what remote machine might be hitting it. Even if you're not good with it, you can do some filtering and narrow things down a bit. The suggestion of pulling the network cable to isolate local/remote is also a good one...
*********************** Charlie Kaiser [email protected] Kingman, AZ *********************** > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Tuesday, November 10, 2009 2:17 PM > To: NT System Admin Issues > Subject: finding out what is causing disk to thrash? > > Looking for ideas here. > > I have a File server (windows 2003) that is connected to a > SAN via the F: > drive. The F: drive is used to store user data (home folders). > > The F: drive is showing bad performance. When viewing > Windows Performance Monitoring, the counter Disk Read % for > F: is constantly pegged at 100%. > Disk Write% on F: seems okay at < 10%. > > So, I'm trying to find out what is causing the constant > reads. When I run Process Monitor (Filemon) on the server, I > don't see anything that is hitting F: and causing the issue. > I'm guessing that process monitor is NOT showing me the > activity on F: from my networked PCs that are accessing the > user share on the F: drive. > > So.... Is there a way to find out what/who is causing my > disks to constantly be 100% Disk Read? > > I don't see anything outstanding under Open Files in Computer > Management either... > > Ideas? > > > -------------------------------------------------------------------- > myhosting.com - Premium MicrosoftR WindowsR and Linux web and > application hosting - http://link.myhosting.com/myhosting > > > > ~ Finally, powerful endpoint security that ISN'T a resource > hog! ~ ~ > <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
