Copying 64-bit W10 Pro's single huge files (~88 GB) to Debian bullseye v11 stops after a few GBs via Samba.

[Ant]

Hello,

Copying 64-bit W10 Pro's single huge files (~88 GB) to Debian bullseye
v11 stops after a few GBs via Samba. Telling W10 to pause and resume it
fails (just hangs). Even cancelling gets stuck. This only happens after
I close/exit 64-bit W10's File Explorer. If I leave it open, then it
will finish. Is this a bug in W10 or something else with Samba?

Thank you for reading and hopefully answering soon. :)
--
"Do not work for food that spoils, but for food that endures to eternal life, which the Son of Man will give you. On him God the Father has placed his seal of approval." --John 6:27. 2day will B slammy? Somewhat slammy Mon. with 3 dentist appts. 4 Colony.
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

[Marco Moock]

Am 08.08.2023 um 16:54:15 Uhr schrieb Ant:

> Copying 64-bit W10 Pro's single huge files (~88 GB) to Debian
> bullseye v11 stops after a few GBs via Samba. Telling W10 to pause
> and resume it fails (just hangs). Even cancelling gets stuck. This
> only happens after I close/exit 64-bit W10's File Explorer. If I
> leave it open, then it will finish. Is this a bug in W10 or something
> else with Samba?

What does the log say?

Can you use Wireshark to check what happens when you close the explorer?

[Ant]

Marco Moock <mo...@posteo.de> wrote:
> Am 08.08.2023 um 16:54:15 Uhr schrieb Ant:

> > Copying 64-bit W10 Pro's single huge files (~88 GB) to Debian
> > bullseye v11 stops after a few GBs via Samba. Telling W10 to pause
> > and resume it fails (just hangs). Even cancelling gets stuck. This
> > only happens after I close/exit 64-bit W10's File Explorer. If I
> > leave it open, then it will finish. Is this a bug in W10 or something
> > else with Samba?

> What does the log say?

I only saw startups:
$ sudo cat /var/log/samba/log.smbd
[2023/08/08 07:55:26.403037, 0] ../../source3/smbd/server.c:1784(main)
smbd version 4.13.13-Debian started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
[2023/08/08 07:55:26.411104, 0] ../../lib/util/become_daemon.c:135(daemon_ready)
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
[2023/08/08 08:35:11.307650, 0] ../../source3/smbd/server.c:1784(main)
smbd version 4.13.13-Debian started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
[2023/08/08 08:35:11.329313, 0] ../../lib/util/become_daemon.c:135(daemon_ready)
daemon_ready: daemon 'smbd' finished starting up and ready to serve connections

sudo cat /var/log/samba/log.nmbd
[2023/08/08 08:35:01.477709, 0] ../../source3/nmbd/nmbd.c:59(terminate)
Got SIGTERM: going down...
[2023/08/08 08:35:11.238712, 0] ../../source3/nmbd/nmbd.c:960(main)
nmbd version 4.13.13-Debian started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
[2023/08/08 08:35:11.242655, 0] ../../lib/util/become_daemon.c:135(daemon_ready)
daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
[2023/08/08 08:35:55.184198, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****

Samba name server ANTIANSSD is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.7

*****
[2023/08/08 09:06:14.333252, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****

Samba name server ANTIANSSD is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.2

*****
[2023/08/08 10:07:05.997653, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****

Samba name server ANTIANSSD is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.14

*****
[2023/08/08 10:12:01.653927, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****

Samba name server ANTIANSSD is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.10

*****

> Can you use Wireshark to check what happens when you close the explorer?

In my 64-bit W10 Pro?

According to the answers in my https://answers.microsoft.com/en-us/windows/forum/windows_10-files/copying-64-bit-w10-pros-single-huge-files-88-gb-to/8026df5d-ce23-42e3-b158-fae4a36a96b0?messageId=d679b05f-a07e-49ae-8517-61506a67b88b, https://old.reddit.com/r/WindowsHelp/comments/15lnkmm/copying_64bit_w10_pros_single_huge_files_88_gb_to/, and https://old.reddit.com/r/techsupport/comments/15lnl2g/copying_64bit_w10_pros_single_huge_files_88_gb_to/, it is session and buffer related when I close W10's File Explorer.

Does that sound right? :/
--
"Do not work for food that spoils, but for food that endures to eternal life, which the Son of Man will give you. On him God the Father has placed his seal of approval." --John 6:27. Slammy Tues. after a somewhat slammy Mon. with 3 dentist appts. 4 da colony. More 2morrow?

[Marco Moock]

Am 09.08.2023 um 03:51:12 Uhr schrieb Ant:

> In my 64-bit W10 Pro?
>
> According to the answers in my
> https://answers.microsoft.com/en-us/windows/forum/windows_10-files/copying-64-bit-w10-pros-single-huge-files-88-gb-to/8026df5d-ce23-42e3-b158-fae4a36a96b0?messageId=d679b05f-a07e-49ae-8517-61506a67b88b,
> https://old.reddit.com/r/WindowsHelp/comments/15lnkmm/copying_64bit_w10_pros_single_huge_files_88_gb_to/,
> and
> https://old.reddit.com/r/techsupport/comments/15lnl2g/copying_64bit_w10_pros_single_huge_files_88_gb_to/,
> it is session and buffer related when I close W10's File Explorer.
>
> Does that sound right? :/

Maybe, I am not an expert of SMB and I have no experience with
it on Windows. It was just a guess.