Date: Sat, 18 Feb 2006 17:45:23 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: David Rhodus <drhodus@machdep.com>, freebsd-current@freebsd.org Subject: Re: It still here... panic: ufs_dirbad: bad dir Message-ID: <20060218064523.GA684@turion.vk2pj.dyndns.org> In-Reply-To: <200602180439.k1I4drNm010220@apollo.backplane.com> References: <20060102222723.GA1754@dragon.NUXI.org> <200602180439.k1I4drNm010220@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060218064523.GA684>