I have filed a PR:  kern/26274 .

On the bright side, I have duplicated the panic with a DEBUG kernel.
However, neither Thomas nor I were able to get a crash dump.  :(

I'm confident that I can get the panic to happen again if someone
has some ideas what I should look at.

Thanks,
+j

On Tue, Jul 13, 2004 at 11:39:39PM +0200, Thomas Klausner wrote:
> On Tue, Jul 13, 2004 at 10:08:21AM -0700, Jeff Rizzo wrote:
> > After a number of months running smoothly (in relation to softdeps, anyway),
> > I just got a softdep-related panic for the second day in a row with
> > a similar workload on the machine (./build.sh for -current with -j4).
> [...]
> > The only thing particularly different from GENERIC.MP about the
> > kernel I'm running is that NEW_BUFQ_STRATEGY is enabled.
> 
> I was just going to mail current-users about this myself, since I have
> the same problem with a 2.0G from July 5, but UP and NEW_BUFQ_STRATEGY
> _not_ enabled. I use FFSv2 file systems, which are all softdeps-enabled,
> in case it matters.
> 
> The backtrace looks the same, once it started with:
> panic: allocdirect_merge ob 0 != 407264 || lbn 1 >= 12 || osize 0 != nsize 16384
> and once with
> panic: allocdirect_merge ob 0 != 448416 || lbn 1 >= 12 || osize 0 != nsize 16384
> 
> The rest is identical.
> 
> At the time the machine was doing a ./build.sh without -j
> and handling consistent network-to-disk traffic of ~100KB/s.
> 
> Ideas and patches :) very welcome...
>  Thomas

-- 
Jeff Rizzo                                         http://www.redcrowgroup.com/