On Tue, Nov 20, 2012 at 5:46 PM, Michael Biebl <bi...@debian.org> wrote: > On 20.11.2012 13:43, Zenaan Harkness wrote: >> On 11/20/12, Zenaan Harkness <z...@freedbms.net> wrote: >>> On 11/20/12, Michael Biebl <bi...@debian.org> wrote: >>>> >>>> You mentioned, that you use some sort of encryption. >>>> Posting more details (fstab, cryptab, etc) might help. >>>> I suspect your problem is related to that. >>> >>> fstab: >>> # / was on /dev/sda5 during installation # about 80GB >>> UUID=e73a71d3-a391-40bc-9d45-55fa72f245c1 / ext4 errors=remount-ro 0 1 >>> # /boot was on /dev/sda3 during installation # about 300MB >>> UUID=75e1d222-c9df-4d10-93de-9da4cf005158 /boot ext2 defaults 0 2 >>> # swap was on /dev/sda6 during installation # about 3GB >>> UUID=25d4ff20-1c78-4e1d-bd2a-2a0060e85f9a none swap sw 0 0 >> >> OK, here's my bad, I ignored /media/usb* entries (which are not >> relevant here), but also ignored two bind mount entries as follows (in >> hindsight, guess I was rushing), which are the "systemd bug" exposing >> culprits: >> >> /zenlocal/zen/justa /home/justa none >> bind,uid=1000,gid=1000,comment=systemd.automount 0 0 >> >> /zenlocal/zen/ /home/justa/zen none >> bind,uid=1000,gid=1000,comment=systemd.automount 0 0 > > This setup is pretty weird, I have to say. Those bind mounts overlap > each other > >> #[This setup provides for me to separate cruft in ~, /home/justa in >> this case, from "my real files/ work files", which is /zenlocal/zen >> bindmounted as ~/zen in this case. >> This setup provides a very simple way to cleanly reinstall, then add a >> few symlinks (after these two bindmounts), and we're off to the >> races...] >> >> Commenting out the second bindmount above sees systemd hang just the same. >> Removing both, systemd starts fine. >> So it's not a "systemd-induced bindmount circular-dependency problem", >> but simply an systemd's inability to handle plain directory (not >> device??) bindmounts. >> >> As before: >> $ systemctl --version >> systemd 44 >> debian >> +PAM +LIBWRAP +AUDIT +SELINUX +SYSVINIT +LIBCRYPTSETUP >> >> debian wheezy, systemd 44-5 >> >> Can someone please forward this to the systemd devs. It appears quite >> easy to test. > > Let's turn this into a bug report then, otherwise this issue will just > be forgotten
I've set up a simple but similar bind-mount and can boot and access/use it (on a base install). th@wheezysysd:~$ id uid=1000(th) gid=100(users) groups=100(users) th@wheezysysd:~$ dpkg -l | grep systemd ii libpam-systemd:amd64 44-5 amd64 system and service manager - PAM module ii libsystemd-daemon0:amd64 44-5 amd64 systemd utility library ii libsystemd-id128-0:amd64 44-5 amd64 systemd 128 bit ID utility library ii libsystemd-journal0:amd64 44-5 amd64 systemd journal utility library ii libsystemd-login0:amd64 44-5 amd64 systemd login utility library ii systemd 44-5 amd64 system and service manager th@wheezysysd:~$ ls -lR .: total 4 drwxr-xr-x 2 th users 4096 Nov 21 04:06 693843 ./693843: total 4 -rw-r--r-- 1 th users 3 Nov 21 04:06 csim th@wheezysysd:~$ touch 693843/buggy th@wheezysysd:~$ ls -lR .: total 4 drwxr-xr-x 2 th users 4096 Nov 21 04:33 693843 ./693843: total 4 -rw-r--r-- 1 th users 0 Nov 21 04:33 buggy -rw-r--r-- 1 th users 3 Nov 21 04:06 csim th@wheezysysd:~$ root@wheezysysd:~# ls -ld /misc1/ drwxr-xr-x 3 root root 4096 Nov 21 03:47 /misc1/ root@wheezysysd:~# ls -lR /misc1/ /misc1/: total 4 drwxr-xr-x 2 th users 4096 Nov 21 04:33 misc2 /misc1/misc2: total 4 -rw-r--r-- 1 th users 0 Nov 21 04:33 buggy -rw-r--r-- 1 th users 3 Nov 21 04:06 csim root@wheezysysd:~# cat /etc/fstab UUID=8b05b721-ac9f-4453-b00b-12615f984276 / ext4 errors=remount-ro 0 1 UUID=3a57c4cf-143a-4632-9dde-37a6ba9d864f none swap sw 0 0 /misc1/misc2 /home/th/693843 none bind,uid=1000,gid=100,comment=systemd.automount 0 0 root@wheezysysd:~# -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=sx_vetsgctovyf11wfkz2udbhp7qgtcat+ugx_yfxg...@mail.gmail.com