07-06-2004
Type "df -k" and look at the result. Removing files in other filesystems won't help if / is full. You've got to remove stuff in the root filesystem. Note that /proc is a separate filesystem. That right there should tell you that looking at /proc is barking up the wrong tree. What's worse is trhat /proc consumes no disk space at all. It's a psuedo filesystem. Psuedo means make-believe. So ignore /proc and the other filesystems...if root is full, you've got to address that by looking at root.
If root has filled it's because someone wrote some files there. So a reasonable approach is to look at a recently written files in root...
find / -mount -mtime -10 -type f -print | xargs ls -l
The -mtime -10 says written to less than 10 days ago. You may need to adjust that.
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
tar(5) File Formats Manual tar(5)
Name
tar, mdtar - tape archive file format
Description
The tape archive command dumps several files, including special files, into one, in a medium suitable for transportation.
A tape or file is a series of blocks. Each block is of size TBLOCK. A file on the tape is represented by a header block, which describes
the file, followed by zero or more blocks, which give the contents of the file. At the end of the tape are two blocks filled with binary
zeros, as an end-of-file indicator.
The blocks are grouped for physical I/O operations. Each group of n blocks (where n is set by the option on the command line, and the
default is 20 blocks) is written with a single system call; on 9-track tapes, the result of this write is a single tape record. The last
group is always written at the full size, so blocks after the two zero blocks contain random data. On reading, the specified or default
group size is used for the first read, but if that read returns less than a full tape block, the reduced block size is used for further
reads.
The following is an example of a header block:
#define TBLOCK 512
#define NAMSIZ 100
union hblock {
char dummy[TBLOCK];
struct header {
char name[NAMSIZ];
char mode[8];
char uid[8];
char gid[8];
char size[12];
char mtime[12];
char chksum[8];
char linkflag;
char linkname[NAMSIZ];
char rdev[6]
} dbuf;
};
The name field is a null-terminated string. The other fields are 0-filled octal numbers in ASCII. Each field (of width w) contains w
minus 2 digits, a space, and a null, except size and mtime , which do not contain the trailing null. The name field specifies the name of
the file, as specified on the command line. Files dumped because they were in a directory that was named in the command line have the
directory name as prefix and /filename as suffix. The field specifies the file mode, with the top bit masked off. The uid and gid fields
specify the user and group numbers that own the file. The size field specifies the size of the file in bytes. Links and symbolic links
are dumped with this field specified as zero. The mtime field specifies the modification time of the file at the time it was dumped. The
chksum field is a decimal ASCII value, which represents the sum of all the bytes in the header block. When calculating the checksum, the
chksum field is treated as if it were all blanks. The linkflag field is ASCII 0 if the file is normal or a special file and ASCII 1 if it
is a hard link, and ASCII 2 if it is a symbolic link. The name to which it is linked, if any, is in linkname, with a trailing null.
Unused fields of the header are binary zeros and are included in the checksum. The rdev field encodes the ASCII representation of a device
special file's major and minor device numbers.
The first time a given i-node number is dumped, it is dumped as a regular file. The second and subsequent times, it is dumped as a link
instead. Upon retrieval, if a link entry is retrieved, but not the file it was linked to, an error message is printed and the tape must be
manually rescanned to retrieve the linked file.
The encoding of the header is designed to be portable across machines.
Restrictions
Names or link names longer than NAMSIZ produce error reports and cannot be dumped.
See Also
tar(1)
tar(5)