Help! locate.code /tmp: filesystem full

[Glen Barber]

On Wed, Jan 14, 2009 at 1:34 PM, Andy Wodfer <wodfer at gmail.com> wrote:
> Hi,
> I'm getting an error message every week and I can't seem to understand why
> nor manage to fix it. Here it is:
>

[snip]

>
> # df -h
> Filesystem     Size    Used   Avail Capacity  Mounted on
> /dev/ar0s1a    989M     53M    857M     6%    /
> devfs          1.0K    1.0K      0B   100%    /dev
> /dev/ar0s1g     48G    8.5G     36G    19%    /backup
> /dev/ar0s1d    989M     44K    910M     0%    /tmp
> /dev/ar0s1f    387G    168G    189G    47%    /usr
> /dev/ar0s1e    7.7G    398M    6.7G     5%    /var
>
> As you see there's 910MB free space in /tmp. Should be plenty to run the
> weekly locate script?
>

Have you recently had disk failures?  When was your last `fsck' ?

What is the output of `du -h /tmp' ?

To rule out if 910M is not enough, you could `mv' /tmp to /tmp.bak and
do a hard link pointing a new /tmp somewhere with more space, for
example /usr/faketmp.

I don't know how this will affect fstab or mount, however.

-- 
Glen Barber