From owner-freebsd-current@FreeBSD.ORG Sat Feb 18 06:45:37 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 8370416A420; Sat, 18 Feb 2006 06:45:37 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from mail25.syd.optusnet.com.au (mail25.syd.optusnet.com.au [211.29.133.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA0E043D49; Sat, 18 Feb 2006 06:45:36 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail25.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k1I6jO4t030773 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 18 Feb 2006 17:45:24 +1100 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k1I6jO01005001; Sat, 18 Feb 2006 17:45:24 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k1I6jO7g005000; Sat, 18 Feb 2006 17:45:24 +1100 (EST) (envelope-from peter) Date: Sat, 18 Feb 2006 17:45:23 +1100 From: Peter Jeremy To: Matthew Dillon Message-ID: <20060218064523.GA684@turion.vk2pj.dyndns.org> References: <20060102222723.GA1754@dragon.NUXI.org> <200602180439.k1I4drNm010220@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200602180439.k1I4drNm010220@apollo.backplane.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: David Rhodus , 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 06:45:37 -0000 On Fri, 2006-Feb-17 20:39:53 -0800, Matthew Dillon wrote: > 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. Is it worth setting up a ring buffer that just stores the last few thousand I/O requests and waiting for someone to trip over the panic? This should work if the corruption is close (in temporal terms) to the panic. -- Peter Jeremy