That is part of the story. You most likely have some protocol issues (thus the log entries).
Why would you experiment with cross-version drbd? You should have the easiest results with both servers at the same, recent level. You would need to verify the kernel module and userland program versions on both servers, the commands run, and the relevant dmesg logs from both sides for folks to help you on this problem. ... BTW ... Are you aware that if you do not care about the contents of the disks, you don't have to sync all the zeros? You can create up-to-date disks instantly, and then put a file system on it. Everything will be in sync. The first verify will find a bunch of out-of-sync blocks, but they are in the filesystem's free space and are synced by simply doing a disconnect/reconnect on the secondary node. It really speeds up initial setup, expecially with multi-terabyte resources. (See new-current-uuid in http://www.drbd.org/users-guide-8.3/re-drbdsetup.html; syntax may be different on 8.3 versions). Dan -----Original Message----- From: drbd-user-boun...@lists.linbit.com [mailto:drbd-user-boun...@lists.linbit.com] On Behalf Of Vyacheslav Karpukhin Sent: Tuesday, April 10, 2012 2:49 PM To: drbd-user@lists.linbit.com Subject: Re: [DRBD-user] Unable to perform initial sync On 11.04.2012, at 0:36, Dan Barker wrote: > I do not understand what you did or are trying to do. In Sync has no > "direction". If you are in sync from Primary to Secondary, you are in > sync period. There is no reason to think about a direction. I'm talking about direction because in my case sync from server B to server A works fine, but from server A to server B -- fails. Since it's initial sync of newly created volume, it doesn't matter for me which of the hosts to make Primary, and which -- Secondary. So, that initial sync may be performed in two directions -- from server A to server B, or from server B to server A. In my case when I mark server B as primary, everything is fine, drbd synchronizes from B to A. But if instead I mark server A as primary, synchronization won't perform -- there are protocol errors in the log. I tried to use different versions of drbd, and found out that this issue starts with 8.3.11. Right now drbd performs synchronization from A to B with 8.3.10, but I couldn't make it do that with 8.3.11, 8.3.12 and 8.4.1. In my experiments each time I do the following: 1) "create-md" on both servers 2) starting the resource on both servers 3) marking one of the servers as primary _______________________________________________ drbd-user mailing list drbd-user@lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user _______________________________________________ drbd-user mailing list drbd-user@lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user
