[conandor]

i du -hd on the root directory and it came back show the / use only 4.2G
but df showing me i have 16G of space and its almost fully use
where is the rest of the space go to if it is not in / ?

here part of the screenshot

bash-3.00$ du -hd /
.
.
.
79M ./export/home/mydirec
137M ./export/home
137M ./export
1K ./vol
4.2G .
bash-3.00$ df -ah
Filesystem size used avail capacity Mounted on
/dev/dsk/c0t0d0s0 16G 15G 518M 97% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 813M 992K 812M 1% /etc/svc/volatile
objfs 0K 0K 0K 0% /system/object
fd 0K 0K 0K 0% /dev/fd
swap 512M 4.8M 507M 1% /tmp
swap 812M 24K 812M 1% /var/run
bash-3.00$ pwd
/
bash-3.00$

[kazler]

I have had something similar to this before where some one had tried to zip up a log file while it was still in use e.g. apache access log, the problem occurs as the inodes still exist on the drive for the log file even though it has been zipped up and a new log spawned. A quick fix is to reboot if a reboot is a no no then you could run lsof which will list open files and look for any thing suspicious and restart that app which makes the suspicious file or possibly delete the file. The drive could also just be calculating wrong due to corruption which is a bit tricky as it is the root partition, you could boot a live cd and run fsck on the partition and see what it finds (dont do this while it is mounted though as it could lead to data loss).

[jayd512]

Hi, conandor! Welcome to LinuxForums!

Do this:

fdisk -l

Post output here.

[HROAdmin26]

It's Solaris/OpenSolaris - there is no lsof or fdisk command.

[jayd512]

Oops... didn't realize