From owner-freebsd-stable@FreeBSD.ORG Wed Mar 5 13:05:30 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 2B91B1065677 for ; Wed, 5 Mar 2008 13:05:30 +0000 (UTC) (envelope-from devin@spamcop.net) Received: from mail.distalzou.net (203.141.139.231.static.zoot.jp [203.141.139.231]) by mx1.freebsd.org (Postfix) with ESMTP id CFCB78FC1C for ; Wed, 5 Mar 2008 13:05:29 +0000 (UTC) (envelope-from devin@spamcop.net) Received: from plexi.pun-pun.prv ([192.168.7.29]) by mail.distalzou.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1JWsxp-000Ina-87 for freebsd-stable@freebsd.org; Wed, 05 Mar 2008 21:43:17 +0900 Date: Wed, 5 Mar 2008 21:43:15 +0900 (JST) From: Tod McQuillin X-X-Sender: devin@plexi.pun-pun.prv To: freebsd-stable@freebsd.org Message-ID: <20080305213442.A36748@plexi.pun-pun.prv> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: 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 13:05:30 -0000 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 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, -- Tod McQuillin