[Buildd-tools-devel] Bug#401180: schroot: using a symlink for /var/lib/schroot/mount causes /home and /tmp to be erased

Lucas Nussbaum lucas at lucas-nussbaum.net
Fri Dec 1 14:29:29 CET 2006


Package: schroot
Version: 1.0.3-1
Severity: critical
Justification: causes removal of /home

Hi,

I am using "file" chroots. the chroot is usually untared under
/var/lib/schroot, however, I wanted to change this to another location
(my /var is quite small, and many apps don't like it being full).

I couldn't find any way to specify another directory for this, so I just
symlinked /var/lib/schroot to another place. However, this caused
$LIBEXEC_DIR/schroot-listmounts to be unable to determine that /home,
/tmp, etc were still bind-mounted. So do_umount_all in that file exits
without error even if my filesystems are still bind-mounted, and my home
directory and my /tmp got removed.

Example:
***lucas at beothuk:~$ mount
[...]
/dev/pts on
/home/space/schroot/tetch-0128da3c-4a77-4b19-a10b-f60b91536bb5/dev/pts
type none (rw,bind)
tmpfs on
/home/space/schroot/tetch-0128da3c-4a77-4b19-a10b-f60b91536bb5/dev/shm
type tmpfs (rw)

***lucas at beothuk:~$ /usr/lib/schroot/schroot-listmounts -m
/var/lib/schroot/mount/tetch-0128da3c-4a77-4b19-a10b-f60b91536bb5/
***lucas at beothuk:~$

schroot-listmounts needs fixing, of course. But it would also be nice to
not bind-mount /home by default. There was already a bug causing
/home removal (bug #369626).

Please note that this bug was discovered in version 1.0.2-1. I cannot
confirm that 1.0.3-1 is also affected since I'm still recovering data
from a backup. However, I diff'd the two source packages and couldn't
find any reason why it wouldn't be affected.

Thank you,
-- 
| Lucas Nussbaum
| lucas at lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas at nussbaum.fr             GPG: 1024D/023B3F4F |




More information about the Buildd-tools-devel mailing list