Bug#816912: systemd: Can't make non-shared bind mounts in fstab

[Rogier]

Package: systemd
Version: 215-18
Severity: normal

Dear Maintainer,

For some time, I have been using a distinct set of bind mounts of the system
directory tree (i.e. /, /usr, /var) for backup purposes. Unfortunately,
it seems that systemd now makes bind mounts shared by default, so that /tmp,
/home etc. etc. end up being mounted as well, which makes it impossible to
make a backup of just a subset of my filesystem tree.

The only 'solution' I have found, is that applications that need non-shared
bind mounts should be adapted. However, the application in question here is
systemd itself...

Please add an fstab flag (or so) that directs systemd to create a non-shared
bind mount.

Kind regards,

Rogier.

/etc/fstab:

-------------------------------------------
# <file system> <mount point>	<type>	<options>	<dump>	<pass>
/dev/data/root		/				ext4	errors=remount-ro,relatime 0 1
/dev/data/boot		/boot			ext4	relatime	0 2
/dev/data/home		/home			ext4	relatime	0 2
/dev/data/tmp			/tmp				ext4	relatime	0 2
/dev/data/usr			/usr				ext4	relatime	0 2
/dev/data/local		/usr/local		ext4	relatime	0 2
/dev/data/var			/var				ext4	relatime	0 2
/dev/data/swap		none				swap	sw		0 0
/dev/data/scratch		/mnt/scratch		ext4	relatime	0 2
/dev/data/media		/home/rogier/media	ext4	relatime	0 2
/dev/data/wheezy32		/mnt/wheezy32		ext4	ro,relatime,noauto	0 2
/dev/data/wheezy64		/mnt/wheezy64		ext4	ro,relatime,noauto	0 2
/dev/data/jessie32		/mnt/jessie32		ext4	ro,relatime,noauto	0 2
/dev/data/jessie64		/mnt/jessie64		ext4	ro,relatime,noauto	0 2
/dev/data/stretch32	/mnt/stretch32	ext4	ro,relatime,noauto	0 2
/dev/data/stretch64	/mnt/stretch64	ext4	ro,relatime,noauto	0 2
/dev/backup/backup		/var/lib/backuppc	ext4	relatime,noauto	0 2
/dev/data/postgresql	/var/lib/postgresql	ext4	relatime	0 2
/dev/data/deb-cache	/var/cache/apt/archives	ext4	relatime	0 2

# Loopback mounts of system filesystems for backup - allows using rsync without need to
# exclude all unwanted mounts on the command-line (which is unmaintainable)
/			/export/sys			none	rw,bind		0 0
/usr			/export/sys/usr		none	ro,bind		0 0
/var			/export/sys/var		none	rw,bind		0 0
/boot		/export/sys/boot		none	ro,bind		0 0
/usr/local	/export/sys/usr/local	none	ro,bind		0 0
-------------------------------------------

-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  acl             2.2.52-2
ii  adduser         3.113+nmu3
ii  initscripts     2.88dsf-59.2
ii  libacl1         2.2.52-2
ii  libaudit1       1:2.4.2-1
ii  libblkid1       2.26.2-6
ii  libc6           2.19-18
ii  libcap2         1:2.24-9
ii  libcap2-bin     1:2.24-9
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20     1.6.3-2
ii  libkmod2        20-1
ii  liblzma5        5.1.1alpha+20120614-2+b3
ii  libpam0g        1.1.8-3.1
ii  libselinux1     2.3-2+b1
ii  libsystemd0     215-18
ii  mount           2.26.2-6
ii  sysv-rc         2.88dsf-59.2
ii  udev            215-18
ii  util-linux      2.26.2-6

Versions of packages systemd recommends:
ii  dbus            1.8.18-1
ii  libpam-systemd  215-18

Versions of packages systemd suggests:
pn  systemd-ui  <none>

-- no debconf information

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160306/0e0966c8/attachment.html>