Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi guys, Seem to have hit a snag on a 2.6 FC2 machine running drbd-0.7.5-3 This pair had been running fine for a couple of months, then the Primary (Machine A) died, a manual failover worked and we're currently running on the Secondary (Machine B). Machine B is now running and in WFConnection. Whenever I try to sync Machine A back up with it I get a hard kernel panic: Sep 26 11:41:54 ipadca kernel: drbd2: Secondary/Unknown --> Secondary/Primary Sep 26 11:42:00 ipadca kernel: drbd1: [drbd1_worker/3807] sock_sendmsg time expired, ko = 4294967295 Sep 26 11:42:03 ipadca kernel: drbd1: [drbd1_worker/3807] sock_sendmsg time expired, ko = 4294967294 | Sep 26 11:42:21 ipadca kernel: drbd2: [drbd2_receiver/3871] sock_sendmsg time expired, ko = 4294967289 Sep 26 11:42:24 ipadca kernel: drbd1: [drbd1_worker/3807] sock_sendmsg time expired, ko = 4294967287 Sep 26 11:42:24 ipadca kernel: drbd1: Got NegRSDReply. WE ARE LOST. We lost our up-to-date disk. Sep 26 11:42:24 ipadca kernel: Kernel panic: drbd1: Got NegRSDReply. WE ARE LOST. We lost our up-to-date disk. I tried to "drbdadm invalidate all" on Machine A, but had no luck... I notice in the CHANGELOG for drbd 0.7.6 that "'drbdadm invalidate [res]' was not working correct", perhaps that is why I can't invalide my Machine A. Is there some other way I can invalidate the data so the sync happens ok? Is it possible to upgrade my Machine A to 0.7.6 whilst leaving Machine B on 0.7.5 (They both use proto 74, but different api's)???? The big problem is that these machines are about 400km away in the middle of the Australian outback :) Any suggestions would be most appreciated. Cheers Jon -- _____ _____ _____ _____ _____ _____ _____ _____ _____ Institute of Medical and Veterinary Science (IMVS) Jonathan Soong ICTS: Systems Administration and Programming Email: jon.soong at imvs.sa.gov.au Web: http://www.imvs.sa.gov.au Tel: +61 8 82223095