Your message dated Sun, 19 Jul 2026 11:50:30 +0300
with message-id <[email protected]>
and subject line Re: Bug#1111107: samba: server reports 0 bytes available disk
space to client
has caused the Debian Bug report #1111107,
regarding samba: server reports 0 bytes available disk space to client
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.)
--
1111107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111107
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: samba
Version: 2:4.22.3+dfsg-4~bpo12+1
Severity: important
Dear Maintainer,
After upgrading to Debian 12, the Samba server is reporting 0 bytes
available disk space to all users, but is correctly reporting disk
used space. This prevents Windows Explorer clients from being able to
copy new files into the share.
This only seems to happen with Debian 12's Samba 4.17; it is
not happening with 4.13 (Debian 11), 4.20 or 4.22 (Debian 12 backports).
Share roots are user home directories on NFS exports from Linux NFS
servers. Each user has a user quota on the underlying volume.
I don't have any local disk based shares to test with, so I can't
confirm that it only happens with NFS-mounted volumes. I assume it is not
happening with local disk shares, or someone surely would have reported
it by now.
I would expect the normal Samba behavior of reporting the lesser of available
user quota space or the volume's available disk free space be reported to
the client.
-- Package-specific info:
* /etc/samba/smb.conf present, but not attached
-- System Information:
Debian Release: 12.11
APT prefers oldstable-security
APT policy: (500, 'oldstable-security'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-38-amd64 (SMP w/4 CPU threads; PREEMPT)
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 samba depends on:
ii init-system-helpers 1.65.2
ii libbsd0 0.11.7-2
ii libc6 2.36-9+deb12u10
ii libcups2 2.4.2-3+deb12u8
ii libdbus-1-3 1.14.10-1~deb12u1
ii libgnutls30 3.7.9-2+deb12u5
ii libldap-2.5-0 2.5.13+dfsg-5
ii libldb2 2:2.11.0+samba4.22.3+dfsg-4~bpo12+1
ii libpopt0 1.19+dfsg-1
ii libtalloc2 2:2.4.3+samba4.22.3+dfsg-4~bpo12+1
ii libtasn1-6 4.19.0-2+deb12u1
ii libtdb1 2:1.4.13+samba4.22.3+dfsg-4~bpo12+1
ii libtevent0 2:0.16.2+samba4.22.3+dfsg-4~bpo12+1
ii libtirpc3 1.3.3+ds-1
ii liburing2 2.3-3
ii passwd 1:4.13+dfsg1-1+deb12u1
ii procps 2:4.0.2-3
ii samba-common 2:4.22.3+dfsg-4~bpo12+1
ii samba-common-bin 2:4.22.3+dfsg-4~bpo12+1
ii samba-libs [libndr6] 2:4.22.3+dfsg-4~bpo12+1
Versions of packages samba recommends:
ii attr 1:2.5.1-4
ii python3-samba 2:4.22.3+dfsg-4~bpo12+1
ii samba-ad-dc 2:4.22.3+dfsg-4~bpo12+1
Versions of packages samba suggests:
pn ctdb <none>
pn samba-vfs-ceph <none>
pn samba-vfs-glusterfs <none>
pn ufw <none>
ii winbind 2:4.22.3+dfsg-4~bpo12+1
-- debconf information:
samba/run_mode: daemons
samba-common/title:
--- End Message ---
--- Begin Message ---
Version: 2:4.20.1+dfsg-1
On Fri, 15 Aug 2025 09:14:26 +0300 Michael Tokarev <[email protected]> wrote:
...
Either way, as far as debian is concerned, I'd say this bug is history,
-- by your own words it doesn't happen in trixie version of samba, which
is what matters now. It would be difficult to fix this in bookworm,
which has become oldstable.
Let's close this bug report finally.
Thanks,
/mjt
--- End Message ---
