Sponsored Content
Full Discussion: handling a coredump on HP?
Top Forums UNIX for Dummies Questions & Answers handling a coredump on HP? Post 302141060 by matrixmadhan on Wednesday 17th of October 2007 02:01:15 PM
Old 10-17-2007
surprising, why the redirection is not working here ?

I could see that you have used 2>&1 and both stdout and stderr to be redirected to the log file

Smilie
 

10 More Discussions You Might Find Interesting

1. Programming

coredump

i create one executed file (based on c language). when 1 try to executed the file, the result show me the bus error (coredump). can you help me to solve this problem. thanks. (2 Replies)
Discussion started by: lala
2 Replies

2. Solaris

Set Up Coredump's

I am trying to set up coredumps on a server, I have enabled the coreadm, and have also set a path to whre the coredumps will go. I now need to set the ulimit , as this is set to 0. I made the change: ulimit -c 8192 but when I logged out and back in, it was set back to 0 again. I need to know... (1 Reply)
Discussion started by: mzyvn6
1 Replies

3. Programming

Strncpy - coredump

haiu all what makes strncpy to coredump (0 Replies)
Discussion started by: vijaysabari
0 Replies

4. Solaris

metainit gives coredump

SunOS unknown 5.9 Generic_118558-10 sun4u sparc SUNW,Sun-Fire-880 I'm trying to set up mirroring and am running into a problem: As you can see, I set up the metadb, but am getting a coredump when running metainit. I saw this through google, but don't know the validity of it. Any ideas? #... (5 Replies)
Discussion started by: dangral
5 Replies

5. UNIX for Advanced & Expert Users

coredump after every reboot

Every time I reboot our solaris 9 (SunOS 5.9 Generic_118558-19 sun4u sparc SUNW,Sun-Fire-480R) box, I get the messages below: # dmesg | grep dump Mar 24 12:39:55 hostname savecore: initial dump header corrupt Mar 24 12:39:55 hostname genunix: dump on /dev/dsk/c1t0d0s1 size 700 MB Mar 24... (2 Replies)
Discussion started by: xnightcrawl
2 Replies

6. Red Hat

how to read coredump on RHEL

Hi All, I just wondering how can we read core files (core.****). I have an appication, when it is trying to crash I got the coredump. since it is in binary format, I dont know how to read that. Thanks (1 Reply)
Discussion started by: s_linux
1 Replies

7. HP-UX

Need help on Bus error(coredump)

Hi all, I am quite weak in C but I need to get some work done. Hope someone can help me out. I keep getting this error when i try to run my C application in my HP-UX 10.20 machine. Some code snippet: Month(DBTime) =====This is a function which will return variable "CutOffTime" to be use... (5 Replies)
Discussion started by: Vision©
5 Replies

8. AIX

coredump: xsnaadmin

Hello! I do have an IBM pSeries 7043 server running AIX 5.2.0.0. Well, I do have trouble to run xsnaadmin tool remotely, I mean, the xsnaadmin tool can't run on exported X display. What I'm doing is aixserver>export DISPLAY=xxx.xxx.xxx.xxx:0.0 aixserver>xsnaadmin Segmentation... (0 Replies)
Discussion started by: jssanche
0 Replies

9. Shell Programming and Scripting

bc throwing coredump

Hi Gurus, I tried bc 1000 % 10 on tcsh and ksh and its throwing a core dump on a sun solaris machine. uname -a SunOS azote 5.9 Generic_118558-39 sun4u sparc SUNW,Ultra-4 Please let me know if you find anything. Thanks, Kinny (8 Replies)
Discussion started by: kinny
8 Replies

10. HP-UX

Coredump HP-UX 11.23 and 11.31

Hi, I'm looking for the help on how to implement coredump using the tools that comes with HP-UX 11.23 and HP-UX 11.31. To also avoid the the dump files fill-up the root disk when dump occurs. I'm new to this and would need step by step please. Thanks in advance! (3 Replies)
Discussion started by: lamoul
3 Replies
xfs_metadump(8) 					      System Manager's Manual						   xfs_metadump(8)

NAME
xfs_metadump - copy XFS filesystem metadata to a file SYNOPSIS
xfs_metadump [ -efgow ] [ -l logdev ] source target DESCRIPTION
xfs_metadump is a debugging tool that copies the metadata from an XFS filesystem to a file. The source argument must be the pathname of the device or file containing the XFS filesystem and the target argument specifies the destination file name. If target is -, then the output is sent to stdout. This allows the output to be redirected to another program such as a compression application. xfs_metadump should only be used to copy unmounted filesystems, read-only mounted filesystems, or frozen filesystems (see xfs_freeze(8)). Otherwise, the generated dump could be inconsistent or corrupt. xfs_metadump does not alter the source filesystem in any way. The target image is a contiguous (non-sparse) file containing all the filesystem's metadata and indexes to where the blocks were copied from. By default, xfs_metadump obfuscates most file (regular file, directory and symbolic link) names and extended attribute names to allow the dumps to be sent without revealing confidential information. Extended attribute values are zeroed and no data is copied. The only excep- tions are file or attribute names that are 4 or less characters in length. Also file names that span extents (this can only occur with the mkfs.xfs(8) options where -n size > -b size) are not obfuscated. Names between 5 and 8 characters in length inclusively are partially obfuscated. xfs_metadump should not be used for any purposes other than for debugging and reporting filesystem problems. The most common usage scenario for this tool is when xfs_repair(8) fails to repair a filesystem and a metadump image can be sent for analysis. The file generated by xfs_metadump can be restored to filesystem image (minus the data) using the xfs_mdrestore(8) tool. OPTIONS
-e Stops the dump on a read error. Normally, it will ignore read errors and copy all the metadata that is accessible. -f Specifies that the filesystem image to be processed is stored in a regular file (see the mkfs.xfs -d file option). This can also happen if an image copy of a filesystem has been made into an ordinary file with xfs_copy(8). -g Shows dump progress. This is sent to stdout if the target is a file or to stderr if the target is stdout. -l logdev For filesystems which use an external log, this specifies the device where the external log resides. The external log is not copied, only internal logs are copied. -o Disables obfuscation of file names and extended attributes. -w Prints warnings of inconsistant metadata encountered to stderr. Bad metadata is still copied. DIAGNOSTICS
xfs_metadump returns an exit code of 0 if all readable metadata is succesfully copied or 1 if a write error occurs or a read error occurs and the -e option used. NOTES
As xfs_metadump copies metadata only, it does not matter if the source filesystem has a realtime section or not. If the filesystem has an external log, it is not copied. Internal logs are copied and any outstanding log transactions are not obfuscated if they contain names. xfs_metadump is a shell wrapper around the xfs_db(8) metadump command. SEE ALSO
xfs_repair(8), xfs_mdrestore(8), xfs_freeze(8), xfs_db(8), xfs_copy(8), xfs(5) BUGS
Email bug reports to xfs@oss.sgi.com. xfs_metadump(8)
All times are GMT -4. The time now is 05:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy