Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
if the only way you can trigger those corruptions is to pull the plug, chances are that your disk is lying to the kernel, and pretends that it has written something to stable storage while it has only reached the disks internal cache. if that is the case, you'd get those corruptions without drbd just the same, if you pull the plug during busy io. to solve that, you have several options. * get battery backed cache, * get a disk that has some cache, even if not battery backed, but still does only reports writes as done when they _are_ in fact on disk. * disable the cache if you believe it is something else, please try to reproduce without heartbeat, with only one single small drbd device, and try to not line-wrap mangle the log files... it just costs too much time to dig through all that stuff otherwise. -- : 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.