Hi, This is the expected behavior, but not the desired behavior.
In case you are using DRBD Manage, DRBD Manage will get the feature to skip the initial resync in case it deploys a DRBD resource on a thinly provisioned volume. It is in development should be merged on the master branch latest next week. In case you are using plain DRBD, read on the drbdsetup man-page how to skip the initial resync. best regards, Phil > Hi, > > I'm using LVM thin as a back-end for DRBD. When initial sync was done the > thin logical volume on secondary node shows 100% of data. Is this normal > behavior? > > Here is the output of lvs -a on primary node: > > LV VG Attr LSize Pool Origin > Data% Meta% Move Log Cpy%Sync Convert > lv_data01 vg_fsdata Vwi-aotz-- 16.00t tp_data > 45.99 > [lvol0_pmspare] vg_fsdata ewi------- > 2.50g > tp_data vg_fsdata twi-aotz-- 20.00t > 36.81 4.76 > [tp_data_tdata] vg_fsdata Twi-ao---- > 20.00t > [tp_data_tmeta] vg_fsdata ewi-ao---- > 10.00g > > > Here is the output of lvs -a on secondary node: > > LV VG Attr LSize Pool Origin Data% Meta% > Move Log Cpy%Sync Convert > lv_data01 vg_fsdata Vwi-aotz-- 16.00t tp_data > 100.00 > [lvol0_pmspare] vg_fsdata ewi------- > 2.50g > tp_data vg_fsdata twi-aotz-- 20.00t 80.00 > 10.31 > [tp_data_tdata] vg_fsdata Twi-ao---- > 20.00t > [tp_data_tmeta] vg_fsdata ewi-ao---- > 10.00g _______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
