From nobody@FreeBSD.org  Wed Aug 18 02:16:35 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0F98516A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 18 Aug 2004 02:16:35 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F20AC43D4C
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 18 Aug 2004 02:16:34 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i7I2GYHe066918
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 18 Aug 2004 02:16:34 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i7I2GYPP066917;
	Wed, 18 Aug 2004 02:16:34 GMT
	(envelope-from nobody)
Message-Id: <200408180216.i7I2GYPP066917@www.freebsd.org>
Date: Wed, 18 Aug 2004 02:16:34 GMT
From: Charles Sprickman <spork@spork.us>
To: freebsd-gnats-submit@FreeBSD.org
Subject: fsck throws files away when it can't grow lost+found
X-Send-Pr-Version: www-2.3

>Number:         70600
>Category:       bin
>Synopsis:       fsck(8) throws files away when it can't grow lost+found
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-fs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Aug 18 02:20:21 GMT 2004
>Closed-Date:    
>Last-Modified:  Fri Sep 24 20:49:29 UTC 2010
>Originator:     Charles Sprickman
>Release:        FreeBSD 4.9
>Organization:
Spork, LLC
>Environment:
FreeBSD skunkworks.spork.us 4.9-RELEASE-p4 FreeBSD 4.9-RELEASE-p4 #6: Mon Mar 29 00:49:50 EST 2004
>Description:
When fsck is run on a well-trashed partition that has a large number of files/directories (for example a mail server using Maildirs, a news server, large office file server), there seems to be some internal limit on the number of directories and/or files that fsck can create within lost+found.  This results in many possibly recoverable files being deleted.
>How-To-Repeat:
Trash a filesystem badly. :)  Then run fsck on it.  At some point, fsck will start spitting out the error "SORRY. NO SPACE IN lost+found DIRECTORY".  Since one is probably running with "-y" due to the large number of prompts a bad fs will have, from that point on everything fsck tries to "reconnect" into lost+found gets trashed.  You have lost possibly good data at that point.
>Fix:
I don't really have any C skills, but on a box where I'm attempting recovery off of a dd image of a trashed fs, I've modified "dir.c" like so to make fsck just exit when it can no longer add files to lost+found:

if (makeentry(lfdir, orphan, (name ? name : tempname)) == 0) {
                pfatal("SORRY. NO SPACE IN lost+found DIRECTORY");
                printf("exiting...\n\n");
                exit (99);
                return (0);
        }

I then mount the fs r/w, copy off everything in lost+found, rm -rf lost+found, unmount, and then run fsck again.  I keep doing this until it's finished.  

I imagine someone more familiar with fsck could have it do something else at that point; like create a "lost+found1" directory and keep incrementing.  That's my best guess as to how to approach this.

Thanks,

Charles
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-fs 
Responsible-Changed-By: brucec 
Responsible-Changed-When: Fri Sep 24 20:49:10 UTC 2010 
Responsible-Changed-Why:  
Over to maintainer(s). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=70600 
>Unformatted:
