On Wed, Feb 10, 2010 at 07:45:17PM -0800, Matthew Dillon wrote: > :This didn't fix it. There was a new crash this night, possibly during the > :daily maintenance window at 3am. > > I've gotten a couple of the panics too. I haven't found the bug yet > but it's definitely still there. I'm still trying to locate it. > Heavy vnode activity triggers it. > > This is the only major bug in the development system right now. > > Speaking of which, could you try turning off vfs.cache_mpsafe if you > have it on? See if that helps.
Unfortunately, it is still at the default value. vfs.cache_mpsafe: 0 -- Francois Tigeot
