No space left in lost+found

Konstantin Belousov kostikbel at gmail.com
Thu Dec 17 11:58:06 UTC 2015


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 at www:~ # ls -ld /tmp
> drwxrwxrwt  15 root  wheel  3584 Dec 16 08:13 /tmp
> and
> root at www:~ # ls -ld /tmp/lost+found
> drwx------  547 bob  wheel  364544 Sep  1 20:10 /tmp/lost+found
> 
> root at 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 at 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


More information about the freebsd-arm mailing list