[Pkg-samba-maint] Bug#1111107: samba: server reports 0 bytes available disk space to client

[Michael Tokarev]

Control: tag -1 found 2:4.17.0+dfsg-1
Control: tag -1 fixed 2:4.20.1+dfsg-1

On 14.08.2025 20:36, Daniel Fussell wrote:

> 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.

It's a kind of fun bug.  I did try to quickly set up samba 4.17 in a
bookworm container, - I don't see this behavior with local shares.

Setting up nfs is something I don't have an easy way to do now, - maybe
some time in the future, using two VMs.

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.

Also, for example, bisecting samba is rather painful, so I'd need to
know which commit fixed it without bisecting.  It's another nail to
the coffin, - this issue, while fixed in stable, needs more and more
efforts for oldstable which usage diminishes as I write this.

If someone knows where this is fixed and can verify, maybe I'll try
to push the fix to bookworm.  But as for now, it's fixed.

BTW, I stopped using 4.17 in production when 4.19 were released.
And speaking of upstream samba, 4.17 is dead completely.

Thanks,

/mjt