Re: Help! locate.code /tmp: filesystem full
On Thursday 15 January 2009 13:37:06 Polytropon wrote: On Thu, 15 Jan 2009 21:37:24 +0100, Andy Wodfer wod...@gmail.com wrote: Added context: Here's the output of fsck (this was a new command to me): # fsck ** /dev/ar0s1a (NO WRITE) Should I run fsck -y? Is it safe to do so? At least, fsck will do its best to repair the defective file system. As you have seen from the messages, you will surely lose some files when their information gets cleared. If you use -y, fsck is allowed to do anything it considers neccessary doing. fsck on a live filesystem (hint: NO WRITE) is a bad idea. Doing an fsck that is supposed to repair stuff, always requires downtime, unless you use background_fsck. However, many people discourage it's usage as it can leave some errors unfixed. In short: reboot in single user mode, then run fsck -y at the prompt. Never ever run fsck -y on a live filesystem. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Help! locate.code /tmp: filesystem full
On Thu, 22 Jan 2009 10:24:39 -0900, Mel fbsd.questi...@rachie.is-a-geek.net wrote: In short: reboot in single user mode, then run fsck -y at the prompt. Never ever run fsck -y on a live filesystem. A very good hint. Didn't I mention it? No? Bad idea. Background concept: The fsck utility does changes to the file system when repairing it, and the kind of these changes implies that the file system is not mounted, so there's no unexpected interruption by maybe a write operation from a program. That's what downtime is good for - letting fsck doing its job well. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Help! locate.code /tmp: filesystem full
On Wed, Jan 14, 2009 at 8:27 PM, Glen Barber glen.j.bar...@gmail.comwrote: On Wed, Jan 14, 2009 at 1:34 PM, Andy Wodfer wod...@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 SizeUsed Avail Capacity Mounted on /dev/ar0s1a989M 53M857M 6%/ devfs 1.0K1.0K 0B 100%/dev /dev/ar0s1g 48G8.5G 36G19%/backup /dev/ar0s1d989M 44K910M 0%/tmp /dev/ar0s1f387G168G189G47%/usr /dev/ar0s1e7.7G398M6.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 1411910% /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=51READY,DSC,ERROR error=4ABORTED ad4: FAILURE - SMART status=51READY,DSC,ERROR error=4ABORTED ad8: FAILURE - SMART status=51READY,DSC,ERROR error=4ABORTED 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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Help! locate.code /tmp: filesystem full
On Wed, Jan 14, 2009 at 7:34 PM, Andy Wodfer wod...@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: #dmesg [snip] pid 54753 (locate.code), uid 65534 inumber 23557 on /tmp: filesystem full # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ar0s1a989M 53M857M 6%/ devfs 1.0K1.0K 0B 100%/dev /dev/ar0s1g 48G8.5G 36G19%/backup /dev/ar0s1d989M 44K910M 0%/tmp /dev/ar0s1f387G168G189G47%/usr /dev/ar0s1e7.7G398M6.7G 5%/var As you see there's 910MB free space in /tmp. Should be plenty to run the weekly locate script? # uname -a FreeBSD host.domain.com 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #5: Sat Jan 12 03:20:02 CET 2008 r...@host.domain.com:/usr/obj/usr/src/sys/MYOWN i386 Does anyone have a suggestion what I can do to fix this problem? Thanks a lot! Best, Andy Here's the output of fsck (this was a new command to me): # fsck ** /dev/ar0s1a (NO WRITE) ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1565 files, 27379 used, 479108 free (1204 frags, 59738 blocks, 0.2% fragmentation) ** /dev/ar0s1g (NO WRITE) ** Last Mounted on /backup ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 873 files, 4467162 used, 20921355 free (891 frags, 2615058 blocks, 0.0% fragmentation) ** /dev/ar0s1d (NO WRITE) ** Last Mounted on /tmp ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 119 files, 67 used, 506420 free (28 frags, 63299 blocks, 0.0% fragmentation) ** /dev/ar0s1f (NO WRITE) ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames UNALLOCATED I=7961594 OWNER=www MODE=100620 SIZE=69292 MTIME=Jan 15 21:06 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/sql_021151d1a377d62dbfaa89a4d1acc716.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961584 OWNER=www MODE=100620 SIZE=4784 MTIME=Jan 15 21:06 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/data_search_results_c34cf621be1e424bde185cb6b71bf55f.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961588 OWNER=www MODE=100620 SIZE=317 MTIME=Jan 15 21:06 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/sql_de3e82ec3f05e04f8caecf9cecb70fe5.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961590 OWNER=www MODE=100620 SIZE=343 MTIME=Jan 15 21:06 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/sql_45386e120e999630d18124e757c15cd5.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961593 OWNER=www MODE=100620 SIZE=155 MTIME=Jan 15 21:06 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/data_search_results_a770f781f984926682ad24b828d1568c.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961595 OWNER=www MODE=100620 SIZE=317 MTIME=Jan 15 21:07 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/sql_f60c9f27d5a394bc6e9a70185d29ccf2.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961597 OWNER=www MODE=100620 SIZE=223 MTIME=Jan 15 21:07 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/data_search_results_99f04705815fd4978b0d47911d8b44ad.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961599 OWNER=www MODE=100620 SIZE=343 MTIME=Jan 15 21:08 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/sql_46c003bc334cf0386554f73d8bb37688.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961600 OWNER=www MODE=100620 SIZE=343 MTIME=Jan 15 21:09 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/sql_0c5aeb430c03186f1c1cd9c56cd3320c.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961601 OWNER=www MODE=100620 SIZE=317 MTIME=Jan 15 21:09 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/sql_1bbabc64d41b06401b3f49122429cfb8.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=7961602 OWNER=www MODE=100620 SIZE=241 MTIME=Jan 15 21:09 2009 FILE=/local/www/[removed]/data/scripts/forum/cache/data_search_results_708ac649d78e7e8f4912da48dbb2f0d3.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=10086553 OWNER=www MODE=100660 SIZE=5572 MTIME=Jan 15 21:09 2009 FILE=/local/www/[removed]/data/scripts/forum/images/avatars/upload/f3bd348b1ce8f9503d1d63b34905349d_3218.jpg UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=7961486 OWNER=www MODE=100620 SIZE=316 MTIME=Jan 15
Re: Help! locate.code /tmp: filesystem full
On Thu, 15 Jan 2009 21:37:24 +0100, Andy Wodfer wod...@gmail.com wrote: Should I run fsck -y? Is it safe to do so? At least, fsck will do its best to repair the defective file system. As you have seen from the messages, you will surely lose some files when their information gets cleared. If you use -y, fsck is allowed to do anything it considers neccessary doing. You could use fsck in preen mode (-p) to have less defects corrected. If it's possible, try to backup all important data. If fsck deletes something, you could restore it afterwards. Your goal should be to get your file system into a consistent state again. Worse kinds of data loss can follow. It hurts, I know it... :-( -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Help! locate.code /tmp: filesystem full
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: #dmesg [snip] pid 54753 (locate.code), uid 65534 inumber 23557 on /tmp: filesystem full # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ar0s1a989M 53M857M 6%/ devfs 1.0K1.0K 0B 100%/dev /dev/ar0s1g 48G8.5G 36G19%/backup /dev/ar0s1d989M 44K910M 0%/tmp /dev/ar0s1f387G168G189G47%/usr /dev/ar0s1e7.7G398M6.7G 5%/var As you see there's 910MB free space in /tmp. Should be plenty to run the weekly locate script? # uname -a FreeBSD host.domain.com 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #5: Sat Jan 12 03:20:02 CET 2008 r...@host.domain.com:/usr/obj/usr/src/sys/MYOWN i386 Does anyone have a suggestion what I can do to fix this problem? Thanks a lot! Best, Andy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Help! locate.code /tmp: filesystem full
On Wed, Jan 14, 2009 at 1:34 PM, Andy Wodfer wod...@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 SizeUsed Avail Capacity Mounted on /dev/ar0s1a989M 53M857M 6%/ devfs 1.0K1.0K 0B 100%/dev /dev/ar0s1g 48G8.5G 36G19%/backup /dev/ar0s1d989M 44K910M 0%/tmp /dev/ar0s1f387G168G189G47%/usr /dev/ar0s1e7.7G398M6.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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Help! locate.code /tmp: filesystem full
On 01/14/2009 10:34 AM, Andy Wodfer 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: #dmesg [snip] pid 54753 (locate.code), uid 65534 inumber 23557 on /tmp: filesystem full # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/ar0s1a989M 53M857M 6%/ devfs 1.0K1.0K 0B 100%/dev /dev/ar0s1g 48G8.5G 36G19%/backup /dev/ar0s1d989M 44K910M 0%/tmp /dev/ar0s1f387G168G189G47%/usr /dev/ar0s1e7.7G398M6.7G 5%/var As you see there's 910MB free space in /tmp. Should be plenty to run the weekly locate script? [...] What is the output of 'df -i /tmp'? -- Benjamin Lee http://www.b1c1l1.com/ signature.asc Description: OpenPGP digital signature
