2017-03-09 13:30 GMT+01:00 Stephan Gampert | GIP <stephan.gamp...@gip.com>: > Hello Mathieu, > > thank you very much for your answer. > > Unfortunately we need the symlinks, so removing the mfsymlinks option is not > really an option for us. > > We've already tried to use jessy. We had the same problem there. > We will test it with Debian stretch.
OK. > > It is because the complete file is parsed whien its size is 1067 bytes. > .... > > However, the slowness is probably coming from the server side. > > I've attached a wireshark trace of a "slow read". 10.0.9.149 is the > Debian-client, 10.0.21.11 is the Windows Server. > > As you can see, all seems ok from package 1-25. The file is read once > (FID 0x009a) and is closed. I presume this is the parse for the symlink. > > The next 4 packets seem strange for me. It looks like the Debian client > opens the file again 2 times in parallel (FID:0xc0f5 and FID 0x0017) and > the Server is sending a lock request back to the Debian-client (which is > not answered by the way). > > Do you expect the Debian-client to open the file again 2 times in parallel? I can't say for sur. But this looks strange. But why is packet 34 more than 7 seconds after packet 28? Can you post here the debugdata and the kernel log as per: https://wiki.samba.org/index.php/LinuxCIFS_troubleshooting Regards -- Mathieu Parent