From owner-freebsd-stable@FreeBSD.ORG Thu Jul 21 09:45:38 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1A0516A423 for ; Thu, 21 Jul 2005 09:45:38 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id D310F43D64 for ; Thu, 21 Jul 2005 09:45:34 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 2D763A2FE4 for ; Thu, 21 Jul 2005 11:45:34 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id 09B236462; Thu, 21 Jul 2005 11:45:34 +0200 (CEST) Date: Thu, 21 Jul 2005 11:45:33 +0200 From: Marc Olzheim To: freebsd-stable@FreeBSD.org Message-ID: <20050721094533.GE52120@stack.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7DO5AaGCk89r4vaK" Content-Disposition: inline X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i Cc: Subject: background fsck, softupdates & inconsistent state on disk 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: Thu, 21 Jul 2005 09:45:38 -0000 --7DO5AaGCk89r4vaK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi. Having enough opportunities to do crash recovery with kern/83375 open and some of my services not yet moved back to FreeBSD 4, I noticed that often it crashes just after (or perhaps during) mirroring of a directory tree. The mirroring involves creating a directory with in it 80 subdirectories in it. Now when the machine panics on a 'screen' again, background fsck fails to properly check the filesystem and reports so in /var/log/messages. What I see on that partition is the main directory that should have contained the 80 subdirs, but now it has a link count of 0 and so doesn't even contain a . or .. , let alone the 80 directories that should have been there. The only thing a manual fsck can do after that is unlink the unreferenced inodes and clear up the mess... Shouldn't this be impossible without power loss ? Or is it inherent to SMP that the machine can crash on a process on CPU #0 while CPU #1 is updating disk structures ? Anyway, as soon as the migration of production services suffering from kern/83375 back to 4.x is done I should have a 5.x test machine ready to crash whenever people want, so I can get debug output out of it. If anyone could tell me how to get it and what they need, I'd be happy to provide it. Marc --7DO5AaGCk89r4vaK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC3269ezjnobFOgrERArKjAKC7MD0AIfrZhthDidHyLYMo6th1HQCcDp3R HhU2UPfgblhFenIqeU+HQ1Q= =uKR+ -----END PGP SIGNATURE----- --7DO5AaGCk89r4vaK--