Android smb clients issue on remove files.

[serj-47]

My mergerfs pool consists of two disks and is used to share both disks over the network using the samba protocol, the pool is mounted as follows:

/srv/ST32000641AS:/srv/WD20SPZX /srv/pool mergerfs cache.files=off,dropcacheonclose=true,category.create=epff,fsname=mergerfs,ignorepponrename=true,minfreespace=10G 0 0

smb.conf:

...
[Storage]
path=/srv/pool/Storage
browseable=yes
writeable=yes
only guest=yes
create mask=0777
directory mask=0777
public=yes

So, samba clients with Windows OS or Linux OS can easily access the pool using the samba protocol, and can create, move and delete files and there are no problems.
But there are some problems with smb clients on Android. Here is a list of file managers for android that I have tried:
-Total Commander, (you need to install a separate plugin to work with smb).
-Material Files
In both file managers can create and move files on the samba server, but when trying to delete an error occurs about the inability to delete a directory or file.
*There is no such problem when sharing a shared directory on a disk without mergerfs.

[trapexit]

Please provide the requested info as defined in the ticket you filled out and in the support section of the page.

[joaopedrolages]

i Have the same issue using mergerfs as OMV 7 plugin
When i delete a file on android (total comander or File manager) using SMB share i get the error :
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 6018 ().

This means there was a problem with the program, such as a segfault.
However, the executable could not be found for process 6018.
It may have died unexpectedly, or you may not have permission to debug
the process.

First i had the error with NTFS on 2 disks but i deleted them and reformated to BTRFS and i get the same error.

No problem with windows

Once i saw user ADB in SMB diagnotics report.

[trapexit]

As I said above I need details as described in the ticket creation page and the support section of the docs. If the app is dying that's not mergerfs' fault. Nothing mergerfs does should cause an app to die. That would be a bug on their side.

[serj-47]

As described in the mergerfs wiki, I see that there may be problems with deleting or moving files in some file managers that do not follow the rfc when working with smb, or something like that. Therefore, I tried several file managers with a built-in smb client available in android, as a result, the 'amaze file manager' perfectly deletes files from mergerfs share and there are no errors.