[DRBD-user] secondary sync behaviour after drbd stop and start

Lars Ellenberg lars.ellenberg at linbit.com
Tue Jun 21 23:51:51 CEST 2011

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

On Tue, Jun 21, 2011 at 05:55:24PM +0200, Gianluca Cecchi wrote:
> hello,
> using drbd 8.3.8 in CentOS 5.6 as provided by extra repo.
> testing/simulating condition when secondary is taken down and some of
> its data are modified before restart it...
> (or you want to verify that if any problem/bug have modified them, you
> come back to safety when you restart the secondary)
> servers are drbdsrv1 and drbdsrv2, in Primary/Secondary with drbdsrv1 as Primary
> with
>  0: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r----
> drbd r0 on /dev/vdb1 for both nodes and then ext3 file system on top of drbd0
> 1) [root at drbdsrv1 ~]# mount /dev/drbd0 /mnt/
> [root at drbdsrv1 ~]# dd if=/dev/zero bs=/mnt/testfile bs=1024k count=2048
> Secondary receives 2Gb on the wire and remains updated
> 2) keep down secondary
> [root at drbdsrv2 ~]# service drbd stop
> 3) mount backing device on secondary

Do not bypass DRBD.

Well, of course you can.

But if you do, don't blame DRBD for not keeping track of your doings.

: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com

More information about the drbd-user mailing list