Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Ok, found a way: debnode2:~# drbdadm down db debnode2:~# drbdadm -- :::::1:::: set-gi db previously 1E65F6C2CB7D5B5C:0000000000000000:E9ACAE2A5D5F54A8:0173BFF26274A71F:1:0:0:0:0:0 set GI to 1E65F6C2CB7D5B5C:0000000000000000:E9ACAE2A5D5F54A8:0173BFF26274A71F:1:1:0:0:0:0 Write new GI to disk? [need to type 'yes' to confirm] yes debnode2:~# drbdadm up db debnode2:~# /usr/lib/heartbeat/ResourceManager takegroup drbddisk Why not add a simple "drbdadm uptodate" to drbdadm to issue the corresponding commands ? This would simplify the commands. Regards, Robert Robert schrieb: > How can I easily set a outdated disk back to UpToDate ? > > Lets assume the situation where your primary data center burns down. > First the network switch for the replication link burns and then the > server itself. So first the standby disk is outdated by dopd. 2 > minutes later the primary server dies and heartbeat ties to activate > ressources - as intended(!). How your boss comes and says - primary > data center burned down ? what the heck, we have a cluster start all > engines in the other data center. Your data (some minutes old but > outdated) in the second data center is ALL you have, so you have to > remove the outdated flag so start the ressource. > > How can someone remove the outdated flag ? drbdmeta ? > > Robert >