Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
I recently experienced some data loss with drbd. I had a resource "r0" which lost its connection about a month ago and went unnoticed. This past weekend something caused both machines to reboot. They are both running heartbeat. The machine with the older data started heartbeat first and became primary. A sync occurred causing the older data to be copied to the other node. In order to prevent this from happening in the future I have put a script in place to monitor the status of drbd and notify me when resources are not connected. I also set the "on-disconnect reconnect" parameter for all of my resources. My question is what would have caused the older data to look newer to drbd and cause the incorrect re-sync, and what additional steps can be taken to prevent this from happening in the future? Thanks Kris Musard Senior Software Analyst Service Assurance - Broadband SPIRENT COMMUNICATIONS 15200 Omega Drive, 2nd Floor Rockville, MD 20850-3240 USA Office: +1 301.417.6464 Fax: +1 301.590.3662 Pager: +1 800.SKY8888 PIN#1266930 kris.musard at spirentcom.com www.spirentcom.com