/ 2006-07-12 09:01:33 +0200 \ Wim Ceulemans: > Hi > > We observed that drbd was completely locked (in kernel thread?). All > drbdsetup commands blocked and were not executed. This was after a > short network failure. The drbd log is below. Some other running processes > like squid where also locked, didn't work anymore and could > not be killed and restarted. > We are using drbd-0.7.14
> Anyone seen this before? Could this be fixed in a more recent drbd version? it may have been this: 0.7.18 (api:78/proto:74) ----- * Under high memory pressure it was possible to hit a deadlock on a kmalloc(). Changed the GFP mask, it is no longer possible to deadlock it with memory pressure. and some more esotheric but related fixes in 0.7.19. -- : Lars Ellenberg Tel +43-1-8178292-0 : : LINBIT Information Technologies GmbH Fax +43-1-8178292-82 : : Schoenbrunner Str. 244, A-1120 Vienna/Europe http://www.linbit.com : __ please use the "List-Reply" function of your email client. _______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user _______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
