philipp.reisner at linbit
Mar 8, 2006, 6:22 AM
Post #1 of 1
(1694 views)
Permalink
|
0.7.17 (api:77/proto:74)
-----
* There was a bug that could cause the activity log to be not applied
after a primary crash, when an other size than 127 elements was configured.
* There was a bug in the activity log code, that could cause that the
latest update to the AL is omitted at recovery time.
* The "Marked additional XXKB as out-of-synced based on AL." message
showed one one eighth of the real amount, fixed.
These are serious flaws in DRBD. Altough the probability to hit by
one of these bugs is not high, and they are only of interest
when you had a primary crash.
But if you are hit by one of these bugs a few data blocks
might be out of sync on your mirror pair!
1. You should upgrade.
2. If you ever had a crash of your primary node in your cluster you
should do a full sync now.
http://oss.linbit.com/drbd/0.7/drbd-0.7.17.tar.gz
http://www.linbit.com/support/drbd-0.7.17/
http://svn.drbd.org/drbd/tags/drbd-0.7.17/
-Philipp
--
: Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Schönbrunnerstr 244, 1120 Vienna, Austria http://www.linbit.com :
_______________________________________________
drbd-announce mailing list
drbd-announce [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-announce
|
