Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933505AbbFJHtJ (ORCPT ); Wed, 10 Jun 2015 03:49:09 -0400 Received: from victor.provo.novell.com ([137.65.250.26]:40356 "EHLO prv3-mh.provo.novell.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753153AbbFJHtD (ORCPT ); Wed, 10 Jun 2015 03:49:03 -0400 From: Nick Wang To: philipp.reisner@linbit.com, lars.ellenberg@linbit.com, drbd-dev@lists.linbit.com Cc: linux-kernel@vger.kernel.org, nwang@suse.com Subject: [PATCH 00/10] Zero out devices instead of initial full sync Date: Wed, 10 Jun 2015 15:48:19 +0800 Message-Id: <1433922509-10280-1-git-send-email-nwang@suse.com> X-Mailer: git-send-email 1.8.4.5 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1401 Lines: 36 Full sync for drbd initial usually take a long time, especically when network become the bottleneck the syncing. Simply skip the full sync with "--clear-bitmap" may not the perfect solution for all the cases. So this patches can be used to zero out devices locally instead of a full sync,two make consistent block device. This approach can be useful when lack of network bandwidth to sync. The patches add one new option "--zap-devices" to "new-current-uuid" to zero out devices. Besides the change of drbd, also need to modify drbd-utils for the flag. All patches are compiled/tested against SLES12. Signed-off-by: Nick Wang CC: Philipp Reisner CC: Lars Ellenberg CC: drbd-dev@lists.linbit.com CC: linux-kernel@vger.kernel.org drbd/drbd_int.h | 9 +++++ drbd/drbd_main.c | 42 ++++++++++++++++++++- drbd/drbd_nl.c | 42 ++++++++++++++++++++- drbd/drbd_protocol.h | 1 + drbd/drbd_receiver.c | 99 ++++++++++++++++++++++++++++++++++++++++++++++++++ drbd/linux/drbd_genl.h | 1 + 6 files changed, 191 insertions(+), 3 deletions(-) -- 1.8.4.5 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/