Hide Forgot
Description of problem: Some partitions are mounted several times during boot Version-Release number of selected component (if applicable): systemd-26-1.fc15.x86_64 How reproducible: Add the following line in /etc/fstab: /var/tmp /tmp none bind,nosuid,nodev,noexec 0 0 Reboot. Steps to Reproduce: 1. Add line "/var/tmp /tmp none bind,nosuid,nodev,noexec 0 0" to /etc/fstab 2. Reboot 3. Login and run mount Actual results: # mount | grep -vE '^(/sys|/proc|udev|devpts|tmpfs|selinuxfs|tmpfs|cgroup|systemd-1)' /dev/sda2 on / type ext3 (rw,relatime,seclabel,errors=continue,user_xattr,acl,barrier=0,data=ordered) /dev/sda2 on /var/tmp type ext3 (rw,relatime,seclabel,errors=continue,user_xattr,acl,barrier=0,data=ordered) /dev/sda1 on /boot type ext3 (rw,relatime,seclabel,errors=continue,user_xattr,acl,barrier=0,data=ordered) /dev/sda6 on /home type ext4 (rw,relatime,seclabel,barrier=1,data=ordered) /dev/sda5 on /tmp type ext4 (rw,nosuid,nodev,noexec,relatime,seclabel,barrier=1,data=ordered) /dev/sda5 on /var/tmp type ext4 (rw,nosuid,nodev,noexec,relatime,seclabel,barrier=1,data=ordered) Expected results: The following line shoud be printed by running mount: /tmp on /var/tmp type none (rw,noexec,nosuid,nodev,bind) Additional info: /dev/sda3 is mounted 2 times (sometimes 3 times - 2 times in /var/tmp). I can understand the that /tmp on /var/tmp type none (rw,noexec,nosuid,nodev,bind) is now /dev/sda5 on /var/tmp type ext4 (rw,nosuid,nodev,noexec,relatime,seclabel,barrier=1,data=ordered) but how about /dev/sda2? Please also see #701176.
Do you have the sandbox package installed?
Sandbox was disabled but I removed the package anyway. # rpm -ev policycoreutils-2.0.86-7.fc15.x86_64 # reboot ... # mount | grep -vE '^(/sys|/proc|udev|devpts|tmpfs|selinuxfs|tmpfs|cgroup|systemd-1)' /dev/sda2 on / type ext3 (rw,relatime,seclabel,errors=continue,user_xattr,acl,barrier=0,data=ordered) /dev/sda2 on /var/tmp type ext3 (rw,relatime,seclabel,errors=continue,user_xattr,acl,barrier=0,data=ordered) /dev/sda1 on /boot type ext3 (rw,relatime,seclabel,errors=continue,user_xattr,acl,barrier=0,data=ordered) /dev/sda6 on /home type ext4 (rw,relatime,seclabel,barrier=1,data=ordered) /dev/sda5 on /tmp type ext4 (rw,nosuid,nodev,noexec,relatime,seclabel,barrier=1,data=ordered) /dev/sda5 on /var/tmp type ext4 (rw,nosuid,nodev,noexec,relatime,seclabel,barrier=1,data=ordered)
It's seems that /etc/mtab is a symlink to /proc/mounts. So the lines containing /dev/sda5 are correct (I was fooled because of the missing bind option and the fact that /dev/sda5 appears on both lines but that's correct in /proc/mount). Still, I found something more wierd: Unmount /var/tmp (2 times) and /tmp until nothing is mounted under these directories. Did a ls -la /tmp and .ICE-unix, .Test-unix, .X11-unix, .XIM-unix, .font-unix apears to be inside. rm -rf those directories. Reboot. Login and unmount again /var/tmp (2 times) and /tmp. .ICE-unix, .Test-unix, .X11-unix, .XIM-unix, .font-unix directories are there again. systemd-tmpfiles-setup.service create those directories but that's suppose to happen after /tmp is mounted (local-fs.target).
Another problem. If the entry in fstab is not UUID=... but /dev/sdaX... systemd-fsck is not called for that partition (I had to reformat /dev/sda5 partition and I was lazy to put the new UUID back). When I put back the UUID, systemd-fsck is called for /dev/sda5 and now I can see two new lines: Started /var/tmp Started /tmp So I think /var/tmp is mounted before /tmp (bind - /dev/sda2), and then /tmp is mounted and then again /var/tmp is mounted (bind - /dev/sda5).
$ mount | grep -vE \ '^(/sys|proc|udev|devpts|tmpfs|selinuxfs|tmpfs|cgroup|systemd-1)' /dev/mapper/vg_nemesis-lv_root on / type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime) /dev/sda1 on /boot type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered) /dev/mapper/vg_data-lv_data on /data type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered) /dev/mapper/vg_nemesis-lv_home on /home type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered) /dev/mapper/vg_nemesis-lv_log on /var/log type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered) /dev/mapper/vg_nemesis-lv_tmp on /tmp type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered) /dev/mapper/vg_nemesis-lv_tmp on /tmp type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered) /dev/mapper/vg_nemesis-lv_root on /var/tmp type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered) /dev/mapper/vg_nemesis-lv_home on /home type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) NFS share are also tried twice (but fail gracefully).
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This bug is not rawhide specific, Fedora 15 systemd is also impacted.
Does it still happen with current updates? If yes, please attach /etc/fstab and /proc/self/mountinfo.
No.
Sorry. No, it does not happen anymore. But loop mount still look (just look) strange when running mount/df/etc.