From owner-freebsd-arm@freebsd.org Tue Dec 15 19:54:01 2015 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9115A48090 for ; Tue, 15 Dec 2015 19:54:01 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9CBAF10AB for ; Tue, 15 Dec 2015 19:54:01 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from ilsoft.org (unknown [73.34.117.227]) by outbound2.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Tue, 15 Dec 2015 19:54:08 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id tBFJrxQ2021409; Tue, 15 Dec 2015 12:53:59 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1450209239.25138.62.camel@freebsd.org> Subject: Re: No space left in lost+found From: Ian Lepore To: bob prohaska , freebsd-arm@freebsd.org Date: Tue, 15 Dec 2015 12:53:59 -0700 In-Reply-To: <20151215181047.GA29187@www.zefox.net> References: <20151215181047.GA29187@www.zefox.net> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2015 19:54:01 -0000 On Tue, 2015-12-15 at 10:10 -0800, bob prohaska wrote: > Hi all, > > Lately I've been seeing "sorry, no space left in lost+found > directory" during > routine fsck of my rpi2. The messages seem to be new, in the last few > weeks. > The machine has root on the microSD card, but /usr, /tmp, /var and > swap are > all on a mechanical USB hard disk. Unrecovered files/directories are > in /tmp. > > The running cycle is typically to build the latest revision of > current, compile, > reboot, fsck -fy twice and run stress2 -a till it crashes. Next, > reboot, run fsck -fy > three times, update using svnlite and repeat. > > After the reboot is complete, /lost+found is empty. > > Do I have something misconfigured? > > Thanks for reading, > > bob prohaska I had a similar-ish problem a while back, where a 128gb ufs filesystem showed 75gb in use, 43gb free, but kept getting "no space" errors on trying to copy a few big files to it. I finally found a filesystem snapshot (.snap file) in lost+found and when I removed that suddenly everything was back to normal on that filesystem. -- Ian