Problem in Reducing the root file system space
Hi All ,
The root file system is reached 86%. We have cleared 1 GB data in /var file system. But the root file system still showing 86%. Please note that the /var file is not seprate file system.
I have furnished the df -h output for your reference. Please provide solution as soon as possible.
/dev/dsk/c1t0d0s02.9G2.4G404M86%/
/devices0K0K0K0%/devices
ctfs 0K0K0K0%/system/contract
proc 0K0K0K0%/proc
mnttab0K0K0K0%/etc/mnttab
swap30G1.0M30G1%/etc/svc/volatile
objfs0K0K0K0%/system/object
/dev/dsk/c1t0d0s36.7G3.7G3.0G56%/usr
/platform/SUNW,Sun-Fire-T200/lib/libc_psr/libc_psr_hwcap1.so.1
2.9G2.4G404M86%/platform/sun4v/lib/libc_psr.so.1
/platform/SUNW,Sun-Fire-T200/lib/sparcv9/libc_psr/libc_psr_hwcap1.so.1
2.9G2.4G404M86%/platform/sun4v/lib/sparcv9/libc_psr.so.1
fd0K0K0K0%/dev/fd
swap33G3.5G30G11%/tmp
swap30G48K30G1%/var/run
/dev/dsk/c1t0d0s445G30G15G67%/www
/dev/dsk/c1t0d0s52.9G1.1G1.7G39%/export/home
Regards,
R. Rajesh Kannan.
[1070 byte] By [
grkrajesha] at [2007-11-26 20:07:53]
# 1
> Hi All ,
>
> The root file system is reached 86%. We have cleared
> 1 GB data in /var file system. But the root file
> system still showing 86%. Please note that the /var
> file is not seprate file system.
Perhaps you ran 'rm' on an open file (like a log file still in use). If you did that, then you didn't actually remove the file, you just removed its name from the directory.
The file will not be deleted until the program that still is using the file closes the file or exits.
Don't remove in-use files and expect to get the space back. This is a very common issue.
If this has occured, you can run 'df -k /' and 'du -sdk /' and you will get different figures. (df will account for the files on disk, but du will not be able to since they are no longer in a directory).
--
Darren
# 3
I don't know if the root partition filling up was sudden, and thus due to the killing of an in-use file, or some other problem. However, I have noticed that VAST amounts of space is used up just through the normal patching process.
After I installed Sol 10 11/06, my 12GB root partition was 48% full. Now, about 2 months later, after applying available patches, it is 53% full. That is about 600 MB being taken up by the superseded versions of the installed patches. This is ridiculous. I have patched using Sun Update Manager, which by default does not use the patchadd -d option that would not back up old patch versions, so the superseded patches are building up in /var, wasting massive amounts of space.
Are Solaris users just supposed to put up with this, or is there some other way we should manage patches? It is time consuming and dangerous to manually clean up the old patch versions by using patchrm to delete all versions of a patch and then using patchadd to re-install only the latest revision.
Thank you.
# 4
Hi Darren ,
Exactly, What you mentioned is happened in my environment.
I have removed the /var/adm/wtmpx file. This file occupied 800 MB of space. So, I have removed. After removing this file, the space of / file system not reduced.
I have furnished the the df -kh and du -sdkh output for your reference.
root@STAR:/var/tmp -> df -kh /
Filesystem size used avail capacity Mounted on
/dev/dsk/c1t0d0s0 2.9G 2.4G 382M 87% /
root@STAR:/var/tmp -> du -sdkh /
1.4G
How to bring back the root file system to 1.4 G
Regards,
R. Rajesh Kannan.
