[Bug 443321] [NEW] drbd devices not automatically mounted via /etc/fstab even witn _netdev

Ari Mujunen Ari.Mujunen at tkk.fi
Mon Oct 5 17:45:51 UTC 2009


Public bug reported:

Both in jaunty-desktop(i386/amd64) and jaunty-server the drbd subsystem
is started by '/etc/rc2.d/S70drbd' script which does not interact well
with the network-device-based filesystems being mounted by '/etc/network
/if-up.d/mountnfs' after network devices have all come up (a typical
system will reach '/etc/rc2.d/S70drbd start' much before than network
will be up).

I'm not sure if this is really a "solid" solution but since calling '/etc/init.d/drbd start' again after it has already been called seems quite benign, I have just added the script '/etc/network/if-up.d/drbd-start' (note the naming alphabetically _before_ 'mountnfs' in that directory) with the contents:
-----
#! /bin/sh
/etc/init.d/drbd start
-----
and I have labeled my drbd mounts in /etc/fstab with the '_netdev' option:
-----
/dev/drbd1 /home           ext3	 _netdev,relatime                 0       2
/dev/drbd2 /local          ext3	 _netdev,relatime                 0       3
-----
This causes the "if-up" system (regardless whether it is NetworkManager-originated or due to interfaces listed in /etc/network/interfaces) to first bring up drbd devices and then mount the network-dependent drbd devices.  Works beautifully for me, in the simple situation where I don't want to use an HA manager to shift the primary/secondary roles around, I just want my "main" computer to be primary and mount the devices by default and the "secondary" to skip all mounting.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: drbd8-utils 2:8.3.0-1ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: drbd8
Uname: Linux 2.6.28-15-generic x86_64

** Affects: drbd8 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug

-- 
drbd devices not automatically mounted via /etc/fstab even witn _netdev
https://bugs.launchpad.net/bugs/443321
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs




More information about the universe-bugs mailing list