Bug#793081: More info

[Raphael Hertzog]

Control: forcemerge 728096 -1

On Tue, 11 Aug 2015, Raphael Hertzog wrote:
> Weirdly this does not happen with all chroots. The problematic one
> is based on Debian Wheezy. One based on jessie is fine.

The problem is the same than in #728096.

The host has this:
# ls -ld /dev/shm /run/shm
drwxrwxrwt 2 root root 40 Jan  9 02:01 /dev/shm
lrwxrwxrwx 1 root root  8 Jan 20  2016 /run/shm -> /dev/shm

The problematic chroot has this:
# ls -ald /srv/chroots/moto-amd64-sbuild/{dev,run}/shm
lrwxrwxrwx 1 root root8 Jun 18  2015 /srv/chroots/moto-amd64-sbuild/dev/shm 
-> /run/shm
drwxr-xr-x 2 root root 4096 Jun 18  2015 /srv/chroots/moto-amd64-sbuild/run/shm

The working chroot has this:
# ls -ald /srv/chroots/sana-amd64-sbuild/{dev,run}/shm
ls: cannot access /srv/chroots/sana-amd64-sbuild/run/shm: No such file or 
directory
drwxr-xr-x 2 root root 4096 Jun 18  2015 /srv/chroots/sana-amd64-sbuild/dev/shm

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#793081: More info

[Raphael Hertzog]

Weirdly this does not happen with all chroots. The problematic one
is based on Debian Wheezy. One based on jessie is fine.

I tried to track down the differences between both and
the output of /proc/mounts and /proc/self/mountinfo differs
between both for a reason that I don't understand (in particular since
those files provide kernel data and that the kernel is shared...).

Problematic chroot:
(moto-amd64-sbuild)root@aphrodite:~# cat /proc/self/mountinfo |grep shm
(moto-amd64-sbuild)root@aphrodite:~# cat /proc/mounts |grep shm
tmpfs /dev/shm tmpfs rw 0 0
tmpfs /dev/shm tmpfs rw,relatime 0 0
tmpfs 
/var/lib/schroot/mount/sana-amd64-sbuild-04f2ac4e-879e-4dd6-818e-3a5074f40007/dev/shm
 tmpfs rw,relatime 0 0

Working chroot:
(sana-amd64-sbuild)root@aphrodite:~# cat /proc/self/mountinfo |grep shm
51 47 0:37 / /dev/shm rw,relatime shared:29 - tmpfs tmpfs rw
(sana-amd64-sbuild)root@aphrodite:~# cat /proc/mounts |grep shm
tmpfs /dev/shm tmpfs rw 0 0
tmpfs /dev/shm tmpfs rw,relatime 0 0
tmpfs /dev/shm tmpfs rw,relatime 0 0

There is no significant difference in the way schroot is configured
for both chroots:
# diff -u /etc/schroot/chroot.d/{moto,sana}-amd64-sbuild 
--- /etc/schroot/chroot.d/moto-amd64-sbuild 2015-08-11 15:51:28.343837512 
+
+++ /etc/schroot/chroot.d/sana-amd64-sbuild 2015-08-11 15:51:30.227837480 
+
@@ -1,8 +1,9 @@
 # File managed by Salt. Do not edit manually.
-[moto-amd64-sbuild]
+[sana-amd64-sbuild]
 type=directory
-description=Kali moto/amd64
-directory=/srv/chroots/moto-amd64-sbuild
+description=Kali sana/amd64
+directory=/srv/chroots/sana-amd64-sbuild
+aliases=kali-current-amd64-sbuild,kali-bleeding-edge-amd64-sbuild
 groups=root,sbuild
 profile=sbuild
 root-groups=root,sbuild

So both are using the same sbuild profile.

-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org