Comment 5 for bug 443321

I mentioned that this affects jaunty-server, too, but I forgot to describe how. By default the server edition doesn't rely on "if-up.d" mechanism but relies on /etc/rcS.d/S40networking to bring up what is defined in /etc/network/interfaces and then gives /etc/rcS.d/S45mountnfs.sh a chance to do NFS mounts and mounts labeled with '_netdev' mount option. The default startup of drbd in /etc/rc2.d/S70drbd comes again much later in the sequence.

I originally planned to enter this as a "Wishlist" item and not a bug (but ubuntu-bug didn't let me do that) since I fully understand the complications in setups where drbd device sync / pri/sec / mounts must be handled by a HA system like heartbeat. I was kind of wondering if there were a safe way to enable the simple functionality for the cases where /etc/fstab mounts with '_netdev' (only on one machine, the "primary one") could work "out of the box"? I would expect HA cases not to rely on /etc/fstab in any case, though there might be other '_netdev' mounts. Checking for 'drbd.*_netdev' mount lines in /etc/fstab, maybe?

In any case, I'm really happy with drbd functionality and robustness in my current setup where I run a three-disk raid0 in my desktop as '/home' and have drbd mirroring that onto a single 2TB disk in a small server. It has survived r8169 driver timeouts, r8168 driver giving bad data (md5 checksums enabled!), any network problem or up/down sequence I've thrown at it and I have _never_ had to reboot either machine because of drbd, it has always "obeyed" the 'drbdadm' and not "locked up". And the performance is great! :-)
I hope you can make the transition to DKMS for the kernel module (not being included in the mainline Ubuntu kernel anymore) a smooth experience!