[systemd-bugs] [Bug 69335] New: Systemd handles bind mounts in a way that is incompatible to the SysV-style init

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=69335

          Priority: medium
            Bug ID: 69335
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: Systemd handles bind mounts in a way that is
                    incompatible to the SysV-style init
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: ggb12.10.Toranaga-San at spamgourmet.com
          Hardware: x86 (IA32)
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

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".

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20130913/89a50855/attachment.html>