coredump: xsnaadmin

10 More Discussions You Might Find Interesting

1. Programming

Why segmentation(coredump) in the following code in C?

hi I have a method which returns char*. In this method am using switch case. I am getting segmentation error in case 49 and my code is case 49: if(intFlag == 0210) { iiIDCode = atoi(getsubstring(sReq,262,2)); l =...

2. 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. 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

4. 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

5. UNIX for Dummies Questions & Answers

handling a coredump on HP?

This works for all my normal executions. But on one machine, a coredump is expected on one command. We don't care and know it will always happen, but need to confirm the version info from the start of the output. This is output from the exe: $ ./Up -*-*- XXXXXXX UPDATE XXXXX Version...

6. 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...

7. 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? #...

8. Programming

Strncpy - coredump

haiu all what makes strncpy to coredump

9. 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...

10. 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.

LEARN ABOUT CENTOS

gfs2_grow

gfs2_grow(8)						      System Manager's Manual						      gfs2_grow(8)

NAME

       gfs2_grow - Expand a GFS2 filesystem

SYNOPSIS

       gfs2_grow [OPTION]... <DEVICE|MOUNTPOINT>...

DESCRIPTION

       gfs2_grow  is  used  to	expand	a  GFS2  filesystem after the device upon which the filesystem resides has also been expanded.	By running
       gfs2_grow on a GFS2 filesystem, you are requesting that any spare space between the current end of the filesystem and the end of the device
       is filled with a newly initialized GFS2 filesystem extension.  When this operation is complete, the resource group index for the filesystem
       is updated so that all nodes in the cluster can use the extra storage space that has been added.

       You may only run gfs2_grow on a mounted filesystem; expansion of unmounted filesystems is not supported.  You only need to run gfs2_grow on
       one node in the cluster.  All the other nodes will see the expansion has occurred and automatically start to use the newly available space.

       You must be superuser to execute gfs2_grow.  The gfs2_grow tool tries to prevent you from corrupting your filesystem by checking as many of
       the likely problems as it can.  When expanding a filesystem, only the last step of  updating  the  resource  index  affects  the  currently
       mounted filesystem and so failure part way through the expansion process should leave your filesystem in its original unexpanded state.

       You can run gfs2_grow with the -T flag to get a display of the current state of a mounted GFS2 filesystem.

       The  gfs2_grow  tool  uses  the	resource  group  (RG) size that was originally calculated when mkfs.gfs2 was done.  This allows tools like
       fsck.gfs2 to better ensure the integrity of the file system.  Since the new free space often does not lie on even boundaries based on  that
       RG size, there may be some unused space on the device after gfs2_grow is run.

OPTIONS

       -D     Print out debugging information about the filesystem layout.

       -h     Prints out a short usage message and exits.

       -q     Be quiet.  Don't print anything.

       -T     Test. Do all calculations, but do not write any data to the disk and do not expand the filesystem. This is used to discover what the
	      tool would have done were it run without this flag.

       -V     Version. Print out version information, then exit.

BUGS

       There is no way to shrink a GFS2 filesystem.

SEE ALSO

       mkfs.gfs2(8) gfs2_jadd(8)

																      gfs2_grow(8)

AIX