Sponsored Content
Full Discussion: / directory is 100% full
Operating Systems Solaris / directory is 100% full Post 100047 by RTM on Thursday 23rd of February 2006 08:29:05 AM
Old 02-23-2006
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).
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Savecore directory is full, what can be done?

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

Full Directory Listing...

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

Full Directory without data....

$ 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

directory full?

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 is full

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

\tmp Directory is full up to 99%.

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

Extract directory from full file name?

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

Directory full error

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

Extract directory name from the full directory path in UNIX using shell scripting

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

100% Inode full with only 67% FS full.

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
KGDB(1) 						    BSD General Commands Manual 						   KGDB(1)

NAME
kgdb -- kernel debugger SYNOPSIS
kgdb [-a | -f | -fullname] [-b rate] [-q | -quiet] [-v] [-w] [-d crashdir] [-c core | -n dumpnr | -r device] [kernel [core]] DESCRIPTION
The kgdb utility is a debugger based on gdb(1) that allows debugging of kernel core files. The options are as follows: -a Increase the annotation level. An annotation level of 1 features the historical -fullname option of gdb(1). This is useful when running kgdb in Emacs. The -f or -fullname options are supported for backward compatibility as well. -b rate Set the baudrate to rate. -q Suppress printing of the banner when the debugger starts. The -quiet form is supported for compatibility as well. -v Increase verbosity. -w Opens kmem-based targets in read-write mode. (This is identical to what --wcore used to do in previous gdb versions for FreeBSD.) -d crashdir Use crashdir instead of the default, /var/crash to locate kernel core dump files in. The name vmcore. plus the dump number will be appended to determine the actual dump file name. -c core Explicitly use core as the core dump file. -n dumpnr Use the kernel core dump file numbered dumpnr for debugging. -r device Use device to connect kgdb to for a remote debugging session. The -c, -n, and -r options are mutually exclusive. Optionally, the name of the kernel symbol file and the name of the core dump file can be supplied on the command-line as positional argu- ments. If no kernel symbol file name has been given, the symbol file of the currently running kernel will be used. If no core dump file has been specified through either of the options or the last command-line argument, /dev/mem will be opened to allow debugging the currently run- ning kernel. FILES
/dev/mem Default memory image to open if no core dump file has been specified. /var/crash Default directory to locate kernel core dump files. SEE ALSO
gdb(1) HISTORY
The kgdb utility first appeared in its current form in FreeBSD 5.3. BSD
October 11, 2006 BSD
All times are GMT -4. The time now is 08:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy