From owner-freebsd-questions Sat May 11 0:26:16 2002 Delivered-To: freebsd-questions@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 4CB5F37B405 for ; Sat, 11 May 2002 00:26:13 -0700 (PDT) Received: (from dan@localhost) by dan.emsphone.com (8.12.2/8.12.3) id g4B7QCnM049852; Sat, 11 May 2002 02:26:12 -0500 (CDT) (envelope-from dan) Date: Sat, 11 May 2002 02:26:11 -0500 From: Dan Nelson To: Edwin Groothuis Cc: freebsd-questions@FreeBSD.ORG Subject: Re: blackout - fsck - cleared files Message-ID: <20020511072611.GM13627@dan.emsphone.com> References: <20020511104229.A750@k7.mavetju.org> <20020511023511.GL13627@dan.emsphone.com> <20020511155044.A748@k7.mavetju.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020511155044.A748@k7.mavetju.org> User-Agent: Mutt/1.3.99i X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (May 11), Edwin Groothuis said: > On Fri, May 10, 2002 at 09:35:11PM -0500, Dan Nelson wrote: > > In the last episode (May 11), Edwin Groothuis said: > > > Last night it was suddenly very dark in the neighbourhood here. > > > Luckely the electricity came back within the hour, but still, my > > > computer didn't like me anymore. It boots without problem, but > > > fsck gave me a lot of lines like: > > > > > > <118> I=1119059 OWNER=edwin MODE=100600 > > > <118>/dev/ad0s1f: SIZE=443 MTIME=May 10 23:44 2002 (CLEARED) > > > <118>/dev/ad0s1f: > > > <118>UNREF FILE > > > > > > The cleared message, does it mean the directory entrance for this > > > file is cleared or that some dirty-flag is cleared? > > > > The UNREF FILE message means there is a valid inode but there are > > no directory entries pointing to it. If you're running softupdates > > you > > So euh... shouldn't these allocated pieces then be stored in > lost+found for possible recovery, or isn't that needed because fsck > does know they're already somewhere else also in a real file? If you have softupdates enabled, it takes care to commit to disk all directory operations in a specific order that guarantees that any unreferenced inodes can be removed. You should actually never need lost+found with softupdates. -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message