KSMBD - What am I doing wrong?

[agarg]

Folks:
I installed Openwrt on a spare Newifi-D2 device and connected a 64GB usb to store my phone random pictures. However my samba access shows me strange folders:

Of this, 64GB is the intended folder and it works fine. Others are unexplained.

root@NEWIFI-D2:~# cd /mnt/sda1
root@NEWIFI-D2:/mnt/sda1# ls
root@NEWIFI-D2:/mnt/sda1# chmod -R 777 ../sda1
root@NEWIFI-D2:/mnt/sda1# ls /etc/config/ksmbd
/etc/config/ksmbd
root@NEWIFI-D2:/mnt/sda1# cat  /etc/config/ksmbd

config globals
	option workgroup 'WORKGROUP'
	option description 'files on NEWIFI'
	option interface 'iot lan'

config share
	option name '64GB-NEWIFI-D2'
	option path '/mnt/sda1'
	option read_only 'no'
	option guest_ok 'yes'
	option create_mask '0666'
	option dir_mask '0777'

root@NEWIFI-D2:/mnt/sda1# 

root@NEWIFI-D2:/mnt/sda1# cat /etc/config/f
firewall  fstab
root@NEWIFI-D2:/mnt/sda1# cat /etc/config/fstab 

config global
	option anon_swap '1'
	option anon_mount '1'
	option auto_swap '1'
	option auto_mount '1'
	option delay_root '5'
	option check_fs '0'

root@NEWIFI-D2:/mnt/sda1#

[agarg]

I noticed this on another openwrt device. I think there is an unexpected behavior from the firmware selector images or perhaps I am doing something wrong. This is on a TP-LINK Onhub 1900:

I found something interesting. It looks like ksmbd generates a file that is stored in /var and its not something we add to. It has added two entries that do not exisit in my /etc/config/ksmbd file.

[brada4]

Ty to explore SMB protocol level with samba4 on common linux. Defaults are always tuned for oldest current windows server and not older.

[agarg]

I uninstalled all the ksmbd components.
Verified that the /var/etc/ksmbd folder did not exist.
Reinstalled kmbd

ksmbd-avahi-service ksmbd-server kmod-fs-ksmbd luci-app-ksmbd

skipped a package I had earlier but did not know its function:

ksmbd-hotplug 

After the reboot, I reconfigured my shares and it is working fine. Not sure from where /var/etc/ksmbd/ksmbd.conf picked up the two shares that I neither knew about not wanted to expose in shares!

Thanks for reading and responding.