[DRBD-user] "syncer" crash when doing full resync

Lars Marowsky-Bree lmb at suse.de
Thu Sep 23 17:12:38 CEST 2004

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


On 2004-09-23T10:55:19,
   "Kohari, Moiz" <mkohari at enterasys.com> said:

> Thank you for a healthy discussion.  I really appreciate your help.
> 
> First, the metadata scheme in 0.7 where it requires a 128M dedicated
> partition instead of a small file in /var/lib/drbd is the reason we
> are still using the 0.6.x release.  Is there an easy way around this
> feature, so we can use 0.7 release?

You could make it work with an external metadata device, or simply
shrink the data on the device a bit.

> Second, we see the memory corruption problem on multiple machines as
> well as inside our simulation on UML.  In our case the problem is
> probably not related to bad RAM (statistically improbable).  In our
> case, its either random kernel memory corruption from somewhere in the
> kernel, or a bug in DRBD.  Considering that it happens in the *exact*
> same spot in the drbd driver every time for us and other users on this
> drbd list, the corruption has a probability of occurring within drbd?

What kernel exactly? Sorry, I couldn't find that in your mail.


Sincerely,
    Lars Marowsky-Brée <lmb at suse.de>

-- 
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX AG - A Novell company




More information about the drbd-user mailing list