Hide Forgot
Created attachment 519343 [details] Output of mount command Description of problem: I get very strange output of a "mount" command. For example if i trust this output then my /tmp should be mounted twice, partition that supposed to be mounted as root is mounted under "/" and under "/var/tmp" at the same time. Very disturbing picture, while system works just fine, i'm glad that this is just my laptop and not production machine, otherwise i would literally freak out. I have folowing set up: 2 SSDs + 1HDD. Only physical partition is /dev/sda1 on SSD mounted as /boot. Rest of SSDs is one physical volume for LVM. Here i have few logical volumes: / /tmp (encrypted, enplanes luks mentioning in output) /home (encrypted, enplanes luks mentioning in output) Couple more LVs that are not mounted (only when needed) HDD is physical volume for LVM as well. Couple of LVs, only one is mounted constantly Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: I can't even understand what in there Expected results: Just mount points (partitions) listed that are actually mounted Additional info: Please see attachment for "mount" output
Can you paste the output of 'cat /proc/mounts' and tell us which version of util-linux you have installed?
Created attachment 519347 [details] Output of /proc/mounts
And util-linux: util-linux-2.19.1-1.4.fc15.x86_64
OK, something actually mounted a variety of devices twice, so mount is just dutifully displaying what happened. It doesn't really appear to be a kernel bug. I think systemd does this, but I can't recall what the reasons are exactly. Hopefully Lennart can explain.
Please attach the output of /proc/self/mountinfo. The old /proc/mounts doesn't show what we need to know today.
You probably have the selinux sandbox installed, right? It creates a couple of bind mounts. Consider removing it and the bind mounts will go away...
Hi Lennart, I do not have sandbox installed (policycoreutils-sandbox - this what you mean right?). I have attached mountinfo output.
Created attachment 519356 [details] output of a /proc/self/mountinfo
45 22 253:9 / /tmp rw,relatime 46 45 253:9 / /tmp rw,relatime The second line looks like an additional bind mount on top of the first one. Having /tmp and /home duplicated might be related to selinux or pam_namespace: https://bugzilla.redhat.com/show_bug.cgi?id=701176#c9 https://bugzilla.redhat.com/show_bug.cgi?id=698793#c14
might be the "sandbox" service? $ chkconfig --list sandbox
Hi Harald, sandbox was indeed "on" , which i thought was strange considering i do not have policycoreutils-sandbox installed on my machine. But anyway i turned it "off" but output of mount dos't look any better,
Im so sorry that i can't edit my comments here, but i was to hasty to comment. When i closely examined output i realized that it WAS looking better then before, for example it didn't show me "/" being mounted twice. I'll upload attachment in a minute.
Created attachment 520095 [details] Output of mount command after sanbox is set to off I have noticed that after setting sandbox to off (chkconfig sanbox off) i got mount output with one "/", one "/home" and one "/tmp" entries, which is nice.
rpm -qf /etc/rc.d/init.d/sandbox will tell you that sandbox is in "polycoreutils", not "policycoreutils-sandbox". Closing, since this is expected behaviour and has little to do with systemd.
Excuse me, What is expected behavior? Is installing F15 and getting from "mount" command that something very strange is going with your system can be considered as expected? Or maybe you mean that is expected from me - a F15 user, to know that it SElinux (sandbox) can be the reason why system gives faulty information. And i should know that first thing i have to do is turn off sandbox daemon. What is exactly expected behavior? And why bug is closed? Is problem solved? Or maybe turning of sandbox daemon is the solution to this problem. If yes, why it is installed and activated from the start?
The mount command is showing bind mounts. Sandbox is used for pam_namespace and requires bind mounts to be setup. pam_namepspace has been fixed to not require this any longer and will be fixed in F16.
Thank you Daniel. This clears up for me.