Bug 69335 - Systemd handles bind mounts in a way that is incompatible to the SysV-style init
Summary: Systemd handles bind mounts in a way that is incompatible to the SysV-style init
Status: NEW
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-13 19:15 UTC by ggb12.10.Toranaga-San
Modified: 2013-09-13 19:15 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ggb12.10.Toranaga-San 2013-09-13 19:15:01 UTC
Hello all,

I have noticed the following problem using bind mounts: I have an encrypted disk which I mount at "/media/crypt". The disk does in particular contain my home directory. Since I would like to access my home via "/home" I used a bind mount like so:

mount -o bind /media/crypt/home/ /home

After that, "ls /home" gives me the home directory "username". To make this permanent I added

/media/crypt/home       /home         bind    defaults,bind            0 0

to my /etc/fstab. Unfortunately once I restart my system and type "ls /home" I get a new "home" directory, in total "/home/home/username" instead of "/home/username". So apparently systemd mounts "/media/crypt" on the mountpoint "/home" instead of binding "/home" to "/media/crypt/home".


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.