From owner-freebsd-current Wed Jan 22 2:14:57 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92E7037B401 for ; Wed, 22 Jan 2003 02:14:56 -0800 (PST) Received: from student.uci.agh.edu.pl (student.uci.agh.edu.pl [149.156.98.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id C104F43F13 for ; Wed, 22 Jan 2003 02:14:55 -0800 (PST) (envelope-from winfried@student.agh.edu.pl) Received: by student.uci.agh.edu.pl (Postfix, from userid 25828) id DA10664632; Wed, 22 Jan 2003 11:14:47 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by student.uci.agh.edu.pl (Postfix) with ESMTP id CDA236F631; Wed, 22 Jan 2003 11:14:47 +0100 (CET) Date: Wed, 22 Jan 2003 11:14:47 +0100 (CET) From: Jan Srzednicki X-X-Sender: winfried@student.uci.agh.edu.pl To: David Schultz Cc: current@FreeBSD.ORG Subject: Re: background fsck did not create lost+found In-Reply-To: <20030120183442.GA2778@HAL9000.homeunix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 20 Jan 2003, David Schultz wrote: > > First two entries clearly correspond to the missing file, which should > > have been put in /home/lost+found. But, the poroblem is that no lost+found > > directory was created, while it should (as fsck_ffs(8) says). I guess its > > a bug, probably in the background fsck code. Still, is there any way to > > reclaim the file now, besides running strings(1) on the whole partition? > > Consider what happens when you remove a large directory tree. > Thousands of directory entries may be removed, but in the > softupdates case, the inodes will stick around a bit longer. The > same also applies to files that have been intentionally unlinked > but are still open. To avoid a syndrome where all these thousands > of files end up in lost+found after a crash or power failure, fsck > just removes them on softupdates-enabled filesystems. Would that be a big problem to allow some fsck option not to erase all these softupdates-pending inodes, but to put them in lost+found as usual? The default behaviour is unchanged, yet there is a way to reclaim lost files. -- -- wrzask --= v =-- Winfried --=-- GG# 3838383 --=-- JS500-RIPE -- -- w@dream.vg --- w@303.krakow.pl --===-- http://violent.dream.vg/ --- --=< Ride the wild wind - push the envelope, don't sit on the fence, --- -- Ride the wild wind - live life on the razor's edge! >=-- Queen -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message