File server _ problem

[RichB]

Please take a look at this log:

 

Running server 2003, both file servers look like this, we are having speed issues when accessing files. Both servers are hitting 100% on disk, and sometimes processor. There is over 140 gig spare on a 1.5TB drive.

 

Any ideas whats wrong? how to combat it?>

 

Thanks

[round2it]

Please take a look at this log:

 

Running server 2003, both file servers look like this, we are having speed issues when accessing files. Both servers are hitting 100% on disk, and sometimes processor. There is over 140 gig spare on a 1.5TB drive.

 

Any ideas whats wrong? how to combat it?>

 

Thanks[ATTACH=CONFIG]11601[/ATTACH]

 

try looking at your switches

we had this and it was a faulty core switch

 

and also check the nic cards they might be on the way out

[zag]

Check the anti virus, that normally causes things like this.

[steveg]

Are you sure the server is not just underspecced / over used? How many people do you have accessing it, what type of drives are they in the server?

 

Before I put a new server in at one of my schools it would look exactly like this when they tried to do video editing in the IT suite off of the network drives.

 

Steve

[PeterW]

How many disks are in the RAID set and is it a hardware or software raid controller?

[RichB]

Sorry in the late reply! the antivirus is not the problem, and we have checked the switches! the raid is hardware based. It is something to do with the DFS roots we use here, on the preformance manager DFS connections are smashing at 100% all day, everyday! something is not getting through, ill check and update the NIC cards, then look at someother things!

[ryanmwalker06]

you sure its not your av rich scanning on read write and rename had this at my last place after i worked with you. and that was the only issue i could find

 

 

ryan

[Geoff]

Are you using DFS replication?

[RichB]

Yes using DFS rep! 100% not the anti virus when we upgraded the AV it was not on any machine in the college for 1 hour and we still had the issue. Since then we've disabled for testing and still get the issue

[Geoff]

Ok, your replication is broken. Check for errors in the event log.

[Michael]

Looking at your performance chart, your system memory peaked at 100% which is not good. This'll bring any server to a crawl.

 

I would agree with the above that replication could be broken. If the server's a DC, you could also check DNS is replicating correctly too.