linux-kernel - [Patch v2 00/10] Zero out devices instead of initial full sync

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1436776744-3135-1-git-send-email-nwang@suse.com>
Date:	Mon, 13 Jul 2015 16:38:54 +0800
From:	Nick Wang <nwang@...e.com>
To:	nwang@...e.com
Cc:	philipp.reisner@...bit.com,
	Lars Ellenberg <lars.ellenberg@...bit.com>,
	drbd-dev@...ts.linbit.com, linux-kernel@...r.kernel.org
Subject: [Patch v2 00/10] Zero out devices instead of initial full sync

Patch set is based on drbd-8.4 859e34a9, have
already compiled/tested against SLES12.

If this feature can be merged into upstream, please
ignore v1, since v1 may caused pingACK timeout when
zeroing out large device.

Compare to v1, changes are as follow:
 1. Using drbd_device_post_work to zero out device as background
    task, so that it won't block pingACK when zeroing out
    large device.

 2. Fix bug of won't update peer node status if it finished
    zeroing out earier.

 3. Change some functions from file drbd_receive.c to
    drbd_worker.c and reorder the patch set.


Full sync for drbd initial usually take a long time, especically
when network become the bottleneck of the syncing. Simply skip
the full sync with "--clear-bitmap" may not the perfect solution
for all the cases, like using the bare device(no filesystem) to
work,etc database,vm... This patche set can be used to zero out
devices locally instead of a full sync to make the 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. It will start zeroing out devices of both
side.

Nick Wang (10):
  drbd: Fix the wrong logic of move history.
  drbd: Add options zap_devices to new-current-uuid
  drbd: Add a function to zero out drbd backing device.
  drbd: New packet P_ZERO_OUT.
  drbd: Functions to notify peer node to start
        zeroing out and zero out finished.
  drbd: Wapper for zeroing out device by worker.
  drbd: Add flag for drbd device work.
  drbd: Function to work with packet P_ZERO_OUT.
  drbd: Receive zero out command from peer node.
  drbd: Handle new-current-uuid --zap-devices.

Signed-off-by: Nick Wang <nwang@...e.com>
CC: Philipp Reisner <philipp.reisner@...bit.com>
CC: Lars Ellenberg <lars.ellenberg@...bit.com>
CC: drbd-dev@...ts.linbit.com
CC: linux-kernel@...r.kernel.org

 drbd/drbd_int.h        | 13 ++++++++
 drbd/drbd_main.c       | 51 ++++++++++++++++++++++++++--
 drbd/drbd_nl.c         | 21 +++++++++++-
 drbd/drbd_protocol.h   |  1 +
 drbd/drbd_receiver.c   | 69 ++++++++++++++++++++++++++++++++++++++
 drbd/drbd_worker.c     | 90 ++++++++++++++++++++++++++++++++++++++++++++++++++
 drbd/linux/drbd_genl.h |  1 +
 7 files changed, 243 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/