[systemd-devel] Multiple mounts of same device after boot

[Oliver Maurhart]

#!/bin/hi *

I'm pretty sure it's a PEBCAK but I don't get it. I do have multiple 
mounts of the same device over and over after boot and I don't know why. 
Please could someone help me out.

Here some specs:

root at semirhage ~ # mount | grep sd | sort
/dev/sda5 on / type ext4 (rw)
/dev/sdb1 on /home/data type ext4 (rw)
/dev/sdb1 on /home/data type ext4 (rw)
/dev/sdb1 on /home/data type ext4 (rw)
/dev/sdb1 on /home/data type ext4 (rw)
/dev/sdb1 on /home/data type ext4 (rw)
/dev/sdb1 on /home/data type ext4 (rw)
/dev/sdb1 on /home/data type ext4 (rw)
/dev/sdb1 on /home/data type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw)
/dev/sdc1 on /home type ext4 (rw,commit=0)
nfsd on /proc/fs/nfsd type nfsd (rw,nodev,noexec,nosuid)


Interestingly all mount points BUT "/" are mounted more then one.

root at semirhage ~ # systemctl --version
systemd 207
+PAM +LIBWRAP -AUDIT -SELINUX +IMA -SYSVINIT -LIBCRYPTSETUP -GCRYPT +ACL -XZ

root at semirhage ~ # grep sd /etc/fstab
/dev/sda5                           /                   ext4 
defaults        1 1
/dev/sda6                           none                    swap 
         sw                  0 0
/dev/sdc1                   /home           ext4        defaults    0 0
/dev/sdb1                   /home/data      ext4        defaults    0 0

root at semirhage ~ # systemctl --all | grep mount
mnt-win7.automount         loaded active   waiting   mnt-win7.automount
proc-sys..._misc.automount loaded active   waiting   Arbitrary 
Executable File Formats File System Automount Point
-.mount                    loaded active   mounted   /
dev-hugepages.mount        loaded active   mounted   Huge Pages File System
dev-mqueue.mount           loaded active   mounted   POSIX Message Queue 
File System
home-data.mount            loaded active   mounted   /home/data
home.mount                 loaded active   mounted   /home
mnt-win7.mount             loaded inactive dead      /mnt/win7
proc-sys...nfmt_misc.mount loaded inactive dead      Arbitrary 
Executable File Formats File System
sys-fs-f...nnections.mount loaded active   mounted   FUSE Control File 
System
sys-kernel-config.mount    loaded active   mounted   Configuration File 
System
sys-kernel-debug.mount     loaded active   mounted   Debug File System
tmp.mount                  loaded active   mounted   Temporary Directory
var-lock.mount             loaded inactive dead      Lock Directory
var-run.mount              loaded inactive dead      Runtime Directory
systemd-remount-fs.service loaded active   exited    Remount Root and 
Kernel File Systems
umount.target              loaded inactive dead      Unmount All Filesystems

root at semirhage ~ # journalctl -x -b -l | grep mount
Sep 25 09:26:06 localhost kernel: EXT3-fs (sda5): error: couldn't mount 
because of unsupported optional features (40)
Sep 25 09:26:06 localhost kernel: EXT2-fs (sda5): error: couldn't mount 
because of unsupported optional features (40)
Sep 25 09:26:06 localhost kernel: EXT4-fs (sda5): mounted filesystem 
with ordered data mode. Opts: (null)
Sep 25 09:26:06 localhost systemd[1]: /etc/mtab is not a symlink or not 
pointing to /proc/self/mounts. This is not supported anymore. Please 
make sure to replace this file by a symlink to avoid incorrect or 
misleading mount(8) output.
Sep 25 09:26:06 localhost systemd[1]: Starting Arbitrary Executable File 
Formats File System Automount Point.
Sep 25 09:26:06 localhost systemd[1]: Set up automount Arbitrary 
Executable File Formats File System Automount Point.
-- Subject: Unit tmp.mount has begun with start-up
-- Unit tmp.mount has begun starting up.
Sep 25 09:26:06 localhost systemd[1]: tmp.mount: Directory /tmp to mount 
over is not empty, mounting anyway.
-- The directory /tmp is specified as the mount point (second field in
-- This does not interfere with mounting, but the pre-exisiting files in
-- this directory become inaccessible. To see those over-mounted files,
-- please manually mount the underlying file system to a secondary
Sep 25 09:26:06 localhost systemd[1]: Starting mnt-win7.automount.
-- Subject: Unit mnt-win7.automount has begun with start-up
-- Unit mnt-win7.automount has begun starting up.
Sep 25 09:26:06 localhost systemd[1]: Set up automount mnt-win7.automount.
-- Subject: Unit mnt-win7.automount has finished start-up
-- Unit mnt-win7.automount has finished starting up.
-- Subject: Unit dev-mqueue.mount has finished start-up
-- Unit dev-mqueue.mount has finished starting up.
-- Subject: Unit dev-hugepages.mount has finished start-up
-- Unit dev-hugepages.mount has finished starting up.
-- Subject: Unit sys-kernel-debug.mount has finished start-up
-- Unit sys-kernel-debug.mount has finished starting up.
-- Subject: Unit tmp.mount has finished start-up
-- Unit tmp.mount has finished starting up.
-- Subject: Unit sys-kernel-config.mount has begun with start-up
-- Unit sys-kernel-config.mount has begun starting up.
-- Subject: Unit sys-fs-fuse-connections.mount has begun with start-up
-- Unit sys-fs-fuse-connections.mount has begun starting up.
-- Subject: Unit sys-fs-fuse-connections.mount has finished start-up
-- Unit sys-fs-fuse-connections.mount has finished starting up.
-- Subject: Unit sys-kernel-config.mount has finished start-up
-- Unit sys-kernel-config.mount has finished starting up.
Sep 25 09:26:08 localhost systemd[1]: Starting Remount Root and Kernel 
File Systems...
-- Subject: Unit systemd-remount-fs.service has begun with start-up
-- Unit systemd-remount-fs.service has begun starting up.
Sep 25 09:26:08 localhost kernel: EXT4-fs (sda5): re-mounted. Opts: (null)
Sep 25 09:26:08 localhost systemd[1]: Started Remount Root and Kernel 
File Systems.
-- Subject: Unit systemd-remount-fs.service has finished start-up
-- Unit systemd-remount-fs.service has finished starting up.
-- Subject: Unit var-lock.mount has finished start-up
-- Unit var-lock.mount has finished starting up.
-- Subject: Unit var-run.mount has finished start-up
-- Unit var-run.mount has finished starting up.
-- Subject: Unit home.mount has begun with start-up
-- Unit home.mount has begun starting up.
Sep 25 09:26:10 localhost kernel: EXT4-fs (sdc1): mounted filesystem 
with ordered data mode. Opts: (null)
-- Subject: Unit home.mount has finished start-up
-- Unit home.mount has finished starting up.
-- Subject: Unit home-data.mount has begun with start-up
-- Unit home-data.mount has begun starting up.
Sep 25 09:26:10 localhost kernel: EXT4-fs (sdb1): warning: maximal mount 
count reached, running e2fsck is recommended
Sep 25 09:26:10 localhost kernel: EXT4-fs (sdb1): mounted filesystem 
with ordered data mode. Opts: (null)
-- Subject: Unit home-data.mount has finished start-up
-- Unit home-data.mount has finished starting up.
-- Subject: Unit var-run.mount has finished start-up
-- Unit var-run.mount has finished starting up.



Thx for any hint.
Dyle