Transparent Reconnection & Persistent handles support

[afiffon]

https://www.samba.org/~slow/talks/2018/SDC-Persistent_Handles.pdf

• TCP reconnect

• SMB2_SHARE_CAP_SCALEOUT

• SMB2_GLOBAL_CAP_PERSISTENT_HANDLES

• SMB2_SHARE_CAP_CONTINUOUS_AVAILABILITY

• Re-Setup session

• Durable handles: Provides a way for a connection to transparently reconnect to the server after a temporary disconnection (v1+v2, 3.2.4.4)

• Clusters?

[d3dx9]

Hi @AvivNaaman

It seems like when the connection crashes, it does not reconnect currently. Is there any plan when this will be implemented?

2025-10-13T18:07:10.462079Z ERROR Got IO error: An existing connection was forcibly closed by the remote host. (os error 10054) -- Mapping to IO error.
2025-10-13T18:07:10.462118Z ERROR Got IO error: An existing connection was forcibly closed by the remote host. (os error 10054) -- Mapping to IO error.
2025-10-13T18:07:10.462137Z ERROR Error in worker loop: Transport error: IO Error: An existing connection was forcibly closed by the remote host. (os error 10054)
2025-10-13T18:07:10.462177Z ERROR Error in worker loop: Transport error: IO Error: An existing connection was forcibly closed by the remote host. (os error 10054)
2025-10-13T18:07:10.462202Z ERROR Got IO error: An existing connection was forcibly closed by the remote host. (os error 10054) -- Mapping to IO error.
2025-10-13T18:07:10.462241Z ERROR Got IO error: An existing connection was forcibly closed by the remote host. (os error 10054) -- Mapping to IO error.
2025-10-13T18:07:10.462279Z ERROR Got IO error: An existing connection was forcibly closed by the remote host. (os error 10054) -- Mapping to IO error.
2025-10-13T18:07:10.462300Z ERROR Error in worker loop: Transport error: IO Error: An existing connection was forcibly closed by the remote host. (os error 10054)
2025-10-13T18:07:10.462333Z ERROR Error in worker loop: Transport error: IO Error: An existing connection was forcibly closed by the remote host. (os error 10054)
2025-10-13T18:07:10.462371Z ERROR Error in worker loop: Transport error: IO Error: An existing connection was forcibly closed by the remote host. (os error 10054)
2025-10-13T18:07:10.462400Z ERROR Got IO error: An existing connection was forcibly closed by the remote host. (os error 10054) -- Mapping to IO error.
2025-10-13T18:07:10.462438Z ERROR Got IO error: An existing connection was forcibly closed by the remote host. (os error 10054) -- Mapping to IO error.
2025-10-13T18:07:10.462469Z ERROR Got IO error: An existing connection was forcibly closed by the remote host. (os error 10054) -- Mapping to IO error.
2025-10-13T18:07:10.462510Z ERROR Got IO error: An existing connection was forcibly closed by the remote host. (os error 10054) -- Mapping to IO error.
PS S:\AzureSedexSync\logs>

[afiffon]

Hi,

I'm currently not sure whether I get to implementing this feature soon, so by that time, I'd suggest you to simply add a retry loop in your code.

A full reconnect implementation is not trivial (keeping files open, etc.)

[nicolube]

@afiffon This is also I feature I quite like to have