[DRBD-user] drbd crashed under 2.6.13 and left a resource hanging in secondary state

Maurice Volaski mvolaski at aecom.yu.edu
Wed Mar 29 03:14:26 CEST 2006

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

The primary is running drbd 0.7.17 under kernel 2.6.13 and it 
crashed. Having drbd crash is not that unusual, but what is unusual 
was the heartbeat/drbd failover behavior.

The secondary was still running drbd 0.7.15. And when it took over, 
every resource on it but one became primary. One was still left in 
secondary state! So naturally heartbeat couldn't mount it. I 
restarted the primary and allowed drbd to sync and watched it weirdly 
sending all data from the secondary computer (acting as primary) to 
the true primary (the one that crashed) except for this resource that 
was left hanging, which synced in the reverse direction! When it was 
done, I ran fsck to be sure (underlying filesystem is ext3) and it 
checked fine.

How could that have happened? What would have happened had the true 
primary not been available?

Maurice Volaski, mvolaski at aecom.yu.edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University

More information about the drbd-user mailing list