Hi all,
I only received one reply on my question (See below) and it was another
question. Our own investigation so far suggests, nothing. No idea. Nadda!
Our call to Compaq came back with "next time take a crash dump" and they
closed the call.
For those who don't know. If the machine hangs. Halt it with the reset
switch. at the "P0>>>" prompt type in "crash" then reboot normally. This
will create a crash dump file which can then be forwarded to Compaq for
analysis. As it was the other log files (/var/adm/messages,
/var/adm/binary.log and /var/adm/syslog.dated...) gave no indication as the
reason for the hang. The only advise from Compaq? Next time get a crash
dump.
So now we sit and wait. The only other thing to add is that since this seems
to happen on a reasonably regular basis, 3 times in the last 6 months, I
think we may just be able to get that crash dump for Compaq to analyse.
Thanks
Wayne Blom
Systems Specialist
F H Faulding & Co Limited
===========================================================================
Gidday True 64ers,
We have multiple DS10 clusters. Most running raid3000 but a couple are using
LSM instead. One of these last night appeared to freeze. At precisely the
same moment the cluster failed over to the 2nd node and the LSM software
began a complete resynch of the ase managed disks lasting 4 hours.
That is all the evidence I have of what transpired. We have logged a service
call with Compaq and also await their insight (pardon the pun).
The systems are running 4.0F with service pack 4. The ASE managed disks are
a pair of 18Gb disks in a mirror set. This system has done this a couple of
times now but this has been the least impacting as it happened at 2:18am.
Any thoughts or suggestions are welcome.
Thanks
Wayne S Blom
Systems Specialist
F H Faulding & Co Limited
Ph: +61 8 8408 3656
Fax: +61 8 8408 3357
Mob: +61 419 808 496
Received on Thu Jun 07 2001 - 01:23:51 NZST