06-11-2012
Can you reboot the computer? This will clear any files which have been deleted while they were still open by a process.
Also check the root directory itself visually and look for rogue large files:
ls -ald /* | more
Last edited by methyl; 06-11-2012 at 07:46 PM..
8 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi
I have a Solaris 2.5.1 system. Recently my file system is full and i couldn't find what flood my root file system.
Anyone can suggext any directories i should look out for.
I am using Samba and Patrol agent. I am just usng this server as a file server, users cannot login into the system,... (1 Reply)
Discussion started by: owls
1 Replies
2. Linux
hi
in my server ( / ) root filesystem size is full how to reduce the size and what are the files i want to remove.
i need answer for linux and AIX also. (6 Replies)
Discussion started by: chomca
6 Replies
3. AIX
Hello
On AIX 5, In a file system - I see no big files but still df shows no space available. What is tricky here?
Filesystem GB blocks Free %Used Iused %Iused Mounted on
/dev/fslv10 20.00 6.11 70% 2167 1% /data/d2
I have calculated all files conumption under... (3 Replies)
Discussion started by: panchpan
3 Replies
4. 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
5. UNIX for Advanced & Expert Users
I was tryin to copy a large file under /tmp location.
I guess the disk space got full and i got fork error.
Then I tried removing some files but the shell did not let me do anything
bash> rm apache22.tar
bash: fork: Not enough space
bash> pwd
/tmp
bash> vmstat 1
bash: fork: Not... (3 Replies)
Discussion started by: mohtashims
3 Replies
6. Solaris
hi guys..
how to give root permission for particular user
tel me step by step (2 Replies)
Discussion started by: coolboys
2 Replies
7. Emergency UNIX and Linux Support
Hello,
This is RHEL 5.7. swap is almost full, but I am not sure, what to release and how to release space. This is production server so I would like to try all possible options before reboot.
# top
top - 00:18:26 up 327 days, 7:01, 3 users, load average: 0.16, 0.21, 0.18
Tasks: 782 total, ... (7 Replies)
Discussion started by: solaris_1977
7 Replies
8. Red Hat
For instance, root partition is full so I don't need to know about /ABC/XYZ when /ABC/XYZ is a separate mount point. (But /ABC isnt).
Can I run a du command or similar and just look at contents effecting the space on that mount point (/)? (2 Replies)
Discussion started by: psychocandy
2 Replies
FSCK(1) General Commands Manual FSCK(1)
NAME
fsck, fsck1 - perform file system consistency check
SYNOPSIS
fsck [-aclmrs] [device] ...
OPTIONS
-a Automatically repair inconsistencies
-c Check and list only the specified i-nodes
-l List the files and directories in the filesytem
-r Prompt user for repairs if inconsistencies are found
-s List the superblock of the file system
EXAMPLES
fsck /dev/hd4 # Check file system on /dev/hd4
fsck -a /dev/at0 # Automatically fix errors on /dev/at0
fsck -l /dev/fd0 # List the contents of /dev/fd0
fsck -c 2 3 /dev/hd3
# Check and list /dev/hd3 i-nodes 2 & 3
DESCRIPTION
Fsck performs consistency checks on the file systems which reside on the specified devices. Fsck1 is an alternate version for use on obso-
lete V1 file systems. When either the -a or -r flags are given, the file system will be repaired if errors are found. Before running fsck
on a mounted file system, it must first be unmounted. Trying to repair a mounted file system is dangerous and should not be attempted.
To repair the root file system (which cannot be unmounted), first type CTRL-F9 at the console to kill any and all processes. Log back in
as root, type sync to force any buffered changes to disk, run fsck on the root file system and immediately reboot the computer by typing
reboot.
It is necessary to kill all processes before repairing the root file system to prevent them from modifying any disk blocks while fsck is
running. This is only necessary for the root file system, any other file system can simply be unmounted before it is checked.
SEE ALSO
mkfs(1), mount(1).
FSCK(1)