Sponsored Content
Full Discussion: Dump Command in Linux
Top Forums UNIX for Dummies Questions & Answers Dump Command in Linux Post 9168 by syedifti on Tuesday 23rd of October 2001 01:25:20 PM
Old 10-23-2001
Dump Command in Linux

Can anybody tell me please how to use the "dump" command in Linux command.
dump -0u /destination /sourcefile or device file.
Please correct me.
-regards
-Iftikhar
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

dump command

For ufsdump you type in a "dump level". The man command mentions levels 0-9 and gives examples. Can anyone define what each level refers to? What does a level 0 dump mean? What is a level 9 dump? What are the differences? Thanks in advance:) (1 Reply)
Discussion started by: Patman
1 Replies

2. UNIX for Dummies Questions & Answers

dump command

Hi all, I am using embedded linux with my own RFS. But I want to use the dump command to try and solve some errors, but I don't know in wich package I can find the dump command. I hope someone can help me. With kind regards, Jurrian Dubbeldam (1 Reply)
Discussion started by: Jurrian
1 Replies

3. UNIX for Dummies Questions & Answers

dump command fault

im performing the dump command : dump 0uaf /dev/hdc /home an error msg appers says: DUMP: you cant update the dumpdates file while dumping a subdirectory DUMP: the entire dump is aborted can anyone help (6 Replies)
Discussion started by: semosam
6 Replies

4. UNIX for Dummies Questions & Answers

Trying to figure out a log dump command

Ok so i'm relatively new at UNIX and I'm trying to figure out how to make a log dump command. My situation is a bit odd in that I'm always looking at customers boxes and as such I can't really do much to them. So everything I do in UNIX pretty much has to be a command I can type in by hand. I... (4 Replies)
Discussion started by: MrEddy
4 Replies

5. UNIX for Dummies Questions & Answers

analyze linux crash dump

Can anybody let me know the steps how can I produce a crash dump and then analyze it? (4 Replies)
Discussion started by: rupeshkp728
4 Replies

6. Shell Programming and Scripting

Is there a command to close a program with dump?

I'm running into some problems using pkill in my scripts. I'm using a program that needs to dump. (4 Replies)
Discussion started by: ninjaaron
4 Replies

7. Emergency UNIX and Linux Support

How to open the core dump file in linux?

Hi, I have got core dump stating "core.bash.29846" so i am unable to open. How to open the core dump file for further analysis? Reagards Vanitha (7 Replies)
Discussion started by: vanitham
7 Replies

8. Linux

Thread specific data from linux core dump

How do i get pointer to thread's local storage or thread specific data while analyzing core dump for linux ? i use pthread_setspecific to store some data in the pthread's local stoare. my multi threaded program on linux crashed, and i want to see what is stored in current running thread's... (2 Replies)
Discussion started by: vishwasungal
2 Replies

9. UNIX for Dummies Questions & Answers

Learn Linux Core Dump Analysis

Can any body provide me some good link to learn to create and analyze linux user mode application / kernel module core dumps? (1 Reply)
Discussion started by: rupeshkp728
1 Replies

10. Red Hat

Core Dump of a process in Red Hat Linux 5.9

Hello All, I am new joiner of this forum.I am new to Linux shell scripting. At present I have identified 1 application which stalls very frequently (PID is say xyz) and I am not having much information in its application log to identify the root cause of stalling. I need to take the core dump... (19 Replies)
Discussion started by: Anjan Ganguly
19 Replies
crashutil(1M)															     crashutil(1M)

NAME
crashutil - manipulate crash dump data SYNOPSIS
version] source [destination] DESCRIPTION
copies and preserves crash dump data, and performs format conversions on it. Common uses of include: o Copying portions of a dump that still reside on a raw dump device into a crash dump directory. o Converting between different formats of crash dumps. o Copying crash dumps from one directory, or medium, to another. will write to its destination the crash dump it reads from its source. The crash dump format used to write the destination is specified with if is not specified, the destination will have the same format as the source. If no destination is specified, source is used; the format conversion will be done in place in the source, without copying. When completes successfully, the entire contents of the crash dump will exist at destination; any portions that had still been on raw dump devices will have been copied to destination. There are three known dump formats: (Version 0) This format, used up through HP-UX 10.01, consists of a single file containing the physical memory image, with a 1-to-1 cor- respondence between file offset and memory address. Normally there is an associated file containing the kernel image. sources or destinations of this type must be specified as two pathnames to plain files, separated by whitespace; the first is the core image file and the second is the kernel image file. (Version 1) This format, used in HP-UX 10.10, 10.20, and 10.30, consists of a directory containing an file, the kernel file, and numerous files, which contain portions of the physical memory image. sources or destinations of this type should be specified as the pathname to a core directory. (Version 2) This format, used in HP-UX 11.00 and later, consists of a directory containing an file, the kernel and all dynamically loaded kernel module files, and numerous files, each of which contain portions of the physical memory image and metadata describing which memory pages were dumped and which were not. sources or destinations of this type should be specified as the pathname to a crash directory. (Version 3) This format is used in HP-UX Release 11i Version 1.0 and later. It is very similar in structure to the format in that it consists of a directory containing an file, the kernel and all dynamically loaded kernel module files, and numerous files, each of which contain portions of the physical memory image and metadata describing which memory pages were dumped and which were not. In addition to the primary file, there are auxiliary index files, that contain metadata describing the image files containing the memory pages. This format will be used when the dump is compressed. See crashconf(1M). Other formats, for example tape archival formats, may be added in the future. When the source and destination are different types of files -- for example, when source is a directory and destination is a pair of plain files -- both must be specified. Options (Quiet) Disables the printing of progress messages. Warning and error messages are still printed. Specifies the version of the destination format. Allowed values are 0, 1, 2 or 3. Also allowed is the keyword which specifies that the destination format should be the same as the current source format. is the default if is not specified. If the destination format is then the source format should also be Conversion to from older formats is not supported. RETURN VALUE
Upon exit, returns the following values: 0 The operation was successful. 1 The operation failed, and an appropriate error message was printed. EXAMPLES
An HP-UX 11.00 crash dump was saved by savecrash(1M) to The flag was specified to savecrash, specifying that only those portions of the dump which were endangered by swap activity should be saved; the rest are still resident in the raw dump devices. To save the remainder of the dump into the crash dump directory, use: If preferred, the completed crash dump directory could be in a different location -- perhaps on another machine via NFS: To debug this crash dump using tools which do not understand the most current crash dump format, convert it to the older core directory format: or the even older "core file and kernel" format: AUTHOR
was developed by HP. SEE ALSO
savecrash(1M), crashconf(1M). crashutil(1M)
All times are GMT -4. The time now is 04:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy