SMB shares on IBM iSeries (Update)

Dev Discussions
1

I’m refering to: Rclone can't connect to smb share

I’ve fixed the problem in the go-smb2 cloudsoda library and issued a pull request.

What is the best procedure to get this modification included in rclone ?

2

Hello, my fix has been merged into the main branch of go-smb2:

Someone knows when the dependency will be included in rclone ?

3

Have you tried to update smb dependency and built rclone yourself? To test if it works?

1 Like
4

Hy, yes, built successfully and run in production since March 20th.

1 Like
5

Any news about the merge ?

6

I am also waiting on this to be merged. This is a huge unlock for me :slight_smile: Is there anything I can do to help move this issue along? Is @gabviv ' s assertion that it has been tested enough or is there some other task / formal stroken that needs to be done?

7

Send a PR to update the go.mod in rclone

I update these once per release cycle but it would need to have made it to a tagged release to be included.

8

I encountered a problem when building docker image:

go: ``github.com/cloudsoda/go-smb2@v0.0.0-20260401042019-a9059825d591`` requires go >= 1.26.1 (running go 1.25.0; GOTOOLCHAIN=local)

Using 1.26.1 works great.
What can I do to send you the PR ?

9

The rclone build supports go 1.25 and 1.26 which is the current and previous versions of go.

This is a pretty standard policy in the Go world.

I would make an issue with the go-smb repo asking for them to support go1.25...

Actually looks like they have done that already so just try a later version

10

Hi All,

I'm just letting you know that I submitted a PR to update the go-smb2 library in rclone (smb: Provides fixes for IBM iSeries and signature verification. by dithwick · Pull Request #9563 · rclone/rclone) which Nick very quickly processed (thanks Nick).

So if you don't build rclone yourself, the fix for the IBM iSeries should be in the next release I guess.

2 Likes
11

Filing a tracking issue on rclone GitHub now — linking to your CloudSoda PR and explaining the iSeries angle — tends to make things go faster once the upstream merge happens. By the time you open the go.mod bump PR, maintainers already have the context. Wrote up the rest of the procedure (and why iSeries breaks things in the first place) here: Getting a go-smb2 Fix Into Rclone: A Guide for IBM iSeries SMB Compatibility - Port & Patch