Date: Thu, 17 Dec 2015 13:57:53 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: No space left in lost+found Message-ID: <20151217115753.GZ3625@kib.kiev.ua> In-Reply-To: <20151216171721.GC29187@www.zefox.net> References: <20151215181047.GA29187@www.zefox.net> <1450204738.4176380.468287977.048387B9@webmail.messagingengine.com> <20151215191845.GB29187@www.zefox.net> <1450209274.4299.468358681.22757635@webmail.messagingengine.com> <1450211241.25138.75.camel@freebsd.org> <20151216074321.GO3625@kib.kiev.ua> <20151216171721.GC29187@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 16, 2015 at 09:17:21AM -0800, bob prohaska wrote: > Hi Konstantin, > > On Wed, Dec 16, 2015 at 09:43:21AM +0200, Konstantin Belousov wrote: > > > > Returning to the OP problem, please show the output of > > ls -ld your/lost+found > > After a fresh rebuild and two passes of fsck -fy the system reports > > root@www:~ # ls -ld /tmp > drwxrwxrwt 15 root wheel 3584 Dec 16 08:13 /tmp > and > root@www:~ # ls -ld /tmp/lost+found > drwx------ 547 bob wheel 364544 Sep 1 20:10 /tmp/lost+found > > root@www:~ # df > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/mmcsd0s2a 7031260 2327656 4141104 36% / > devfs 1 1 0 100% /dev > /dev/mmcsd0s1 51128 7332 43796 14% /boot/msdos > /dev/da0p4 1279260 35500 1141420 3% /tmp > /dev/da0p3 29442460 18778412 8308652 69% /usr > /dev/da0p1 4053308 156140 3572904 4% /var > > so the filesystem does not appear full. However, fsck still > reports messages of the form > > UNREF DIR I=82723 OWNER=bob MODE=40777 > SIZE=512 MTIME=Dec 10 10:43 2015 > RECONNECT? yes > > SORRY. NO SPACE IN lost+found DIRECTORY > UNEXPECTED SOFT UPDATE INCONSISTENCY > > It turns out that /tmp/lost+found contains many files: > root@www:/tmp/lost+found # ls | wc -w > 22782 > Seems like most of them should have been cleaned up automatically > at some point in the past. That by itself appears odd, if not wrong. > There have been no "out of inodes" messages. Nothing 'should' clean /lost+found automatically. It is your files, same as the files linked under other directories. I doubt that you want your files be automatically cleaned, and even in case you want, others don't. AFAIR (I did not rechecked this) fsck does not auto-expand the /lost+found directory. > > Journaling was turned off before the last OS build/install cycle. > Build time remains about 16 hours, no other obvious effects. > > Thanks for reading! > > bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151217115753.GZ3625>