Your message dated Wed, 29 Jul 2026 14:21:38 +0000
with message-id <[email protected]>
and subject line Bug#1140520: fixed in glusterfs 11.2-5
has caused the Debian Bug report #1140520,
regarding glusterfs-server: using KillMode=control-group in systemd service
causes client I/O timeouts
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.)
--
1140520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1140520
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: glusterfs-server
Version: 11.1-6
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
The debian package of glusterfs server has a patch to change the systemd
service KillMode from "process" to "control-group" (see
https://sources.debian.org/patches/glusterfs/11.2-3/02-systemd-service.diff/)
It looks like this was done because killing glusterd does not kill the
children glusterfsd processes. This is a deliberate design decision in
glusterfs, however, and glusterfsd processes should be left up when
restarting glusterd. The daemon will automatically reconnect by looking
for pidfiles. In fact, killing the entire control group can cause
catastrophic timeouts for clients!
When the glusterfsd processes are sent sigterm, they stop serving I/O
then try to "sign out" by contacting glusterd. But with
KillMode=control-group, glusterd will be dead, so the glusterfsd
processes hang. Crucially, they hang without terminating the socket
connection with a FIN/RST. The glusterfs client is designed to handle
socket terminations, but it depends on the FIN/RST (at which point it
would send the I/O request to a different brick), so clients also hang.
The client has a default network timeout of 42s, longer than the 30s
virtual disk timeout of a debian guest OS on qemu, for example. So if
glusterd gets restarted, the client waits 42s to switch bricks, but by
then, the debian guest already has a disk timeout error, and if the disk
is the root, mounts it read only. This causes all kinds of problems.
Fedora handles this in a better way by leaving glusterd with
KillMode=process, and shipping an additional oneshot service to deal
with glusterfsd processes.
See
https://src.fedoraproject.org/rpms/glusterfs/blob/rawhide/f/glusterfsd.service
I'd suggest doing the same for the upcoming 11.2 release, as the problem
still exists in the 11.2-3 package.
Thanks,
Aram
-- System Information:
Debian Release: 13.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.17.13-2-pve (SMP w/6 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages glusterfs-server depends on:
ii glusterfs-cli 11.1-6
ii glusterfs-client 11.1-6
ii glusterfs-common 11.1-6
Versions of packages glusterfs-server recommends:
ii nfs-common 1:2.8.3-1
glusterfs-server suggests no packages.
--- End Message ---
--- Begin Message ---
Source: glusterfs
Source-Version: 11.2-5
Done: Patrick Matthäi <[email protected]>
We believe that the bug you reported is fixed in the latest version of
glusterfs, 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.
Patrick Matthäi <[email protected]> (supplier of updated glusterfs 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: Wed, 29 Jul 2026 15:43:50 +0200
Source: glusterfs
Architecture: source
Version: 11.2-5
Distribution: unstable
Urgency: medium
Maintainer: Patrick Matthäi <[email protected]>
Changed-By: Patrick Matthäi <[email protected]>
Closes: 1085615 1140520
Changes:
glusterfs (11.2-5) unstable; urgency=medium
.
* Add patch 07-python-warning.
Closes: #1085615
* Use a similar way as Fedora to restart glusterfs-server.
Closes: #1140520
* Adjust lintian overrides.
Checksums-Sha1:
dd497c1dd30ff418bf0ea6d751f6500bf5883e83 3542 glusterfs_11.2-5.dsc
71a20f667d2b40e52d23a0b32e3175db1f450fd5 3937297 glusterfs_11.2.orig.tar.gz
4f56fd64c0054b64ea398b48b77c0836db36f668 25304 glusterfs_11.2-5.debian.tar.xz
cbd29ae22427f9555b5994518330fc12938c8a28 7871 glusterfs_11.2-5_source.buildinfo
Checksums-Sha256:
c94e586f13a008cd913daae0040bf6473355c879f33f32b37fa8f131d772a000 3542
glusterfs_11.2-5.dsc
540683ab1acdc95c7fe940061fb24464e1d3d0955a8610d79376911b73ed4ce4 3937297
glusterfs_11.2.orig.tar.gz
0b9c5458c0d0573dcb4043b3ef5770bd1d1d160f380a904fedb1cf5b6f180e1d 25304
glusterfs_11.2-5.debian.tar.xz
2c26d305ae94b6608c8e6eb58426b5afba055b4d079222fc246fa4c56f95a9e5 7871
glusterfs_11.2-5_source.buildinfo
Files:
1b5fbfe526ad747abac29ad10d03a3fe 3542 admin optional glusterfs_11.2-5.dsc
774b78c834e6160f86e01d97a95e7eb2 3937297 admin optional
glusterfs_11.2.orig.tar.gz
cfd3888f4b3491f2e089bdc8144fcd41 25304 admin optional
glusterfs_11.2-5.debian.tar.xz
d47cab33ead328fe586d6fd924d82c03 7871 admin optional
glusterfs_11.2-5_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEWKA9xYJCWk3IuQ4TEtmwSpDL2OQFAmpqA9AACgkQEtmwSpDL
2OSuhQ/9FYaYAjcaWe6/7Tn4BCQPgz4or/U9pXqoW9vokYNXQslnubJfP99oM5qd
xuaY8znK+8KqqPp4vR/v0xegMKx8dDjAa9g6vwM6foKV0bJwlakKK172euQt+TQN
QuLH+YiNcb+dL/5258D8yACHJXLqQojKIGYRRd4tP3IuwBXV8neRFYRHpRjFYpgh
tmv2wBlDGYG8qUAOfOL8uvFh3t65z3AclNsNzQEfMiB+iGuS6OdOfWryV/V62br7
CNYtYIVucHI61iUVSXtE7Jj23dYq08WiR6wJFvsNzOv7qyjWCu3nzW3RN5IxvzRc
Hnh0bIBiK1VMxSsPki9XuF+5frdFqT5FRT0opkNuYG1HHgnQh16UKcWPazXziBrW
xDbOn9WBx3q0syRneeueb9dGhUy8kiJP+yGcs4WtBa5J6+iBu9EBeC+DOKU0Ue2Z
j/vvlduu5oOn2ihC7hsYhh9VSSczRcTkKIHGn+T8jYa3d3go+UHVCiSDfLU+z3Ih
0QvMFNclx0omwJUDvIw9pLCIQCHAQ9E/xC8uVHwMhU/7LQf3NN9AJFZ89I1DD14P
JOKvyTufvcil8R1ZL0FxoF1QwnfF8xLTTMxhUPwFvOxck0JFR2LEcwIfRsEZqbJz
NSwRCEARyX68Nz6+Z1SuBrtCL8S6xWokdh4NsJmlOLbPE/fIhhk=
=Jmxl
-----END PGP SIGNATURE-----
pgp5Qb0smN54M.pgp
Description: PGP signature
--- End Message ---
