OMV Machine hangs randomly on large file transfers to OMV

tinh_x7 · 4. Juli 2016

My samba version is 3.6.6, not sure if samba 4 would help my speed.

mechiah · 6. Juli 2016

Zitat von silentfobos

UPD: The problem just turned to be not…

I don't know that my issue wouldn't have happened over FTP as well.

For me the fix finally came when I upgraded the kernel. Whether it was the other things plus the kernel upgrade that did it, or just the kernel upgrade, I'll never know. I made an image of the drive and hope to never have this issue again, haha. Just letting you know FWIW, that might be all it takes.

tinh_x7 · 7. Juli 2016

My current SMB version is 3.6.6

When I set max protocol =smb3 in the Samba extra settings, I'm unable to access my shares on Windows 10.
I've tried \\local_ip ; \\server_name but not working.
I removed the shares drives, and tried to re-add them but no luck.
As soon as I set it back to max protocol =smb2, I have no issue.
Anybody have this issue?

ryecoaaron · 7. Juli 2016

samba3 (3.6.6) doesn't support the smb3 protocol. It was introduced with samba4. People have had luck installing the backports version of samba4.

tinh_x7 · 7. Juli 2016

I see.
The version number is confusing.
3.6.6 is < 4, and it's consider version 4.

Samba 4 has a mixed reviews.
Some users said it halved speed of Samba 3, while others had better results.

ryecoaaron · 7. Juli 2016

The samba version does not equal the smb protocol version. smb protocol is Microsoft's standard. Samba is the open source server that serves using said protocol.

I have never had an issue with samba 3 or 4 on many different systems. Even my Celeron J1900 maxes out gigabit with either version. I think more of the speed issues come from network adapter/drivers.

tinh_x7 · 7. Juli 2016

Why my samba didn't work if I set min protocol =2, or max protocol = 4 ?

ryecoaaron · 8. Juli 2016

You didn't read my post...

There is no smb protocol version 4. Only samba version 4. That version has NOTHING to do with the protcol version.

Don't set min protocol.

tinh_x7 · 9. Juli 2016

Even I removed all the Samba extra settings, my Windows 10 wouldn't let me access my shares.

ryecoaaron · 9. Juli 2016

I only have one Windows 10 machine and it doesn't access samba. I am building another one so I can figure out if this is a common problem.

tinh_x7 · 9. Juli 2016

I spent about an hour research on this Samba and Windows 10.
Apparently there is an issue with Windows 10 Samba protocol that doesn't support SMB3.11 yet.
Many Linux users are not happy with this issue.
Set max protocol = smb2 is the current best option.
I don't have this issue on Windows 8.

http://serverfault.com/questio…mba-share-from-windows-10

ryecoaaron · 9. Juli 2016

With samba 4, you should be able to set max protocol=smb3 then unless windows thinks 3.11 or 3.02 are ok with that setting. I will have to try it.

tinh_x7 · 9. Juli 2016

My samba is 3.6.6.
I have tried max protocol=smb3 and other methods too but that didn't work.

My OS:
Windows 10 Pro x64 Build 10586.420

ryecoaaron · 9. Juli 2016

max protocol = smb3 works on my win10 box with samba4. It did not work with no max protocol set.

ryecoaaron · 9. Juli 2016

Zitat von tinh_x7

My samba is 3.6.6.
I have tried max protocol=smb3 and other methods too but that didn't work.

Well of course smb3 doesn't work with samba 3.6.6. With that version, you need to stick with smb2 for a max.

tinh_x7 · 9. Juli 2016

I tried installed wheezy backport samba yesterday, it messed up my OMV.
I had to restore it back.

ryecoaaron · 9. Juli 2016

Well, you don't have to have smb3. Not sure why it messed up your system. I thought I had installed it a few times with no problems.

tinh_x7 · 9. Juli 2016

I tried these, then set max protocol = smb3 two days ago.
One thing during the installation asked me is if I want to keep the current samba config or use the new maintainer .
I chose new maintainer, but it didn't work.

Code

Samba Backport:


    Reference:
        http://backports.debian.org/Instructions/


    Add the following line to /etc/apt/sources.list:
        deb http://http.debian.net/debian wheezy-backports main


    Update the package index:
        apt-get update


    Install smbclient deb package:
        apt-get -t wheezy-backports install samba

Alles anzeigen

ryecoaaron · 9. Juli 2016

If you pick new maintainer, it overwrites your samba config. omv-mkconf samba would fix that.

ryecoaaron · 9. Juli 2016

Just installed backports 4.1 samba on an OMV 2.x VM and set max protocol = smb3. Windows 10 client connects just fine.

Jetzt mitmachen!