what should i do in this situation. the system crashes and when it rebooted, it tries to dump the core files in the savecore directory. it finds that there is not enough space to dump the files so it just goes ahead and boots up and saves as much core as the directory can withhold


1.
now my question is, what can be done to get the full original core files?? this happened to me a while ago and when i called SUn they said there is nothin they can do because its too late to generate the original full core files the system would have generated had it not been that the directory was full.


2.
another scenerio. say this system crashes, reboots and stops at the OK prompt. what is wrong with this command to type at the OK prompt:
savecore -L /var/crash/hostname/


3.
what command exactly is used to break out of a hung system? i keep hearing this STOP A thing but what buttons on the keyboard exactly is this??


any input is appreciated. please feel free to expatiate as much as you can. thank you

1.

Well, not enough space at /var/crash/<hostname> ...
Kinda complicated since the boot disk ain't well configured in the 1st place to aviod this scenario. (Might wanna read up on Sun BLUEPRINTS: Boot Disk Management to prevent such incident again)

For a fix, you might wanna use NFS mount to collect the crash dump. A centralized server to collect all the crash dump of the servers. Mind you, this will slow down the booting process due to network latency.


2.
I dun think you can use savecore at ok prom. You can use a sync; to force a crash dump. Or you wanna use a savecore -L after the server comes up to level 3.


3.
It is a button on SUN keyboard.