Re: systemd hangs on fstab directory bindmount

2012-11-21 Thread Tom H
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:amd6444-5  amd64
   systemd login utility library
ii  systemd44-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



Re: systemd hangs on fstab directory bindmount

2012-11-21 Thread Zenaan Harkness
OK, speaking of gooses, I've discovered the goose is me. I've just
spent an hour testing and retesting, trying to recreate the problem!
Quite exasperating. So I went back to previous versions of fstab,
finally digging up an old internal IDE drive from a previous laptop,
to find what I'd somehow changed and hadn't realised I'd changed.

So:
I use plug-in USB drives here and there (especially when rebuilding/
rescuing my workstation or [re]installing a box).

To this end, I create fstab entries on occasion for my USB backup
drive, in particular, normally with an auto mount option to speed up
my reboot and rescue cycles.

My brown paper bag moment (I was evidently not quite as rigorous in my
one-change-at-a-time methodology as I thought I was) is my failure to
add noauto or comment=systemd.automount to my USB rescue
automount.

Twice now I've discarded entries in the thought that they were not
relevant. This is not so cool, but anyway, problem found.

Bit too late now, but I ought to have advised myself to attach a full
fstab file, and someone probably would have seen it straight away.

Thank you for assisting me on my wild goose chase. I'm now found so we
can close this bug...

Now, to discover if fstab somehow applies to the ls problem on my eee.

Thanks
Zenaan


-- 
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/caosgnssrmmat6c939yt7lj92c7gkibp4oh2xvywrpzkxfyv...@mail.gmail.com



Re: systemd hangs on fstab directory bindmount

2012-11-21 Thread Zenaan Harkness
PS, This is still just an assumption, as I don't have a photographic
memory of every command I ran over the last week, but it's the only
way I can recreate something that appears similar/same as I
experienced before, so it seems to me, the most likely possibility.


-- 
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/caosgnst1dmftgro-dnkgmcmk5sughdecke_sevf+tpwtvnv...@mail.gmail.com



Re: Bug#693843: systemd hangs on fstab directory bindmount

2012-11-21 Thread Tollef Fog Heen
]] Zenaan Harkness 

 My brown paper bag moment (I was evidently not quite as rigorous in my
 one-change-at-a-time methodology as I thought I was) is my failure to
 add noauto or comment=systemd.automount to my USB rescue
 automount.

Ooops. :-)

Closing this bug, then.  Thanks for tracking it down.

Cheers,
-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are


-- 
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/878v9uce5a@xoog.err.no



Re: Bug#693843: systemd hangs on fstab directory bindmount

2012-11-21 Thread Zenaan Harkness
Is there a ways for this to be slightly less bite-ing for systemd
newbies such as myself?
Perhaps a timeout of just 20s, plus a big loud syslog msg or something
rather than a 2 to 5 minute hang?
Just a thought, to assist the impatient who might otherwise be lured
into systemd land :)
Kind regards
Zenaan


On 11/22/12, Tollef Fog Heen tfh...@err.no wrote:
 ]] Zenaan Harkness

 My brown paper bag moment (I was evidently not quite as rigorous in my
 one-change-at-a-time methodology as I thought I was) is my failure to
 add noauto or comment=systemd.automount to my USB rescue
 automount.

 Ooops. :-)

 Closing this bug, then.  Thanks for tracking it down.

 Cheers,
 --
 Tollef Fog Heen
 UNIX is user friendly, it's just picky about who its friends are



-- 
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/caosgnsrk_zxh8po0k75kxjqus_4e409-ngf6sa5mb32fmzz...@mail.gmail.com



SOLVED - systemd hangs on fstab directory bindmount - was Re: systemd intermittent startup

2012-11-20 Thread Zenaan Harkness
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 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.

Finally, a workaround - I guess just move my directories manually into
place in order to avoid the bindmounts. I think I was doing the
bindmounts because at some point my real home was on a different
partition. Certainly I don't like the destop of the day trashing my
real home.

Either way, systemd's hand seems unfortunate.

TIA
Zenaan


-- 
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/CAOsGNSSdZrqHEA=YpAAAJ33Qtts-AcTZsoEJkX_-Pk=o-o6...@mail.gmail.com



systemd hangs on fstab directory bindmount

2012-11-20 Thread Michael Biebl
Package: systemd
Version: 44-5
Control: submitter -1 z...@freedbms.net

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


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Re: systemd hangs on fstab directory bindmount

2012-11-20 Thread Zenaan Harkness
Thank you very much. Appreciated. I don't mind goose chases if a goose
is caught, myself or otherwise :)

For reference:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693843

Kind regards
Zenaan


-- 
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/caosgnssj_xdxqyq1uzmjcgrorfguprhc8hzjjeacvsrrhoi...@mail.gmail.com