Date: Thu, 15 Jan 2009 21:10:23 +0100 From: "Andy Wodfer" <wodfer@gmail.com> To: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Help! locate.code /tmp: filesystem full Message-ID: <23ed14b80901151210l6760c4c6sb60cdc1b1990fb29@mail.gmail.com> In-Reply-To: <4ad871310901141127o509d2480l56233209d79d1694@mail.gmail.com> References: <23ed14b80901141034l16ee0dedp9837e4f1162e253b@mail.gmail.com> <4ad871310901141127o509d2480l56233209d79d1694@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 14, 2009 at 8:27 PM, Glen Barber <glen.j.barber@gmail.com>wrote: > On Wed, Jan 14, 2009 at 1:34 PM, Andy Wodfer <wodfer@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. Thanks for your replies. The requested outputs are: # df -i /tmp Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/ar0s1d 1012974 134 931804 0% 119 141191 0% /tmp # du -h /tmp 2.0K /tmp/.snap 2.0K /tmp/.XIM-unix 2.0K /tmp/ssh-fc3AdQjUmT 2.0K /tmp/.X11-unix 2.0K /tmp/.ICE-unix 2.0K /tmp/.font-unix 134K /tmp I have never done a fsck. Didn't really know of this command. I'm running it now and will post the result when it's finished. I have had one diskproblem a few months ago. This was the output of that: ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad6: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad6: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad6: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad6: WARNING - SET_MULTI taskqueue timeout - completing request directly ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=52327168 ad6: FAILURE - SMART status=51<READY,DSC,ERROR> error=4<ABORTED> ad4: FAILURE - SMART status=51<READY,DSC,ERROR> error=4<ABORTED> ad8: FAILURE - SMART status=51<READY,DSC,ERROR> error=4<ABORTED> Haven't had any trouble since and the server is still running on the same disks and with the same RAID setup. The server has been up for almost 200 days now. Ofcoure I'm worried that one or more disks are having trouble. Look forward to your replies. Thanks! Andy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?23ed14b80901151210l6760c4c6sb60cdc1b1990fb29>