samba - Mar 2021 - "not enough space" on share with mountpoints inside

No new kernel. The only thing I recall changing right before it breaking is that
I tried to upgrade all pip3 packages using:
sudo -H pip3 list --outdated --format=freeze | grep -v '^\-e' | cut -d =
-f 1 | xargs -n1 sudo -H pip3 install -U
I think maybe this broke something that samba uses and that is why the issue is
now happening regardless of which samba version I use.
But I have no idea what. So I can't reinstall the possible broken package.



Already did. I used "dfree command" to confirm that it is reading the
wrong folder, unless I mount it as a drive. Also confirmed that the problem also
occurs on linux clients, so the problem is on the server side.


    Em quinta-feira, 11 de mar?o de 2021 13:03:14 BRT, Rowland penny via samba
<samba at lists.samba.org> escreveu:
That is weird, perhaps something other than Samba has changed, a new 
kernel perhaps ?

You could try reading about the 'dfree command' in 'man
smb.conf'.

Rowland



-- 
To unsubscribe from this list go to the following URL and read the
instructions:? https://lists.samba.org/mailman/options/samba

On 11/03/2021 16:09, Alpe via samba wrote:
>   No new kernel. The only thing I recall changing right before it breaking
is that I tried to upgrade all pip3 packages using:
> sudo -H pip3 list --outdated --format=freeze | grep -v '^\-e' | cut
-d = -f 1 | xargs -n1 sudo -H pip3 install -U
> I think maybe this broke something that samba uses and that is why the
issue is now happening regardless of which samba version I use.
> But I have no idea what. So I can't reinstall the possible broken
package.

Samba (as far as I am aware) uses python for two things, to build Samba 
from source and for samba-tool, neither of which seem to have anything 
to the way you are running Samba. If it worked before you upgraded pip3 
and didn't after, then you need to find what actually changed.

Rowland