On Tue, Oct 19, 2004 at 06:01:00PM -0400, Stephen Frost wrote: > * Stephen Frost ([EMAIL PROTECTED]) wrote: > > * Herbert Poetzl ([EMAIL PROTECTED]) wrote: > > > have seen that too, once in a while, but there where > > > some changes in 2.6.9, so maybe trying 2.6.9-rc4 > > > (or soon final) with vs1.9.3-rc3 (not much changed > > > here, see delta for details) would be a good check > > > > Ok. I had been planning on moving to 2.6.9 and 1.9.3 as soon as both > > were final. Guess I can try the RC releases though. :) > > Alright, I got the same oops w/ 2.6.9 and vs1.9.3-rc3: > > Assertion failure in log_do_checkpoint() at fs/jbd/checkpoint.c:361: > "drop_count != 0 || cleanup_ret != 0"
you can split up this assertion into - drop_count != 0 - cleanup_ret != 0 and fail on that (or just output those values before you panic) ... this might give some deeper insight into the issue ... > > I noticed someone else had this problem too: > > http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=123137 hmm, so that kernel should not be vserver related at all, so I'd say something with the ext3 journal is broken ... > I also followed up on that w/ my oops from 2.6.8.1. > > I also upgraded to 0.30.195, though I don't think that (or vserver in > general, really) is related to this oops. yeah, probably not, I think the vserver changes just make the oops more likely (or simply the increased load does) > If there's anything else I can do to help get this resolved, please let > me know.. This is the only problem I'm having with this server now, > other than this it's behaving pretty nicely. :) maybe until it gets fixed, mounting the ext3 without journal might help here? best, Herbert > Thanks, > > Stephen > _______________________________________________ > Vserver mailing list > [EMAIL PROTECTED] > http://list.linux-vserver.org/mailman/listinfo/vserver _______________________________________________ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
