From owner-freebsd-current@FreeBSD.ORG Sat Feb 18 04:39:54 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E9E116A420; Sat, 18 Feb 2006 04:39:54 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D984F43D45; Sat, 18 Feb 2006 04:39:53 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.4/8.13.4) with ESMTP id k1I4drNm010221; Fri, 17 Feb 2006 20:39:53 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.13.4/8.13.4/Submit) id k1I4drNm010220; Fri, 17 Feb 2006 20:39:53 -0800 (PST) Date: Fri, 17 Feb 2006 20:39:53 -0800 (PST) From: Matthew Dillon Message-Id: <200602180439.k1I4drNm010220@apollo.backplane.com> To: obrien@freebsd.org, David Rhodus References: <20060102222723.GA1754@dragon.NUXI.org> Cc: freebsd-current@freebsd.org Subject: Re: It still here... panic: ufs_dirbad: bad dir X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Feb 2006 04:39:54 -0000 :Just in case anyone thought the bug had been fixed... : :FreeBSD 7.0-CURRENT #531: Mon Jan 2 11:32:17 PST 2006 i386 : :panic: ufs_dirbad: bad dir :... :-- David (obrien@FreeBSD.org) :Q: Because it reverses the logical flow of conversation. :A: Why is top-posting (putting a reply at the top of the message) frowned upon? We are still seeing it in DragonFly, too. Right now I have two reports, one from DR, one from Tomaz. It doesn't happen very often but it definitely still happens. I have already turned off background bitmap writes and I disallow inode reuse before the previous user finishes flushing its buffers out. All related softupdates fixes made in FreeBSD have been ported to DragonFly. David, have you tried turning off doreallocblks ? i.e. set vfs.ffs.doreallocblks=0. Both Davids, please try that, do a full manual fsck, and report if the problem still occurs. If it doesn't fix it then we will at least eliminate another possible source for the problem. I wish there were a way to reliably reproduce the failure. I'm running out of ideas. Right now my best idea is that there is something broken in the code that writes out the modified 'rewound' blocks. Perhaps an old version of a buffer, with old already-reused block pointers, is being written out and then something happens to prevent the latest version from being written out. I don't know, I'm grasping at straws here. If I could only reliably reproduce the bug I would write some code to record every I/O operation done on the raw device then track back to the write that created the corruption. -Matt Matthew Dillon