Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hey all, I had an unexpected syncing all last time one of my servers went down. Can you tell me what I did wrong? I am using drbd 0.6.12 Currently I am not using heartbeat, so when my primary went down I ran - /etc/ha.d/resource.d/datadisk start - all my service starts Then when the primary came back I - stopped all my services - /etc/ha.d/resource.d/datadisk stop Which left drbd in secondary/unconnected. Then on the primary I ran - /etc/rc.d/drbd start at this point I got a syncing all message. I thought that by putting drbd into secondary on the secondary machine, I could do a quick sync. What should I have done? Also, I was looking for some docs that explained exactly when a syncing all condition would happen. The closest I found was this: http://wiki.linux-ha.org/DataRedundancyByDrbd#head-67e41946554d49024d8f83f0e2386b69787a4ec0 which was good, but didn't break it down enough for me to understand. Anything else I should have found? I'm not a subscriber, so for any replies - please cc this address in. Thanks for any help, -- Matthew Venn Head of IT oncampusuk Ltd Tel:07949 653 676 This message is confidential and contains information which may be legally privileged. It is intended for the stated addressee(s) only. Access to this e-mail by anyone else is unauthorised. If you are not the intended addressee, any disclosure, copying or storage of the contents of this e-mail, or any action taken (or not taken) in reliance on it, is unauthorised and is unlawful. If you are not the addressee, please delete the original and inform the sender immediately.