| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4343.1 | | PROXY::J_EVANS | | Thu Jan 23 1997 08:52 | 5 |
| 4343.2 | Error log ? Crash dump ? External cabling ? | BBPBV1::WALLACE | john wallace @ bbp. +44 860 675093 | Fri Jan 24 1997 08:51 | 11 |
| Is anything interesting in the error log ?
Are you able to force a crash dump from console mode when the machine
is hung ?
If you're not using the TK50, remove it, terminate the bus at the
system unit, and see if the behaviour is the same. If you are using it,
live without it for a while?
regards
john
|
| 4343.3 | More info needed... | CRLRFR::BLUNT | | Sat Jan 25 1997 19:30 | 11 |
|
What are the EXACT commands that they are issuing to perform the
Backup? Has their disk been Analyzed recently? Do they have either
DECps or a defragger tool available on the system? Has the customer
taken a look at a $DUMP/FOR/HEAD/BLOCK=COUNT=0 FILENAME.EXT? Are they
"forcing" a crash when the system hangs? If not, they probably should,
and then get a copy of the crash dump on tape for evaluation.
I recall a problem with EXTREMELY fragmented disks a long time ago
(something around V3 of VMS) that failed in just the same way.
bob
|
| 4343.4 | Additional Checks... | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Mon Jan 27 1997 11:10 | 16 |
|
In addition to the other questions and the requests for copies of a
crashdump taken during the hang...
How long is the DAT tape? (The TLZ06 works with DAT tapes of lengths
no longer than 90M, maximum.)
I'll assume you've reviewed the minimum BACKUP quotas listed in the
System Management manual. (The list of quotas in .0 is incomplete,
and a few of the values shown in .0 are lower than recommended...)
You'll also want to look for pagefile warning messages and any other
messages that might appear on the system console or in the error log
during the hang, and you'll want to consider an AUTOGEN with FEEDBACK,
after cleaning out any cruft in MODPARAMS.
|
| 4343.5 | misinformation problem | ZPOVC::DAIVC::HERU | | Sun Feb 02 1997 22:04 | 17 |
|
Hello Team ...
Thank you for your replys to my problem. Just the moment I got an information from
my customer that their machine was not hang when doing backup (all user still can access),
but the DAT drive's LED blinking for very long time (more than the time needed for -
+/- 800000 block). In this situation, the user couldn't cancel backup process, so they
need to restart the system. I am sorry for misinformation.
I have already delivered the external DAT drive TLZ06-DA to my customer for temporrary
action, until they send the e-mail for detail information.
I will inform you in this topic for the next progress if there is an interresting log.
Regards,
Heru::daivc
|
| 4343.6 | Still Need Info... | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Mon Feb 03 1997 10:51 | 38 |
|
We still need the BACKUP commands and the other requested info...
How did the customer attempt to stop the process? Did the customer
attempt <CTRL/Y>, or STOP/ID, etc?
When the customer restarted the system, did they take a crash dump?
(If not -- when they next find themselves in this state -- please
show them how to take a crash dump...)
Note 4343.5 reformatted to 80 columns...
: <<< Note 4343.5 by ZPOVC::DAIVC::HERU >>>
: -< misinformation problem >-
:
:
:
: Hello Team ...
:
: Thank you for your replys to my problem. Just the moment I got an
: information from my customer that their machine was not hang when
: doing backup (all user still can access), but the DAT drive's LED
: blinking for very long time (more than the time needed for +/- 800000
: block). In this situation, the user couldn't cancel backup process,
: so they need to restart the system. I am sorry for misinformation.
:
: I have already delivered the external DAT drive TLZ06-DA to my
: customer for temporrary action, until they send the e-mail for detail
: information.
:
: I will inform you in this topic for the next progress if there is an
: interresting log.
:
: Regards,
:
: Heru::daivc
|