Bug#681884: Same problem with schroot 1.6.8-1
Erik de Castro Lopo wrote: Yes, I was using systemd on the machine where this is a problem and *not* using systemd on the machine where there is no problem. On the machine that was having the problem I un-installed systemd and the problem disappeared. This is definitely systemd related. Can anyone figure out from what we know so far if this is an schroot but or a systemd bug? If someone can give me a gentle nudge in the right direction I'm willing to invest some time on this because I really do need this bug fixed. Cheers, Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681884: Same problem with schroot 1.6.8-1
Erik de Castro Lopo wrote: Can anyone figure out from what we know so far if this is an schroot but or a systemd bug? If someone can give me a gentle nudge in the right direction I'm willing to invest some time on this because I really do need this bug fixed. Now I can't even re-produce this bug. I'm still using schroot 1.6.8-1 with systemd 204-8 but upgrading something else (no clue what) seems to have fixed. I have schroot working properly again. I'm very happy. If no one else can re-produce this then the bug should be closed. Cheers, Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681884: [buildd-tools-devel] Bug#681884: Same problem with schroot 1.6.8-1
On Sat, Apr 05, 2014 at 09:25:33PM +1100, Erik de Castro Lopo wrote: Erik de Castro Lopo wrote: Can anyone figure out from what we know so far if this is an schroot but or a systemd bug? If someone can give me a gentle nudge in the right direction I'm willing to invest some time on this because I really do need this bug fixed. Now I can't even re-produce this bug. I'm still using schroot 1.6.8-1 with systemd 204-8 but upgrading something else (no clue what) seems to have fixed. I have schroot working properly again. I'm very happy. If no one else can re-produce this then the bug should be closed. There's definitely a bug here, in fact two bugs: - systemd shouldn't be breaking things by altering defaults that have worked for over a decade, thereby breaking every user of mount --bind. This is utterly wrong. mount --bind is in widespread use and, like it or not, there are thousands of programs and scripts that, unwittingly or not, depend upon the existing kernel default. - schroot should be able to cope with the default being changed; there's a patch to do this; it just needs updating to work on non-Linux systems and I'll apply it. The bits of the existing patch just need wrapping in if(Linux) conditionals. I'll fix this in schroot of course, as I have for many minor portability issues over the years. I do have some rather bad things to say about systemd's attitudes here, but I'll refrain from it here. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681884: [buildd-tools-devel] Bug#681884: Same problem with schroot 1.6.8-1
Roger Leigh wrote: Could this have something to do with the fact that I have /home as a separate ext4 partition and that the chroots are kept in under /home ? I'm not sure. I wouldn't think so, but I haven't tried it myself. Have you seen the other bug where systemd breaks bind mounting? Are you using sytemd? Yes, I was using systemd on the machine where this is a problem and *not* using systemd on the machine where there is no problem. On the machine that was having the problem I un-installed systemd and the problem disappeared. This is definitely systemd related. Cheers, Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681884: [buildd-tools-devel] Bug#681884: Same problem with schroot 1.6.8-1
On Tue, Mar 11, 2014 at 11:21:29AM +1100, Erik de Castro Lopo wrote: Erik de Castro Lopo wrote: I see two mount points for every one mount point I expect. Eg: /var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/home/chroot/sid64/tmp and /home/chroot/sid64/home/chroot/sid64/tmp The second one seems wrong. Could this have something to do with the fact that I have /home as a separate ext4 partition and that the chroots are kept in under /home ? I'm not sure. I wouldn't think so, but I haven't tried it myself. Have you seen the other bug where systemd breaks bind mounting? Are you using sytemd? Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681884: Same problem with schroot 1.6.8-1
Erik de Castro Lopo wrote: I see two mount points for every one mount point I expect. Eg: /var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/home/chroot/sid64/tmp and /home/chroot/sid64/home/chroot/sid64/tmp The second one seems wrong. Could this have something to do with the fact that I have /home as a separate ext4 partition and that the chroots are kept in under /home ? Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681884: Same problem with schroot 1.6.8-1
Erik de Castro Lopo wrote: On the machine that displays this problem I have a amd64 Sid chroot called sid64. If I run it using 'schroot -c sid64' and immediately exit I get: If I just start the chroot and run mount I see: /dev/sda4 on /var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1 type ext4 (rw,relatime,data=ordered) proc on /var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/proc type proc (rw,nosuid,nodev,noexec,relatime) proc on /home/chroot/sid64/proc type proc (rw,nosuid,nodev,noexec,relatime) sysfs on /var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/sys type sysfs (rw,nosuid,nodev,noexec,relatime) sysfs on /home/chroot/sid64/sys type sysfs (rw,nosuid,nodev,noexec,relatime) udev on /var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=1006767,mode=755) udev on /home/chroot/sid64/dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=1006767,mode=755) devpts on /var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) devpts on /home/chroot/sid64/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) /dev/sda4 on /var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/home type ext4 (rw,relatime,data=ordered) /dev/sda4 on /home/chroot/sid64/home type ext4 (rw,relatime,data=ordered) /dev/disk/by-uuid/5065a2f9-ec31-4a10-8992-ccda124f2d26 on /var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/tmp type ext4 (rw,relatime,errors=remount-ro,data=ordered) /dev/disk/by-uuid/5065a2f9-ec31-4a10-8992-ccda124f2d26 on /home/chroot/sid64/tmp type ext4 (rw,relatime,errors=remount-ro,data=ordered) /dev/disk/by-uuid/5065a2f9-ec31-4a10-8992-ccda124f2d26 on /var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/home/chroot/sid64/tmp type ext4 (rw,relatime,errors=remount-ro,data=ordered) /dev/disk/by-uuid/5065a2f9-ec31-4a10-8992-ccda124f2d26 on /home/chroot/sid64/home/chroot/sid64/tmp type ext4 (rw,relatime,errors=remount-ro,data=ordered) I see two mount points for every one mount point I expect. Eg: /var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/home/chroot/sid64/tmp and /home/chroot/sid64/home/chroot/sid64/tmp The second one seems wrong. Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681884: Same problem with schroot 1.6.8-1
Hi all, I'm seeing the same problem with schroot 1.6.8-1 but only on one of the two machines I regularly use schroot on. On the machine that displays this problem I have a amd64 Sid chroot called sid64. If I run it using 'schroot -c sid64' and immediately exit I get: E: 10mount: umount: /var/lib/schroot/mount/sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a/tmp: not mounted E: sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a: Chroot setup failed: stage=setup-stop If I then run 'mount | grep sid64' I get /dev/sda4 on /var/lib/schroot/mount/sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a type ext4 (rw,relatime,data=ordered) proc on /var/lib/schroot/mount/sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a/proc type proc (rw,nosuid,nodev,noexec,relatime) proc on /home/chroot/sid64/proc type proc (rw,nosuid,nodev,noexec,relatime) sysfs on /var/lib/schroot/mount/sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a/sys type sysfs (rw,nosuid,nodev,noexec,relatime) sysfs on /home/chroot/sid64/sys type sysfs (rw,nosuid,nodev,noexec,relatime) udev on /var/lib/schroot/mount/sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a/dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=1006828,mode=755) udev on /home/chroot/sid64/dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=1006828,mode=755) devpts on /var/lib/schroot/mount/sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) devpts on /home/chroot/sid64/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) /dev/sda4 on /var/lib/schroot/mount/sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a/home type ext4 (rw,relatime,data=ordered) /dev/sda4 on /home/chroot/sid64/home type ext4 (rw,relatime,data=ordered) Notice that there are two mount points recorded for say dev: /var/lib/schroot/mount/sid64-089cf50f-4a28-427f-9dfc-cfdb33284a4a/dev /home/chroot/sid64/dev I expected to see the first but not the second (which seems completely wrong). On the machine where schroot is working correctly, I never get the /home/chroot/$chroot_name/dev mount. Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
