09-09-2008
I have seen this type of problem after a reboot in the following circumstances (granted, it was Solaris, but the principle is the same):
1. Server is booted
2. A new filesystem is mounted, but not updated in vfstab
3. A utility to do some task (like cleanup) is called from the new filesystem
4. Server is rebooted
5. The filesystem is not mounted at boot time
6. The utility is called to perform the cleanup task - but there's nothing there.
7. The application crashes quietly, you end up with defunct processes.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
When I ps -ef I see about 3 or 4 <DEFUNCT> things - what are these, and what causes them? Are they a concern? How can I fix them?
Thanks,
Michael (4 Replies)
Discussion started by: cuppjr
4 Replies
2. Programming
how can i assure that daemon process which is being run as init child,can be removed immediately from system when it goes defunct or to avoid daemon process becoming defunt? (5 Replies)
Discussion started by: rish2005
5 Replies
3. Solaris
mqm 17700 16815 0 0:00 <defunct>
kill -9 does not work, even as root (10 Replies)
Discussion started by: csaunders
10 Replies
4. UNIX for Dummies Questions & Answers
Hey guys/gals. I am new to the site and fairly new to Unix/Linux. I have a master netbackup server (solaris) that I get pinged on occasionally regarding defunct processes. (Usually over 50 or so of them.) I know what a defunct process is, but what is it a product of? Just plain sloppy code? (From... (1 Reply)
Discussion started by: EMCSANMAN
1 Replies
5. UNIX for Dummies Questions & Answers
can some one please explain
zombie
orphan
defunct
and how they r related (3 Replies)
Discussion started by: pbsrinivas
3 Replies
6. Shell Programming and Scripting
Hi All,
Sorry to bother you all if my query is silly. Can you please clarify my doubts on defunct processes.
Actually coming to the scenario, i have a server which is under cluster environment. Server B is having problems with the defunct process. There was a cron scheduled on Server B which... (0 Replies)
Discussion started by: reddybs
0 Replies
7. HP-UX
Dear Sir / Madam,
We have two socket programs which are running in background. These two socket programs are creating defunct processes in HP-UX which were not happening in Compaq True64 UNIX. What is the root cause of these defunct processes and how can we correct it?
Your suggestion will be... (3 Replies)
Discussion started by: kcsahoo
3 Replies
8. UNIX for Advanced & Expert Users
HiI had a tool fail recently, on analysis I found it was cleaning up orphaned directories that had been created by specific processes that had died for some reason, thus failing to clean up after themselves.The directories were of the form /dir.pid. The tool would look to see if any instances of... (2 Replies)
Discussion started by: steadyonabix
2 Replies
9. HP-UX
I'd like to remove this defunct processes without rebooting. Or, I could remove this defuncts when the maximum allowable process is nearly reached, then send an email to the user/team. How can I determine the maximum allowable process that a server can handle? Any thoughts?
Jin@PRODUCTION: >... (3 Replies)
Discussion started by: Jin_
3 Replies
10. HP-UX
How to find out and clear the 'defunct' processes at OS and DB level ..?? (6 Replies)
Discussion started by: SurajR
6 Replies
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)