Hide Forgot
Description of problem: I've setup my EeePC using encrypted LVM group. Swap is encrypted using random keys and I want /tmp to be on an tmpfs partition. After the system is up, "mount" tells me that /tmp has been mounted twice. I suspect systemd is responsible for this behaviour, but without any proof... It's really hard to debug this heap of config files in an completely new (to me) subsystem... Version-Release number of selected component (if applicable): kernel-2.6.38.8-32.fc15.i686 systemd-26-4.fc15.i686 How reproducible: Replace the mount for /tmp in /etc/fstab with the following one tmpfs /tmp tmpfs size=200m,mode=1777 0 0 then reboot. Actual results: /tmp is mounted twice: # mount | grep /tmp tmpfs on /tmp type tmpfs (rw,relatime,size=204800k) tmpfs on /tmp type tmpfs (rw,relatime,size=204800k) /dev/mapper/vg_chepre-root on /var/tmp type ext4 (rw,relatime,barrier=1,data=ordered) Expected results: /tmp should be mounted only once.
can you paste the contents of /proc/self/mounts please?
Created attachment 510165 [details] /proc/self/mounts Of course, here they are.
Hmm, and could you also paste your full /etc/fstab please?
Created attachment 510340 [details] /etc/fstab Here is all of /etc/fstab.
The /proc/self/mounts also shows a duplicate /home mount and a /var/tmp mount (which is not even in fstab). This looks like the bind mounts done by the sandbox service. See if disabling it helps: chkconfig sandbox off
Oh yes, it did help. The mount table looks much cleaner now. And /tmp mount apears only once. Thank you.
Closing this bug, because systemd did nothing wrong here. For an explanation of the sandbox service see for instance: http://lists.fedoraproject.org/pipermail/users/2011-May/398310.html