[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 479
  • Last Modified:

novell current disk requests constantly 1 slows whole network

We run a novell 4.1 mirrored servers which i know nothing about the guy that used to fix any problems i had has vanished.
Everything was working fine untill all of a sudden even when they are the only machines turned on the "Current disk requests" is permanently on 1 and the CPU is madly fluctuating betwen 30 to 70 % utilization and then the whole network grinds to a halt.
I have tried to find a pattern but haven't as yet.
If i restart the the servers it can be okay for a while but not sure what triggers it.
What confuses me is what would the constant 1 "Current Disk Request" be
Also the hard drives lights on both the pairs are flahing away madly but what are they doing ?
0
dataclub
Asked:
dataclub
  • 2
1 Solution
 
maquesCommented:
To check:
1) type "mirror status" to see it it is mirrorring. If it does, it displays the percentage. It should finish eventually then.
2) in monitor (load monitor), check "disk information" / select disk / press "tab" - to see "redirected blocks" (note: no "redirect-ION but redirect-ED". If it is not zero, then the disk has bad blocks and need to be replaced. You should have at least 2 harddisk at disk information menu, check all harddisk devices for this (eg.: exclude cdrom, dat, etc.)
0
 
dataclubAuthor Commented:
I checked both disks and both of their "Redirected blocks" was zero.
I carried on trying things last night and i changed the "Minimum directory cache buffers" from 2500 to 500 and all seems to be working fine now the network is really fast again and there is no permanent "Current disk request" and the CPU Utilization is anywhere from 4% upwards basically just jumping about instead of being permanetly high.
Could this mean that with high directory cache buffers the machine is struggling for memory?
0
 
maquesCommented:
There are several other memory/disk related settings also.
Buffers just means that disk requests are delayed a bit until they are filled.
If you have some "bad" sitiuation, they fill up eventually and you're at the same situation again.
We might need more information, such as:
Memory, harddsiks (scsi/ata) and drivers.
Also what was the "mirroring" state?
Maybe it was mirroring, and now it is finished - that's why it is so much better. You can check sys:system/sys$log.err for mirroring related entries. The time between the start and the finish and the size of your harddisk might give us more information on this (if related to it).
0
 
Computer101Commented:
PAQed with points refunded (500)

Computer101
EE Admin
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now