Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Mon, Aug 15, 2005 at 01:00:44PM +0800, Vic Berdin wrote: > I'm just trying out drbd-0.7.11. After a successful synch (initial > complete synch) operation, wherein both nodes now reports an > "ld:Consistent" state, I made changes on the Primary. The change > involved creating new paths and dumping of a few Mb of data. After > typing `sync` on the Primary, I expected drbd to automatically update > the Secondary. But this didn't happen. How did you verify that this automatic synchronization of the secondary didn't happen? What 'protocol' have you configured your resources to use in drbd.conf? > How can I properly invoke drbd to perform synchronization only for the > new changes that was made? I realized that doing a `drbdsetup [dev] > invalidate` on the Secondary node will prompt drbd to peform another > round of complete re-synchronization. This is not what I needed, > however. I just want drbd to auto-update the secondary with the new > chunks of data created on the Primary. How do I do this? You're not supposed to have to do anything to cause the secondary to be kept in-sync with the primary. When the mirroring pair is consistent, the secondary is supposed to be kept up-to-date in realtime. AFAIK, you could pull the plug on the primary right after an fsync(), set the secondary as primary, then mount it and see everything before that fsync(). --> Jijo -- Federico Sevilla III : jijo.free.net.ph : When we speak of free software GNU/Linux Specialist : GnuPG 0x93B746BE : we refer to freedom, not price.