if you had to double the default disk read timeout for CRS then your
disk read delay must be happening at a lower level of the stack then
the cluster services... possibly in the filesystem or kernel?
- how frequently does it happen?
- are you using OCFS or raw partitions? (there was a bug with an older
version of OCFS where an instance would totally hang in a 'D' disk wait
state under certain circumstances.)
- what brand and model of fireware drive are you using? (some firewire
chipsets don't support multiple-login and so only one machine can
access the drive at a time.)
just a few ideas off the top of my head...
Received on Sat Jun 11 2005 - 12:10:14 CDT
