[Samba] "not enough space" on share with mountpoints inside

Alpe douglas.alpe-samba at yahoo.com
Thu Mar 11 19:34:30 UTC 2021


 I'm trying to build with --private-libraries=ALL.
But when I do, I get many missing libraries errors.
eg:/usr/sbin/smbd: error while loading shared libraries: libtevent.so.0: cannot open shared object file: No such file or directory
However, libtevent.so is available at /usr/lib/samba/ with the name libtevent.so.0.10.2.
Using --builtin-libraries=ALL yields the same result.

Why isn't it looking at the right filename? Or why isn't libtevent.so.0.10.2 named libtevent.so.0 by the installer?


I'm building https://github.com/samba-team/samba.

Works:./configure --without-ad-dc --without-json --without-libarchive --with-systemd --systemd-install-services --enable-cups --prefix=/usr --sysconfdir=/etc --localstatedir=/var --enable-fhs --with-shared-modules='!vfs_snapper' && make && sudo checkinstall --default


Doesn't work:./configure --without-ad-dc --without-json --without-libarchive --with-systemd --systemd-install-services --enable-cups --prefix=/usr --sysconfdir=/etc --localstatedir=/var --enable-fhs --with-shared-modules='!vfs_snapper' --private-libraries=ALL && make && sudo checkinstall --default


    Em quinta-feira, 11 de março de 2021 12:22:35 BRT, Alpe via samba <samba at lists.samba.org> escreveu:  
 
  Sorry, via repository the version is 4.12.5. Building myself is 4.14.0.
Ubuntu 20.04.Linux odroid 5.10.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.10.19-202103041610~groovy (2021-03-04) aarch64 aarch64 aarch64 GNU/Linux


[global]
    netbios name = ODROID
    deadtime = 15
    dns proxy = No
    domain master = No
    load printers = No
    log file = /var/log/samba/samba.log
    map to guest = Bad User
    guest account = nobody
    ntlm auth = ntlmv1-permitted
    preferred master = No
    printing = cups
    printcap = cups 
    cups options = raw
    remote announce = 192.168.1.255
    remote browse sync = 192.168.1.255
    security = USER
    server signing = auto
    server string = Samba file server
    template shell = /dev/null
    unix extensions = No
    username level = 6
    winbind nested groups = No
    winbind nss info = no
    winbind use default domain = yes
    idmap config * : backend = tdb
    hosts allow = 127. 192.168.1.
    use sendfile = Yes
    access based share enum = yes
    strict locking = No
    min receivefile size = 16384
    server min protocol = NT1
    server max protocol = SMB3
    acl allow execute always = True
    aio read size = 0
    aio write size = 0


[media]
    create mask = 0664
    directory mask = 02775
    path = /media/alpe
    valid users = alpe
    write list = alpe

    Em quinta-feira, 11 de março de 2021 12:05:06 BRT, L.P.H. van Belle via samba <samba at lists.samba.org> escreveu:  
 
 Sound familiar.. 

samba version? 
OS? 
smb.conf ? 

These things really help us to help you..


> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Alpe via samba
> Verzonden: donderdag 11 maart 2021 15:00
> Aan: samba at lists.samba.org
> Onderwerp: [Samba] "not enough space" on share with mountpoints inside
> 
> I have a share named "media" that points to the folder that contains the
> mountpoints of my external drives.eg:
> \\server\media\mountpoint1\\server\media\mountpoint2
> 
> If i try to write something to any mountpoint I get a "not enough space"
> error.However, if I mount the mountpoint directly to a Windows letter (eg:
> Z:) it works.The same problem also occurs on linux clients.
> I used the "dfree command" command option to log what folder samba is
> checking for free space.When I try to write to
> "\\server\media\mountpoint1" samba checks for ".", but if I mount this
> folder in Z: and try writing to it, samba checks "mountpoint1" as
> expected.
> 
> 
> It stopped working yesterday. It always worked before.
> Yesterday I though it would be a good idea to update all pip3 packages.
> Maybe this is what caused the issue.
> 
> 
> I already tried:
> apt install samba --reinstall
> build from source
> 
> But the issue persists.Anyone have any idea what could be the problem? Or
> what library/module/program is responsible for deciding which folder to
> check. I may have broken it, so I could try reinstalling it too.
> 
> Thanks.
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba



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


More information about the samba mailing list