Sean Whitton wrote... > /etc/schroot/sbuild/fstab contains this: > > # Mount a large scratch space for the build, so we don't use up > # space on an LVM snapshot of the chroot itself. > /var/lib/sbuild/build /build none rw,bind 0 0 (...)
> I would suggest that these lines be removed from the default
> /etc/schroot/sbuild/fstab. Another possibility would be to mount a
> tmpfs there, but maybe that should be left to the local administrator.
At a quick glance, both suggestion don't feel right. Especially when the
build creates a lot of data there.
Just removing that line means the chroot may just run full, depending on
the backend and other configurations. Using tmpfs may likewise trigger
OOM situations.
The only sensible solution I can think of here was schroot will do the
job sbuild no longer wants to do: Create a temporary directory in that
scratch space, mount it to /build inside, and clean up afterwards. This
however can no longer be achieved using an fstab line.
This requires some more checking. Your thoughts?
Christoph
signature.asc
Description: PGP signature
