FreeBSD 6.2-RELEASE-p4

I have a problem with a partition that is full fsck -Bfy provided no results and I cannot seem to track down what is taking up the space as of three weeks ago for an entire year this partition was fine. It just popped up.

/dev/ad0s1a 1.9G 1.9G -157M 109% /
devfs 1.0K 1.0K 0B 100% /dev
/dev/ad0s1h 48G 14G 30G 33% /home
/dev/ad0s1d 1.9G 130K 1.8G 0% /tmp
/dev/ad0s1e 9.7G 4.0G 4.9G 45% /usr
/dev/ad0s1f 9.7G 2.1G 6.8G 24% /var
devfs 1.0K 1.0K 0B 100% /var/named/dev
procfs 4.0K 4.0K 0B 100% /proc
/dev/ad3s1d 108G 31G 68G 32% /drive2

Ive checked out the filesystem to see if I could find out what was wrong

912K /bin/
68M /boot
0B /compat
1.5K /dev
2.7M /etc
2.3M /etc.good
3.5M /lib
158K /libexec
2.0K /media
2.0K /mnt
4.0K /nonexistent
2.0K /opt
2.0K /perl
0B /proc
3.2M /rescue
17M /root
3.5M /sbin
5.6M /scripts
0B /sys

du -ch -d 1
2.0K ./.snap
1.5K ./dev
14G ./home
138K ./tmp
3.9G ./usr
2.1G ./var
5.7M ./scripts
2.7M ./etc
912K ./bin
68M ./boot
3.5M ./lib
158K ./libexec
2.0K ./media
2.0K ./mnt
0B ./proc
3.2M ./rescue
1.2M ./root
3.5M ./sbin
4.0K ./nonexistent
2.3M ./etc.good
2.0K ./perl
2.0K ./opt
31G ./drive2
52G .
52G total

du -xh -d 2 /| grep M
2.1M /scripts/cPScript
5.7M /scripts
2.7M /etc
22M /boot/kernel
22M /boot/kernel.good
22M /boot/kernel.old
68M /boot
3.5M /lib
3.2M /rescue
200K /root/.MirrorSearch
16M /root
3.5M /sbin
2.3M /etc.good
106M /

no drive errors
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 16837 -
# 2 Short offline Completed without error 00% 16836 -
# 3 Short offline Completed without error 00% 0 -


What am I overlooking here

What does this show?

# find -x / -size +20M

arch# find -x / -size +20M
arch#

I wouldn't expect that -- especially since you have three files under /boot that are > 20MB.

Is it possible df is giving bogus information? i.e. Can you create a new file on the / filesystem?

Cannot write to `86random-f1.1.gif' (No space left on device).

/boot is 68 megs btw
arch# du -sh /boot
68M /boot

Strange problem.

# ls -Slra /

(Sort listing from smallest to largest, show hidden files, etc.)

Maybe a hidden file?? i.e. /.some-core-dump

arch# ls -Slra /
total 119
-rw-r--r-- 1 root wheel 0 Jun 17 20:01 te~#e
dr-xr-xr-x 1 root wheel 0 Jun 25 14:13 proc
lrwxr-xr-x 1 root wheel 10 May 23 2007 compat -> usr/compat
lrwxrwxrwx 1 root wheel 11 May 23 2007 sys -> usr/src/sys
-rw-r--r-- 2 root wheel 251 Jan 12 2007 .profile
drwxr-xr-x 26 root wheel 512 Jun 22 02:13 var
drwxr-xr-x 19 root wheel 512 May 28 2007 usr
drwxr-xr-x 2 root wheel 512 Jun 13 2007 perl
drwxr-xr-x 2 root wheel 512 Oct 14 2007 opt
drwxr-xr-x 2 root wheel 512 May 25 2007 nonexistent
drwxr-xr-x 2 root wheel 512 Jan 12 2007 mnt
drwxr-xr-x 2 root wheel 512 Jan 12 2007 media
drwxr-xr-x 2 root wheel 512 May 23 2007 libexec
drwx--x--x 5 poker poker 512 Jun 24 08:12 drive2
dr-xr-xr-x 4 root wheel 512 Dec 31 1969 dev
drwxr-xr-x 7 root wheel 512 Oct 10 2007 boot
drwxrwxr-x 2 root operator 512 May 23 2007 .snap
-rw-r--r-- 2 root wheel 801 Jan 12 2007 .cshrc
drwxr-xr-x 9 root wheel 1024 Jun 25 14:13 root
drwxr-xr-x 3 root wheel 1024 May 23 2007 lib
drwxrwxrwx 42 root wheel 1024 Jun 4 03:26 home
drwxr-xr-x 2 root wheel 1024 May 23 2007 bin
drwxr-xr-x 25 root wheel 1024 Jun 25 12:17 ..
drwxr-xr-x 25 root wheel 1024 Jun 25 12:17 .
drwxrwxrwt 11 nobody wheel 2048 Jun 25 14:13 tmp
drwxr-xr-x 2 root wheel 2560 May 23 2007 sbin
drwxr-xr-x 2 root wheel 2560 Oct 10 2007 rescue
drwxr-xr-x 28 root wheel 3584 May 28 2007 etc.good
drwxr-xr-x 29 root wheel 4096 Jun 25 14:13 etc
-rw------- 1 root wheel 4096 Jun 22 01:50 entropy
-r--r--r-- 1 root wheel 6196 Jan 12 2007 COPYRIGHT
drwxr-xr-x 5 root wheel 14848 Jun 25 01:26 scripts
-rw-r--r-- 1 root wheel 18432 Jun 25 12:17 86random-f1.1.gif
-rw-r----- 1 root operator 32320 May 24 2007 quota.user


noticed that gif file i dumped into / is there

I'm out of ideas at this point. Something wonky is going on.

How's your change control management? Can you trace back any maintenance / modifications to around the time period you started seeing this?

I remember that the second drive doesnt auto mount and some data was being writte to / which should of went on drive2 thats why it was full that data was still there I got it off the system and all is fine now thanks for your help anyway but i managed to resolve it.