Hello Mathieu,
I can't say for sur. But this looks strange. But why is packet 34 more
than 7 seconds after packet 28?
I don't know. Perhaps the server is waiting for a response to the
Locking AndX Request.
Can you post here the debugdata and the kernel log as per:
Hello Mathieu,
We have tested it with Debian stretch (installed from iso-image
downloaded today, 2017-01-28). The problem still exists in stretch.
Accessing a file with length 1067 still lasts some seconds.
Regards
Stephan
--
Stephan Gampert
_
GIP Exyr GmbH
Hechtsheimer
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.
> It is because the complete file
"Control: severity -1 wishlist
Control: tag -1 upstream
2017-03-01 10:54 GMT+01:00 Stephan Gampert | GIP :
> Subject: cifs-utils: Accessing files with length of 1067 bytes extremly slow
[...]
> we are using cifs-utils to access Microsoft Windows 2012R2 File-Server
>
2017-03-01 10:54 GMT+01:00 Stephan Gampert | GIP :
> Subject: cifs-utils: Accessing files with length of 1067 bytes extremly slow
[...]
>
> All of the "slow files" have a length of 1067 bytes.
> As far as I know this is also the length of symlink files. Perhaps there is
>
5 matches
Mail list logo