[buildd-tools-devel] Bug#686148: schroot: Does not unmount /run/shm

Daniel Dehennin daniel.dehennin at baby-gnu.org
Wed Aug 29 07:42:16 UTC 2012


Package: schroot
Version: 1.6.3-1
Severity: minor

Dear Maintainer,

I noticed several “/run/shm” in my mount since a moment but did not
figure out where they came from.

I just create a new schroot and got one more, I umount all superfluous
“/run/shm” and run “schroot -c sid-amd64-sbuild” and got:

  /dev/mapper/hati-sid--amd64--sbuild--a91d556e--4f12--4e9c--9c00--b7f4ee915b59 on /var/lib/schroot/mount/sid-amd64-sbuild-a91d556e-4f12-4e9c-9c00-b7f4ee915b59 type btrfs (rw,noatime,space_cache)
  proc on /var/lib/schroot/mount/sid-amd64-sbuild-a91d556e-4f12-4e9c-9c00-b7f4ee915b59/proc type proc (rw,nosuid,nodev,noexec,relatime)
  sysfs on /var/lib/schroot/mount/sid-amd64-sbuild-a91d556e-4f12-4e9c-9c00-b7f4ee915b59/sys type sysfs (rw,nosuid,nodev,noexec,relatime)
  devpts on /var/lib/schroot/mount/sid-amd64-sbuild-a91d556e-4f12-4e9c-9c00-b7f4ee915b59/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
  tmpfs on /run/shm type tmpfs (rw,relatime)
  /dev/dm-13 on /var/lib/schroot/mount/sid-amd64-sbuild-a91d556e-4f12-4e9c-9c00-b7f4ee915b59/build type btrfs (rw,nodev,noatime,space_cache)
  /dev/mapper/hati-var+cache on /var/lib/schroot/mount/sid-amd64-sbuild-a91d556e-4f12-4e9c-9c00-b7f4ee915b59/var/cache/apt/archives type ext4 (rw,noatime,data=ordered)
  

After quitting the schroot, the “/run/shm” is still here.

Regards.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (90, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.6.0-rc3+hati.1 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages schroot depends on:
ii  libboost-filesystem1.49.0       1.49.0-3.1
ii  libboost-iostreams1.49.0        1.49.0-3.1
ii  libboost-program-options1.49.0  1.49.0-3.1
ii  libboost-regex1.49.0            1.49.0-3.1
ii  libboost-system1.49.0           1.49.0-3.1
ii  libc6                           2.13-35
ii  libgcc1                         1:4.7.1-7
ii  liblockdev1                     1.0.3-1.5
ii  libpam0g                        1.1.3-7.1
ii  libstdc++6                      4.7.1-7
ii  libuuid1                        2.20.1-5.1
ii  schroot-common                  1.6.3-1

schroot recommends no packages.

Versions of packages schroot suggests:
pn  aufs-modules | unionfs-modules  <none>
ii  btrfs-tools                     0.19+20120328-8
ii  debootstrap                     1.0.42
ii  lvm2                            2.02.95-4
pn  qemu-user-static                <none>

-- Configuration Files:
/etc/schroot/sbuild/fstab changed:
/proc		/proc		none    rw,bind        0       0
/sys		/sys		none    rw,bind        0       0
/dev/pts	/dev/pts	none	rw,bind		0	0
tmpfs		/dev/shm	tmpfs	defaults	0	0
/var/lib/sbuild/build	/build	none	rw,bind	0	0
/var/cache/apt/archives /var/cache/apt/archives none rw,bind 0 0

/etc/schroot/setup.d/05lvm changed:
set -e
. "$SETUP_DATA_DIR/common-data"
. "$SETUP_DATA_DIR/common-functions"
. "$SETUP_DATA_DIR/common-config"
if [ "$VERBOSE" = "verbose" ]; then
    LVM_VERBOSE="-v"
fi
if [ "$CHROOT_TYPE" = "lvm-snapshot" ]; then
    if [ $STAGE = "setup-start" ]; then
	if [ ! "$DEVTYPE" "$CHROOT_DEVICE" ]; then
	    fatal "Device '$CHROOT_DEVICE' does not exist"
	fi
	if [ "$VERBOSE" = "verbose" ]; then
	    lvcreate $LVM_VERBOSE --snapshot --name "$CHROOT_LVM_SNAPSHOT_NAME" \
		"$CHROOT_DEVICE" $CHROOT_LVM_SNAPSHOT_OPTIONS
	else
	    lvcreate $LVM_VERBOSE --snapshot --name "$CHROOT_LVM_SNAPSHOT_NAME" \
		"$CHROOT_DEVICE" $CHROOT_LVM_SNAPSHOT_OPTIONS > /dev/null
	fi
    elif [ $STAGE = "setup-stop" ]; then
	if [ "$DEVTYPE" "$CHROOT_LVM_SNAPSHOT_DEVICE" ]; then
            # The lock needs to be dropped immediately before
            # destroying the device.  There is a small race here, but
            # the lock can't be dropped once the device has been
            # removed.
	    info "Removing device lock for $CHROOT_LVM_SNAPSHOT_DEVICE, owned by pid $PID"
            "$LIBEXEC_DIR/schroot-releaselock" \
		--device="$CHROOT_LVM_SNAPSHOT_DEVICE" \
		--pid=$PID || true
	    MAPPER_DEVICE=`dmsetup info --noheadings -c -o name $CHROOT_LVM_SNAPSHOT_DEVICE`
	    if [ "$VERBOSE" = "verbose" ]; then
                dmsetup remove -f "/dev/mapper/${MAPPER_DEVICE}" || true
                dmsetup remove -f "/dev/mapper/${MAPPER_DEVICE}-cow" || true
		lvremove $LVM_VERBOSE -f "$CHROOT_LVM_SNAPSHOT_DEVICE" || true
	    else
                dmsetup remove -f "/dev/mapper/${MAPPER_DEVICE}" > /dev/null || true
                dmsetup remove -f "/dev/mapper/${MAPPER_DEVICE}-cow"  > /dev/null || true
		lvremove $LVM_VERBOSE -f "$CHROOT_LVM_SNAPSHOT_DEVICE" > /dev/null || true
	    fi
	else
	    # The block device no longer exists, or was never created,
	    # for example on lvcreate failure.
	    warn "$CHROOT_LVM_SNAPSHOT_DEVICE does not exist (it may have been removed previously)"
	fi
    fi
fi


-- no debconf information

-- 
Daniel Dehennin
Récupérer ma clef GPG:
gpg --keyserver pgp.mit.edu --recv-keys 0x7A6FE2DF
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 229 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20120829/e739277d/attachment.pgp>


More information about the Buildd-tools-devel mailing list