Re: which .DMP files to keep?



In article <xc6dnTmntPEU1qHUnZ2dnUVZ_hadnZ2d@xxxxxxxxxxxx>, rgilbert88
@comcast.net says...>
Phillip Helbig---remove CLOTHES to reply wrote:
Since I've been doing so much other maintenance work and since some
system disks could use a bit more free space, I'm thinking about
deleting non-needed big files from the system disk, in particular dump
files.

There are some files, of course, which should remain in place. Others
are produced when some application crashes, but if one isn't interested
in the analysis of that problem, then they are no longer needed.

Some should obviously be kept; some can obviously be deleted. Some I'm
not 100% sure about. If the space will be re-used when the same
application crashes again, then I might as well leave them there.

Which of the following would folks here recommend a) keeping in any case
and b) deleting in any case?

ERRORLOG.DMP
JBC$JOB_CONTROL.DMP
OPCOM.DMP
SMISERVER.DMP
SYS$ERRLOG.DMP
**************

SYSDUMP-COMMON.DMP
******************

SYSDUMP.DMP
TCPIP$SMTP_SYMBIONT.DMP
UCX$SMTP_SYMBIONT.DMP


If you don't anticipate a use for any of these files, you might as well
delete all but SYSDUMP.DMP. I'm assuming that's SYS$SYSTEM:SYSDUMP.DMP
or at least the dump file you have configured for use if your system
ever crashes. If your system crashes, you will probably wish to analyze
the dump or have HP support do so. Without the dump file, you might
never know why the system crashed. Maybe the crash was a one time
thing. . . . I wouldn't want to bet on it.

One of the joys of VMS is the rarity of crashes but if it does crash, it
will probably crash again, and again until you find the cause and
eliminate it.

sysdump-common.dmp is probably an alias for each nodes'
[sysN.sysexe]sysdump.dmp

Verify this by doing a directory/file_id on them.

If so, *DON'T* *DELETE* *IT*. (There, I hope I shouted loud enough.)

sys$errlog.dmp (assuming it's in sys$system:) is used by VMS to
preserver error log entries during a shutdown or crash. Don't delete
it, either. (If you do delete it or sysdump.dmp, it won't actually
go away until you reboot, at which time they will become lost files,
and still won't go away until you do analyze/disk/repair, but you'll
have lost the crash dump capability, which is probably a bad idea.)



--
John
.



Relevant Pages

  • Re: ADAM crashing
    ... So after it crashes, it might write off a file user.dmp on your system. ... If it's when you last observed a crash, I'd like to check out that dump ... >> rights. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Continuing crashes are driving me nuts!
    ... Windows doesn't even seem to know that a major crash ... How to configure system failure and recovery options in Windows ... No BSOD or memory dump occurs. ... even though Windows was set to generate minidumps on hard crashes. ...
    (microsoft.public.win2000.general)
  • Re: Run Time Error 216
    ... The Case of the Random IE and WMP Crashes ... Crashes go by default into %LOCALAPPDATA%\Crashdumps, but you can override that with a Registry value and also specify a limit on the number of crashes WerFault will keep. ... Read the above; create the crash dump settings you prefer; post back with the dump. ...
    (microsoft.public.windows.vista.security)
  • Re: SetUnhandledExceptionFilter
    ... The only way to prevent at all cost a crash in the applicaiton ... Looking at a full dump of Word.exe and/or LotusNotes is the only way ... A bad heap metadata will cause an access violation, ... normally dismissed in some wide exception handler) ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Crash with recent kernel on wireless
    ... You should use the kernel image with the debugging symbols here. ... Dump Length: 190091264B ... pointer. ... Most of crashes even failed to save vmdump due to double faults. ...
    (freebsd-stable)