From owner-freebsd-stable@FreeBSD.ORG Wed Mar 5 22:03:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69EC61065670 for ; Wed, 5 Mar 2008 22:03:51 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from hosted.kievnet.com (hosted.kievnet.com [193.138.144.10]) by mx1.freebsd.org (Postfix) with ESMTP id 2E2AA8FC21 for ; Wed, 5 Mar 2008 22:03:51 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from edge.pp.kiev.ua ([91.193.172.111]) by hosted.kievnet.com with esmtpa (Exim 4.62) (envelope-from ) id 1JX166-00064n-7A; Wed, 05 Mar 2008 23:24:22 +0200 Message-ID: <47CF0F7D.3050805@icyb.net.ua> Date: Wed, 05 Mar 2008 23:24:13 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.9 (X11/20071208) MIME-Version: 1.0 To: Tod McQuillin References: <1204734183.00036125.1204722602@10.7.7.3> In-Reply-To: <1204734183.00036125.1204722602@10.7.7.3> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Odd file in /lost+found after softupdate inconsistency in fsck X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Mar 2008 22:03:51 -0000 on 05/03/2008 14:43 Tod McQuillin said the following: > Hi all, > > My server froze up tonight after a 2 month uptime running 6.3-PRERELEASE > from Dec 28 2007. > > I had to fsck /home by hand because of an inconsistency fsck couldn't > repair automatically -- something to do with an unexpected softupdate > inconsistency. > > After that, I ended up with some files in /home/lost+found, one of which > is quite interesting: > > /home/lost+found# ls -lksh > total 24432 > 24432 -r-------- 1 root operator 40G Mar 5 20:12 #0000005 > > It is 40G in size but only occupies 24432k on disk, so it is a sparse > file. I'm not aware of any sparse files of quite that size on my system > (or relative sparseness) but it's possible i might overlook one. > > But the thing that's interesting to me is the inode number (inode 5) and > the fact that rm doesn't want me to remove it: > > /home/lost+found# rm \#0000005 > override r-------- root/operator snapshot for #0000005? n Are you sure that it doesn't want to remove it? It's just asking you the question (maybe because you executed rm as non-root or maybe because of the mode of the file); you can answer 'yes', you know. > Is there a magic "shapshot" flag on the file? Have I somehow damaged my > ufs2+softupdates filesystem by losing its inode #5 containing snapshot > data? > > Any insights appreciated, You can try stat(1) on it to see all the details, that could help with further conclusions. -- Andriy Gapon