Open bugith opened 17 hours ago
Some more info : this happened too with smbd -D testparm output, followed with log file head:
[global] add group script = /data/data/com.termux/files/usr/bin/true add machine script = /data/data/com.termux/files/usr/bin/true add user script = /data/data/com.termux/files/usr/bin/true add user to group script = /data/data/com.termux/files/usr/bin/true allow dns updates = disabled bind interfaces only = Yes dcerpc endpoint servers = rpcecho deadtime = 15 delete group script = /data/data/com.termux/files/usr/bin/true delete user from group script = /data/data/com.termux/files/usr/bin/true delete user script = /data/data/com.termux/files/usr/bin/true disable spoolss = Yes dns proxy = No dns update command = /data/data/com.termux/files/usr/bin/false enable core files = No host msdfs = No interfaces = 127.0.0.0/8 wlan0 lm announce = No load printers = No local master = No max log size = 50 max smbd processes = 8 max stat cache size = 1024 min receivefile size = 16384 multicast dns register = No name resolve order = lmhosts host bcast passwd program = /data/data/com.termux/files/usr/bin/true preferred master = No printcap name = /dev/null rename user script = /data/data/com.termux/files/usr/bin/true restrict anonymous = 2 security = USER server role = standalone server server services = smb server string = Samba on Termux show add printer wizard = No smb ports = 1139 4445 socket options = TCP_NODELAY SO_KEEPALIVE unix extensions = No idmap config * : backend = tdb aio write size = 0 delete readonly = Yes ea support = No inherit permissions = Yes lpq command = /data/data/com.termux/files/usr/bin/false lprm command = /data/data/com.termux/files/usr/bin/false map archive = No max connections = 6 max print jobs = 0 nt acl support = No print command = /data/data/com.termux/files/usr/bin/false store dos attributes = No strict locking = No use sendfile = Yes
[internal] browseable = No comment = Internal storage path = @TERMUX_HOME@/storage/shared read only = No vfs objects = aio_pthread aio_pthread:aio open = yes
The log file is flooded with these messages: [2024/10/20 11:44:39.459452, 0] ../../source3/smbd/server.c:1741(main) smbd version 4.16.11 started. Copyright Andrew Tridgell and the Samba Team 1992-2022 [2024/10/20 11:54:50.435054, 0] ../../source3/smbd/server.c:981(smbd_accept_connection) accept: Invalid argument [2024/10/20 11:54:50.435805, 0] ../../source3/smbd/server.c:981(smbd_accept_connection) accept: Invalid argument [2024/10/20 11:54:50.435994, 0] ../../source3/smbd/server.c:981(smbd_accept_connection) accept: Invalid argument [2024/10/20 11:54:50.436238, 0] ../../source3/smbd/server.c:981(smbd_accept_connection) accept: Invalid argument [2024/10/20 11:54:50.436428, 0] ../../source3/smbd/server.c:981(smbd_accept_connection) accept: Invalid argument [2024/10/20 11:54:50.436722, 0] ../../source3/smbd/server.c:981(smbd_accept_connection) accept: Invalid argument [2024/10/20 11:54:50.436898, 0] ../../source3/smbd/server.c:981(smbd_accept_connection) accept: Invalid argument [2024/10/20 11:54:50.437073, 0] ../../source3/smbd/server.c:981(smbd_accept_connection) accept: Invalid argument [2024/10/20 11:54:50.437245, 0] ../../source3/smbd/server.c:981(smbd_accept_connection) ...
Problem description
This morning I find my phone is out of storage. du -a .| sort -nr| head -n20 ran from com.termux/files dir shows the culprit is usr/var/log/samba/log.smbd (190GB)
Removed then restarting some crashed apps and everything seems OK.
What steps will reproduce the bug?
I imagine maybe just restart smbd -i and let run until phone turns into sleep mode or something similar, because I saw twice the termux screen spitting error messages I could stop (Ctrl+C did not work) and I had to force-kill from Android Settings Application
What is the expected behavior?
Don't fill the storage, respect the directive
System information