/ full hidden files?

[F Verschuren]

hy, i have a problem whit my root filesytem,
it is now 95 % full:
/dev/vg00/lvol3 262144 248568 13568 95% /
dut if I do a
find . -xdev -type f -exec ll
and sum $5 than I only have 154503118 k files in / used.

I think there is ore a proces alocating space on a file that is removed ore that there is someting under a mountpoint.

Is there a way to see what is under a mount point whitout umount the filesytem?

[Robert-Jan Goossens]

Hi Freek,

Could you post the output of

# cd /
# du -kx / | sort -rn | head -20

--
Is there a way to see what is under a mount point whitout umount the filesytem?
--
Not without booting from cdrom, / is mounted in single user mode.

Regards,
Robert-Jan

[Devender Khatana]

Hi,

You should try this by rebooting in single user mode. Here applications shall not be running & you should be able to see the actual usage.

HTH,
Devender

[Yew Lee · Accepted solution]

Hi Freek, you can try the "/usr/sbin/ff" command. It will list the files and inodes, even if it is underneath a mount point.

In case you are interested in finding out which process is holding on to a deleted file, you can try the "lsof" utility. You should be able to get a copy of "lsof" from http://hpux.connect.org.uk.

[F Verschuren]

100480 /
62384 /etc
37672 /sbin
26696 /etc/vx
21656 /etc/vx/type
11848 /etc/opt
10952 /etc/lp
9968 /etc/lp/interface
9176 /etc/opt/resmon
8616 /etc/vx/type/static
8032 /etc/lp/interface/model.orig
7552 /etc/opt/resmon/lbin
7472 /etc/lvmconf
6344 /etc/vx/type/gen
5904 /sbin/fs
5120 /etc/vx/type/raid5
4008 /etc/vx/static.d
3496 /sbin/fs/vxfs
3296 /etc/vx/static.d/build
1768 /sbin/fs/hfs

[F Verschuren]

hy the ff dit the Jop I have fount some files that where under a mount point.
tanks.

[Greg OBarr]

1) If you're printing off this box, check /var/spool/lp/request, or just do a du -s on /var/spool/lp. It shouldn't be that large.

2) Also, check in /dev for files that may have been intended for a tape device, but the command was fat-fingered and it created a tar file there instead.

3) Finally, I would look for core files using:

find / -depth -type f -name core