[Samba] 2x Samba4 Bugs - "mount error(5): Input/output error" & "recycle: stat for ... AFP_AfpInfo returned No such file or directory"

[Leander Schäfer]

Hi Jeremy

Tnaks for your reply. I use samba41 from FreeBSD Ports. Can you tell me 
how I should give it the minus -g option? the only way how I know to 
compile ports is:

cd /usr/ports/net/samba41
make install clean

Thanks


Am 09.05.14 20:59, schrieb Jeremy Allison:
> On Thu, May 08, 2014 at 11:21:09AM +0200, Leander Schäfer wrote:
>> Hi
>>
>> I'm using Samba version 4.1.7 on the server side. On the Client side
>> is multiple versions
>> - a copy machine Konica Minolta
>> - Windows XP
>> - Windows 7
>> - Mac OSx (Mavericks)
>> - CentOS (XenServer)
>>
>> all of them get sporadic input output errors. E.g: on a Linux I would get a
>>
>> mount error(5): Input/output error
>>
>> after the first try. And as funny as it sounds, but the second try
>> is a success and all is mounted as expected. What causes this
>> sporadic behaviour?
>> It is quite annoying, since almost every second scan with the copy
>> machine is a fail ...
>> Is this a bug?
>>
>> Mount command on Linux:
>> mount -t cifs //10.0.0.200/MYSHARE -o
>> username="${SMB_USR}",password="${SMB_PWD}",sec=ntlmv2 /mnt/MyShare
>>
>> Also I saw this in the logs:
>>
>>    recycle: stat for /mnt/MyShare/.Trashes/Management/Gründung/06 -
>> Corporate Design/02 - Farbverläufe/Bildschirmfoto 2014-04-30 um
>> 17.23.08.png:AFP_AfpInfo returned No such file or directory
>> [2014/05/05 21:37:28.770219,  0] ../lib/util/fault.c:72(fault_report)
>>    ===============================================================
>> [2014/05/05 21:37:28.786358,  0] ../lib/util/fault.c:73(fault_report)
>>    INTERNAL ERROR: Signal 11 in pid 18048 (4.1.7)
>>    Please read the Trouble-Shooting section of the Samba HOWTO
>> [2014/05/05 21:37:28.786505,  0] ../lib/util/fault.c:75(fault_report)
>>    ===============================================================
> This isn't enough detail for us to debug the problem.
>
> Can you rebuild with debug symbols (-g) and add a
> panic action = /bin/sleep 9999999
> line to your smb.conf [global] section ? That
> way you'll get a stuck smbd on a crash you
> can attach to via gdb and get a good backtrace
> so we can see what might be going on.
>
> Thanks !
>
> Jeremy.