03-02-2006
Quote:
Originally Posted by RTM
First, don't do what
this person did
Next, look to see how your filesystems are laid out - is everything under / ? If you do a df -kl, what shows up?
If /var is not it's own partition, then you can look into /var/adm/ to see if there are files you can trim down - it's up to you to not delete something that is needed. Check /var/crash/`hostname` for any core files such as unix.xx and vmcore.xx (where xx is a number). These can be removed with no issues.
Check for core files in / - these are usually large and are caused when a application or program crashes and leaves a core file for diagnostics. Check when each was made (ls -l filename) and the type of file it is (file filename).
Thanks for your reply. It helped me a lot.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
what should i do in this situation. the system crashes and when it rebooted, it tries to dump the core files in the savecore directory. it finds that there is not enough space to dump the files so it just goes ahead and boots up and saves as much core as the directory can withhold
1.
now my... (1 Reply)
Discussion started by: TRUEST
1 Replies
2. UNIX for Dummies Questions & Answers
Is there a way of listing everything under a directory.
So for example if you wanted to know everything under the USR directory you would get all the sub directories and files in those directories as well as the file directly under the USR directory. I would imagine that you could do this... (5 Replies)
Discussion started by: B14speedfreak
5 Replies
3. Solaris
$ df -hl
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d0 9.8G 5.0G 4.7G 52% /
/proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
fd 0K 0K 0K ... (2 Replies)
Discussion started by: adel8483
2 Replies
4. HP-UX
I'm not a unix admin, just fell into support, so I may be asking a real duh question.
Client runs a PeopleSoft HR/Payrool system. The batch server runs in HPUX PA_RISC 11.11
When a batch process runs, output is written to "staging" directory. When the job finishes, successfully or not, the... (1 Reply)
Discussion started by: abNORMal
1 Replies
5. Solaris
root directory in server / is full 100% , i already tried to delete any core file , log , ..
still files under /proc directory take more than 4 G..
what you advice please i don't want to format the server and install again and re partition , i tried the FORMAT tools ! but it seems i cant do... (5 Replies)
Discussion started by: moata_u
5 Replies
6. AIX
Dear All,
We are on AIX OS, /tmp directory is filled up to 99% percent,
Please suggest, How to get free space for "/tmp"?
which files can be deleted from /tmp? and How to delete it? is there any commands.....
Thanks in advance,
Its very urgent, Helpful answers will be appreciated,
Please... (7 Replies)
Discussion started by: kak
7 Replies
7. UNIX for Dummies Questions & Answers
I think I know what this is doing, but the 'eval' is confusing
fname=$(echo ${lineItem} | awk 'BEGIN {FS=";"}{print $1}')
fname=${fname%%+(])}
fname=${fname##+(])}
eval "fname=${fname}"
The first line extracts the contents of the line preceeding the ";"
2nd & 3rd lines trim the value (I... (5 Replies)
Discussion started by: jdorn001
5 Replies
8. UNIX for Dummies Questions & Answers
I have a directory 97% full warning. I have deleted 2 large files and still get the error each time I sign on. Can anyone help me with what I have failed to do? Thanks in advance. Danny Corley (4 Replies)
Discussion started by: Danny Corley
4 Replies
9. UNIX for Dummies Questions & Answers
My input is as below :
/splunk/scrubbed/rebate/IFIND.REBTE.WROC.txt
/splunk/scrubbed/rebate/IFIND.REBTE.WROC.txt
/splunk/scrubbed/loyal/IFIND.HELLO.WROC.txt
/splunk/scrubbed/triumph/ifind.triumph.txt
From the above input I want to extract the file names only .
Basically I want to... (5 Replies)
Discussion started by: IshuGupta
5 Replies
10. AIX
AIX Version 6.1 and 7.1.
I understand that when the OS initially creates the FS and inodes, its pretty strict, but not always tuned to a 1:1 ratio. I see the same thing when adding a whole disk LV to a separate device.
It seems that when we expand a filesystem the inodes don't get tuned... (5 Replies)
Discussion started by: mrmurdock
5 Replies
LEARN ABOUT ULTRIX
savecore
savecore(8) System Manager's Manual savecore(8)
Name
savecore - save a core dump of the operating system
Syntax
/etc/savecore [ options ] dirname [ system ] [ corename ]
Description
The command is meant to be called near the end of the file. The command saves the core dump of the system (assuming one was made) and
writes a reboot message in the shutdown log.
The command checks the core dump to be certain it corresponds with the current running ULTRIX. If it does, it saves the core image in the
file dirname/vmcore.n and saves the namelist in the file dirname/vmunix.n. The trailing .n in the pathnames is replaced by a number which
increments each time is run in that directory.
After saving the core and namelist images, will save the error logger buffer into a predetermined file. The error logger buffer contains
information about why the crash occurred. After completes, the daemon will extract the error logger file and translate its contents into a
form familiar to the program.
Before writes out a core image, it reads a number from the file dirname/minfree. If there are fewer free blocks on the filesystem that
contains dirname than the number obtained from the file, a core dump is not done. If the file does not exist, savecore always writes out
the core file (assuming that a core dump was taken).
The command also writes a reboot message in the shut down log. If the system crashed as a result of a panic, also records the panic string
in the shut down log.
For partial crash dumps, creates a sparse core image file in dirname/vmcore.n. If this sparse core image file is copied or moved to
another location, the file expands to its true size which can take too much file system space. Hence, to copy or move sparse core image
files, you must use the command. The command has a conversion option to create sparse output files.
Options
-c Clears the core dump. This option is useful when the core dump is corrupted in a way that will not allow to save it safely. Use the
option with caution, because once it clears the core dump, the core dump cannot be retrieved.
-d dumpdev dumplo
Specifies the dump device and the dump offset when running on a system image other than the currently running system image. The pro-
gram assumes that the running system image is and it reads the dump device and dump device offset are different in the system image
that crashed, the option provides the correct dump device and dump device offset.
-e Saves only the error logger buffer into a file. If used, core or namelist images are not saved.
-f corename
Takes the i corefile name as the file from which to extract the the crash dump data instead of the default dump device. This option
is used only for diskless workstations.
If the core dump was from a system other than /vmunix, the name of that system must be supplied as system. The program assumes that the
running image is
After successful completion, the core dump is cleared. Also, a message is written in the file which tells whether the dump succeeded or
failed.
Files
Shut down log
Current running ULTRIX system
See Also
dd(1), uerf(8)
savecore(8)