07-06-2004
/ is full
Hi Exprts,
I faced this problem several times, which / file system is full (near 100%) and "proc" under that is the main reason.
i don't know how to reduce the size as all directories under proc seems important & other dir/files under / are OS related & could not be removed.
could anyone advise me for the possible solutions on making the / file system free.
Thanks,
--nikk
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi..
i am having a problem, for some reason my / directory is 100 % full.. and i didn't install or anything on it.. it has almost 2 gig on thr root directory.. maybe i am missing some concept because i do not understand why it get full. it is happening on all three of my system.. and i always... (9 Replies)
Discussion started by: souldier
9 Replies
2. Solaris
Dear All
I have a problem regarding my Solaris 8 OS . This is regarding the space available in my disk.
Although the df -k for /export/home shows 32% capacity I am not able to create any file on the disk.
Again, quot -af shows the same output . I have got directories in my /export/home but... (3 Replies)
Discussion started by: encrypted
3 Replies
3. UNIX for Advanced & Expert Users
Please solve the following
NOTICE HTFS:No space on dev hd(1/42) (2 Replies)
Discussion started by: msuheel
2 Replies
4. AIX
Hi everybody;
Javaecore files and heapdump created every day in my system in the "/" and make it full. Is there any way to disable this core files or change there directory from the "/" to "/tmp".
Note that AIX level is 5.2 with ML 6.
BeSt ReGaRs (0 Replies)
Discussion started by: khalifah
0 Replies
5. UNIX for Dummies Questions & Answers
Hi Everyone,
I think I've filled up one of the partitions on my drive. I suspect that one of the applications I've been running has been spitting out junk files to this partition - most of which can be deleted. The problem is that I have no idea how to go look at what's on that partition and... (2 Replies)
Discussion started by: Choppy
2 Replies
6. UNIX for Dummies Questions & Answers
my root filesystem is eventually full "/dev/rdsk/c1d0s0" as a result i cannot boot to the operating system, i booted into the fail safe mode to check the space using df -h command i discover that it is eventually full. Also to my amazement i found that i cannot see the filesystem which mounted on... (1 Reply)
Discussion started by: seyiisq
1 Replies
7. Shell Programming and Scripting
/Path/snowbird9/nrfCompMgrRave1230100920.log.gz:09/20/2010 06:14:51 ERROR Error Message.
/Path/snowbird6/nrfCompMgrRave1220100920.log.gz:09/20/2010 06:14:51 ERROR Error Message.
/Path/snowbird14/nrfCompMgrRave920100920.log.gz:09/20/2010 06:14:51 ERROR Error Message.... (0 Replies)
Discussion started by: Shirisha
0 Replies
8. Red Hat
/ has become full.... So i'm unable to login to the server. What should i do now ??
please help me... Thanks in advance (4 Replies)
Discussion started by: vamshigvk475
4 Replies
9. 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 REDHAT
slabinfo
SLABINFO(5) Linux manual SLABINFO(5)
NAME
/proc/slabinfo - Kernel slab allocator statistics
SYNOPSIS
cat /proc/slabinfo
DESCRIPTION
Frequently used objects in the Linux kernel (buffer heads, inodes, dentries, etc.) have their own cache. The file /proc/slabinfo gives
statistics. For example:
% cat /proc/slabinfo
slabinfo - version: 1.1
kmem_cache 60 78 100 2 2 1
blkdev_requests 5120 5120 96 128 128 1
mnt_cache 20 40 96 1 1 1
inode_cache 7005 14792 480 1598 1849 1
dentry_cache 5469 5880 128 183 196 1
filp 726 760 96 19 19 1
buffer_head 67131 71240 96 1776 1781 1
vm_area_struct 1204 1652 64 23 28 1
...
size-8192 1 17 8192 1 17 2
size-4096 41 73 4096 41 73 1
...
For each slab cache, the cache name, the number of currently active objects, the total number of available objects, the size of each object
in bytes, the number of pages with at least one active object, the total number of allocated pages, and the number of pages per slab are
given.
Note that because of object alignment and slab cache overhead, objects are not normally packed tightly into pages. Pages with even one in-
use object are considered in-use and cannot be freed.
Kernels compiled with slab cache statistics will also have "(statistics)" in the first line of output, and will have 5 additional columns,
namely: the high water mark of active objects; the number of times objects have been allocated; the number of times the cache has grown
(new pages added to this cache); the number of times the cache has been reaped (unused pages removed from this cache); and the number of
times there was an error allocating new pages to this cache. If slab cache statistics are not enabled for this kernel, these columns will
not be shown.
SMP systems will also have "(SMP)" in the first line of output, and will have two additional columns for each slab, reporting the slab
allocation policy for the CPU-local cache (to reduce the need for inter-CPU synchronization when allocating objects from the cache). The
first column is the per-CPU limit: the maximum number of objects that will be cached for each CPU. The second column is the batchcount:
the maximum number of free objects in the global cache that will be transferred to the per-CPU cache if it is empty, or the number of
objects to be returned to the global cache if the per-CPU cache is full.
If both slab cache statistics and SMP are defined, there will be four additional columns, reporting the per-CPU cache statistics. The
first two are the per-CPU cache allocation hit and miss counts: the number of times an object was or was not available in the per-CPU cache
for allocation. The next two are the per-CPU cache free hit and miss counts: the number of times a freed object could or could not fit
within the per-CPU cache limit, before flushing objects to the global cache.
It is possible to tune the SMP per-CPU slab cache limit and batchcount via:
echo "cache_name limit batchcount" > /proc/slabinfo
AVAILABILITY
/proc/slabinfo exists since Linux 2.1.23. SMP per-CPU caches exist since Linux 2.4.0-test3.
FILES
<linux/slab.h>
2001-06-19 SLABINFO(5)