Your message dated Fri, 06 Mar 2026 20:34:52 +0000
with message-id <[email protected]>
and subject line Bug#1008616: fixed in schroot 1.6.13-8
has caused the Debian Bug report #1008616,
regarding /etc/schroot/setup.d/05zfs: make ZFS snapshot removal more robust
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1008616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008616
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: schroot
Version: 1.6.10-12
Severity: minor
File: /etc/schroot/setup.d/05zfs
Tags: patch
Dear maintainer,
thank you for enabling ZFS usage.
Please consider the following patch to make clone removal a little more
robust:
| diff --git a/schroot/setup.d/05zfs b/schroot/setup.d/05zfs
| index 6ecc0196..785aee5f 100755
| --- a/schroot/setup.d/05zfs
| +++ b/schroot/setup.d/05zfs
| @@ -49,10 +49,10 @@ if [ "$CHROOT_TYPE" = "zfs-snapshot" ] && [ -n
"$CHROOT_ZFS_CLONE_NAME" ]; then
| if zfs list "$CHROOT_ZFS_CLONE_NAME" >/dev/null 2>&1
| then
| if [ "$VERBOSE" = "verbose" ]; then
| - zfs destroy "$CHROOT_ZFS_CLONE_NAME"
| + zfs destroy -r "$CHROOT_ZFS_CLONE_NAME"
| zfs destroy "$CHROOT_ZFS_SNAPSHOT_NAME"
| else
| - zfs destroy "$CHROOT_ZFS_CLONE_NAME" > /dev/null
| + zfs destroy -r "$CHROOT_ZFS_CLONE_NAME" > /dev/null
| zfs destroy "$CHROOT_ZFS_SNAPSHOT_NAME" > /dev/null
| fi
| else
I.e. recursively destroy all children of that clone via the "-r" option.
Otherwise I can all too easily happen that such children exist in the
form of snapshots, e.g. when using zfsnap or any such tool that might
automatically create a snapshot of a ZFS dataset while it is in use.
For illustration, let's consider the following sequence of actions:
1. a user enters a ZFS-based chroot via
$ schroot -c unstable-amd64-sbuild
2. schroot creates a snapshot of the base dataset and then a clone of
that snapshot, e.g.
$ zfs list -t all
[...]
zfspool/SYSTEM/srv/chroot/unstable-amd64-sbuild@unstable-amd64-sbuild-44e762df-cab6-4cf3-99dd-15f0fd018d18
0B - 359M -
zfspool/SYSTEM/srv/chroot/unstable-amd64-sbuild/schroot-unstable-amd64-sbuild-44e762df-cab6-4cf3-99dd-15f0fd018d18
8K 62.2G 359M legacy
3. some tool - here done manually - creates a snapshot of that clone
$ sudo zfs snapshot
zfspool/SYSTEM/srv/chroot/unstable-amd64-sbuild/schroot-unstable-amd64-sbuild-44e762df-cab6-4cf3-99dd-15f0fd018d18@test
4. the user exits their schroot session and schroot complains
E: 05zfs: cannot destroy
'zfspool/SYSTEM/srv/chroot/unstable-amd64-sbuild/schroot-unstable-amd64-sbuild-44e762df-cab6-4cf3-99dd-15f0fd018d18':
filesystem has children
E: 05zfs: use '-r' to destroy the following datasets:
E: 05zfs:
zfspool/SYSTEM/srv/chroot/unstable-amd64-sbuild/schroot-unstable-amd64-sbuild-44e762df-cab6-4cf3-99dd-15f0fd018d18@test
E: unstable-amd64-sbuild-44e762df-cab6-4cf3-99dd-15f0fd018d18: Chroot setup
failed: stage=setup-stop
5. $CHROOT_ZFS_CLONE_NAME and $CHROOT_ZFS_SNAPSHOT_NAME must be cleaned
up manually
Cheers,
Flo
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: schroot
Source-Version: 1.6.13-8
Done: Christoph Biedl <[email protected]>
We believe that the bug you reported is fixed in the latest version of
schroot, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christoph Biedl <[email protected]> (supplier of updated schroot
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 05 May 2025 08:05:35 +0200
Source: schroot
Architecture: source
Version: 1.6.13-8
Distribution: unstable
Urgency: medium
Maintainer: Christoph Biedl <[email protected]>
Changed-By: Christoph Biedl <[email protected]>
Closes: 1008616 1094739 1101658 1102156 1104692 1110659 1113487 1127026 1129698
Changes:
schroot (1.6.13-8) unstable; urgency=medium
.
* Update Portuguese translation, thanks Pedro Ribeiro.
Closes: #1102156
* Add Canalan debconf translation, thanks Carles Pina i Estany.
Closes: #1101658
* Avoid lockfile directory creation race, thanks Anton Mikanovich.
Closes: #1094739
* Add mount to build dependencies to loopback support.
Closes: #1104692
* Make ZFS snapshot removal more robust, thanks Florian Ernst.
Closes: #1008616
* Fix build with CMake 4, thanks Graham Inggs for collecting
these and the following ones. Closes: #1113487
* Fix build with Boost 1.85 and 1.89. Closes: #1110659, #1127026
* Add swedish DebConf translation, thanks Daniel Nylander.
Closes: #1129698
Checksums-Sha1:
013f33c928c859cf03dc16d04b07191dc886978d 2218 schroot_1.6.13-8.dsc
4df8cf6c10c0c6fe6be683c683df0b7452ad5b0f 122288 schroot_1.6.13-8.debian.tar.xz
815aaae3aa12b8193526bd02d3476f2e002fc638 8553
schroot_1.6.13-8_powerpc.buildinfo
Checksums-Sha256:
28d5d408dbc65f72e217ef77c20fdd4b0e9620fde412c765b455ecf914dbdc2b 2218
schroot_1.6.13-8.dsc
69f35c8264b62474fd85a206ecdc0e40410212c8bfa9f92a56afbf652d78f1f0 122288
schroot_1.6.13-8.debian.tar.xz
5df48474b576e7ba397a9084a69274fdb8378b1be1779e33bdaf43a806bc5410 8553
schroot_1.6.13-8_powerpc.buildinfo
Files:
a9eaa15ca7cc6e252d25a89fa8e44381 2218 admin optional schroot_1.6.13-8.dsc
81a984f1eeef405499d60a6e1fbb7f15 122288 admin optional
schroot_1.6.13-8.debian.tar.xz
203dc5ae291abdb57c7984d3572767e9 8553 admin optional
schroot_1.6.13-8_powerpc.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEWXMI+726A12MfJXdxCxY61kUkv0FAmmrGRAACgkQxCxY61kU
kv3DeQ//Z+tadri6hp+mdZseroa5cwS/Q4sLb2ocPgGbMq4B/BS7txQ+DFc07oUc
iTdSgQPTAm4bwpi/GnkDj3EPFR5Mowbrdp6nnAhKdxwxAsn9qMv2GOcb74xgwh8s
YUNBG66QEmSgsus2WXdJ4qgAm8uq7hjrLzykJvY7/X0ABVsbYWl5659BGG6nuONt
5qflWAyC/Me1kCOh/nPo+DFXdOMyWBVldiSDsjHFqUiQB9LNDYPWT46SAM8Mbzyp
38HS5ji11KstCDKauK23hAYcZ25baY3yEXErvmB/Bk4bahTe3l56kvMgIp6Hwib9
oyIAJsJSvd9DoGB9QFn4mffkViy4FNbRsvxJu4WewxmUo56Lt+Yuct1tkGA1j7W+
RiLuI1Y2JWAWUZY7mNrFucI5RfXHWt2JctSEb4cZroSflySBoLRMlf7jjOULlGPf
bgo87UGBIu4cxd8Klld47TO/q7vUJ9tTnzEsThedA8c33szAm4CzYPTpivI8c/gJ
fqOpm5d4sSIM2fF3/C1hFTaZzLNj1Z8ablraVv5YGf0giDH5kFXK+Kg7kLHenKmv
f40AwnTpi3o5VaRSA1jzT+KVgW1H/faX8s4XxDT8U/lpQhgmgMu7mNwY41rLHH2F
tUFrx8pXrcsLIUUAn+JIg08NlbQY/pPIzy5NwHEe/xth8Tj1Wn0=
=ru3p
-----END PGP SIGNATURE-----
pgpCtPSz86NrZ.pgp
Description: PGP signature
--- End Message ---
