linux-kernel - Re: [Drbd-dev] [PATCH 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Wed, 10 Jun 2015 13:44:02 +0200
From:	Lars Ellenberg <lars.ellenberg@...bit.com>
To:	philipp.reisner@...bit.com, lars.ellenberg@...bit.com,
	drbd-dev@...ts.linbit.com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [Drbd-dev] [PATCH 00/10] Zero out devices instead of initial
 full sync

resent, accidentally truncated the Cc list.
also added one paragraph.

On Wed, Jun 10, 2015 at 03:48:19PM +0800, Nick Wang wrote:
> 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.

Completely unnecessary.
Zero out the devices in userspace, then set up DRBD,
and skip the initial sync.

On backends that support it,
you can already simply blkdiscard /dev/drbdX
(or use the implicit discard of some mkfs)
once you set it up for the first time,
even when the initial resync just began,
and that discard will finish the "initial resync",
without taking up any real network bandwidth.

In short: I don't see the point.

	Lars Ellenberg

--
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/