From owner-freebsd-current Wed Mar 14 16:40:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 2077937B719 for ; Wed, 14 Mar 2001 16:40:27 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2F0drt33628; Wed, 14 Mar 2001 16:39:53 -0800 (PST) (envelope-from dillon) Date: Wed, 14 Mar 2001 16:39:53 -0800 (PST) From: Matt Dillon Message-Id: <200103150039.f2F0drt33628@earth.backplane.com> To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: Panic and filesystem corruption References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I was cvsupping the GNATS database (the *entire* GNATS database, that :is - I didn't already have a copy) when I got this panic: How old a kernel are you running? Kirk and I have been attempting to locate the filesystem bitmap corruption for months. We've fixed a number of bugs but have yet to find a smoking gun. It is possible that it *has* been fixed but people's filesystems still contain some corruption from previous breakage. The corruption appears to be related to heavy directory activity and may or may not be related to softupdates. We just can't tell. We can't reproduce it. We thought we had found someone who could reproduce the problem at will but it turned out to be his RAID controller screwing up (where even newfs followed by an fsck would generate errors). Yahoo's test machines still occassionally show the problem, but so far it's too infrequent to get a good handle on. fsck all of your filesystems from single-user to remove the possibility of 'old' corruption (as in 'fsck', not 'fsck -p'). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message