Thank you! Nothing is jumping into my eye from the logs. The SMB Server just
drops
the network connection. Also I don't see a memory issue. I have 16GB of Ram
6GB in use
while copying. The oplocks option unfortunately did not work. This is so
strange...
Kind regards,
Leon
> Rodrigo Cunha <rodrigo.root.rj at gmail.com> hat am 08.03.2023 21:26
CET geschrieben:
>
>
> Hi, Jeremy. I saw that in the samba servers. This smells like a known
problem, with 'out of memory'. Check the log.
> Run journalctl -f and try again.
> Sometimes, this problem Is solved with the setup:
> [global]
> oplocks = no
>
> How much memory do you have?
>
>
>
> On Wed, Mar 8, 2023 at 2:40?PM Jeremy Allison via samba <samba at
lists.samba.org mailto:samba at lists.samba.org> wrote:
>
> > On Wed, Mar 08, 2023 at 08:54:24AM +0100, Leon Benthaus via samba
wrote:
> > >Dear all,
> > >
> > >I still have CentOS7 running with the latest Samba Version
available
> > >for it (samba-4.10.16-20.el7)
> > >I'm experiencing a really strange issue. When I copy a file
larger
> > >than 2GB I always get a network
> > >drop. It just stops at around 1,74gb. The logs didn't show
something
> > >in default logging level and
> > >are overwhelming at 5. An interesting detail is: If I pause the
copy
> > >process every other second
> > >I can get the whole file copied. If I let it run at full speed it
is
> > >not working. Any idea? I already
> > >played around with socket options and stuff. No change. The shares
is
> > >located on a xfs formatted drive.
> >
> > Might be:
> >
> > https://bugzilla.samba.org/show_bug.cgi?id=15261
> >
> > Contains a patch you might try.
> >
> > --
> > To unsubscribe from this list go to the following URL and read the
> > instructions: https://lists.samba.org/mailman/options/samba
> >
>
>
> --
> Atenciosamente,
> Rodrigo da Silva Cunha
> S?o Gon?alo, RJ - Brasil
>
>