CIFS/Samba Unstable still?

[cyberjock]

You can't go back if your config file is from a newer version than what you are using. Your pool won't go backwards either if you upgraded it(which is why there is the fat warning in the manual about it).

 

[pilotjunky]

So far so good with CIFS/Samba on 9.2.1.4 BETA.

 

[diedrichg]

You can't go back if your config file is from a newer version than what you are using. Your pool won't go backwards either if you upgraded it(which is why there is the fat warning in the manual about it).

Wasn't the pool upgrade (zfs version) just from v8.x to v9.x? Shouldn't 9.2.1.3 > downgrade to 9.2.0 with config backup restored work fine?

 

[Youri Andropov]

Hi there.

I'm also using CIFS shares, and I'm affected by hangs . I found that in /var/log/messages :

Code:

Apr  9 21:08:56 freenas smbd[20662]:  matchname: host name/name mismatch: 192.168.0.90 != (NULL)
Apr  9 21:08:56 freenas smbd[20662]:  matchname failed on 192.168.0.90
Apr  9 21:43:43 freenas smbd[20977]:  matchname: host name/name mismatch: 192.168.0.90 != (NULL)
Apr  9 21:43:43 freenas smbd[20977]: [2014/04/09 21:43:43.868007,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Apr  9 21:43:43 freenas smbd[20977]:  matchname failed on 192.168.0.90
Apr  9 21:44:14 freenas smbd[20662]: [2014/04/09 21:44:14.010544,  0] ../source3/smbd/oplock.c:335(oplock_timeout_handler)
Apr  9 21:44:14 freenas smbd[20662]:  Oplock break failed for file SERIES/Oz/S5/Oz S5E02 Les lois de la gravité.mkv -- replying anyway
etc.

[edit] Ok I'm trying 9.2.1.4-beta, I'll tell.

 

[cyberjock]

Wasn't the pool upgrade (zfs version) just from v8.x to v9.x? Shouldn't 9.2.1.3 > downgrade to 9.2.0 with config backup restored work fine?

No. FreeNAS 9.1.0 brought about v5000, which is feature flags. If your pool has a flag that doesn't exist in the version of FreeNAS that you are using, the pool either won't mount or can only be mounted read-only. And each version of FreeNAS has added flags every time. 9.2.1 adds like 5 of them.

 

[pilotjunky]

Update... 3 days in with 9.2.1.4 BETA 27/7 and CIFS/Samba seems solid again. I have a security system doing regular writes to it 24/7, I've been doing some laptop backups with thousands of files going back and forth and all my Laser Cutting/Design files no longer bog down. Not a single lost connection to a Share either.

 

[Youri Andropov]

Sorry but I still have the issue, even with 9.2.1.4-beta.

Code:

[root@freenas ~]# uname -a
FreeBSD freenas.local 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #0 r262572+5356990: Tue Apr  8 10:44:24 PDT 2014    root@build.ixsystems.com:/home/jkh/9.2.1-BRANCH/freenas/os-base/amd64/tank/home/jkh/9.2.1-BRANCH/freenas/FreeBSD/src/sys/FREENAS.amd64  amd64
[root@freenas ~]# grep smbd /var/log/messages | tail -10
Apr 10 22:16:53 freenas smbd[21711]: [2014/04/10 22:16:53.690025,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Apr 10 22:16:53 freenas smbd[21711]:  matchname failed on 192.168.0.90
Apr 10 22:43:47 freenas smbd[21977]: [2014/04/10 22:43:47.754343,  0] ../source3/lib/util_sock.c:941(matchname)
Apr 10 22:43:47 freenas smbd[21977]:  matchname: host name/name mismatch: 192.168.0.90 != (NULL)
Apr 10 22:43:47 freenas smbd[21977]: [2014/04/10 22:43:47.754460,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Apr 10 22:43:47 freenas smbd[21977]:  matchname failed on 192.168.0.90
Apr 10 23:15:47 freenas smbd[22320]: [2014/04/10 23:15:47.854002,  0] ../source3/lib/util_sock.c:941(matchname)
Apr 10 23:15:47 freenas smbd[22320]:  matchname: host name/name mismatch: 192.168.0.90 != (NULL)
Apr 10 23:15:47 freenas smbd[22320]: [2014/04/10 23:15:47.854122,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Apr 10 23:15:47 freenas smbd[22320]:  matchname failed on 192.168.0.90

I've opened a bug : https://bugs.freenas.org/issues/4780

 

[pilotjunky]

9.2.1.4 BETA has been rock solid for me all week versus the 9.2.1.3 Release. Sorry, I can't comment on your issues ... someone more knowledgeable than I will have to chime in.

 

[marcevan]

In your CIFS settings, can you share the max version of Samba you're operating under? Should be down near the bottom of the CIFs settings.

 

[Youri Andropov]

server max protocol = SMB3

 

[matt_man22]

Sorry but I still have the issue, even with 9.2.1.4-beta.

Code:

[root@freenas ~]# uname -a
FreeBSD freenas.local 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #0 r262572+5356990: Tue Apr  8 10:44:24 PDT 2014    root@build.ixsystems.com:/home/jkh/9.2.1-BRANCH/freenas/os-base/amd64/tank/home/jkh/9.2.1-BRANCH/freenas/FreeBSD/src/sys/FREENAS.amd64  amd64
[root@freenas ~]# grep smbd /var/log/messages | tail -10
Apr 10 22:16:53 freenas smbd[21711]: [2014/04/10 22:16:53.690025,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Apr 10 22:16:53 freenas smbd[21711]:  matchname failed on 192.168.0.90
Apr 10 22:43:47 freenas smbd[21977]: [2014/04/10 22:43:47.754343,  0] ../source3/lib/util_sock.c:941(matchname)
Apr 10 22:43:47 freenas smbd[21977]:  matchname: host name/name mismatch: 192.168.0.90 != (NULL)
Apr 10 22:43:47 freenas smbd[21977]: [2014/04/10 22:43:47.754460,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Apr 10 22:43:47 freenas smbd[21977]:  matchname failed on 192.168.0.90
Apr 10 23:15:47 freenas smbd[22320]: [2014/04/10 23:15:47.854002,  0] ../source3/lib/util_sock.c:941(matchname)
Apr 10 23:15:47 freenas smbd[22320]:  matchname: host name/name mismatch: 192.168.0.90 != (NULL)
Apr 10 23:15:47 freenas smbd[22320]: [2014/04/10 23:15:47.854122,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Apr 10 23:15:47 freenas smbd[22320]:  matchname failed on 192.168.0.90

I've opened a bug : https://bugs.freenas.org/issues/4780

I found disabling "Hostnames lookups" in the CIFS settings to do the trick.

 

[marcevan]

I'm sticking with 9.2.1.3 for now.

My issues with Samba/CIFS were only on Windows 8 and Windows 7 is fine.

I can live with Transmission not being in the tree view and getting a 500 or 502 error.

When I see freenas go from 9.2.1.x to 9.2.2 or higher, I'll then take a look.

 

[rk1]

I upgraded from 9.1.1 to 9.2.1.3 and it has been a nightmare. I would not suggest anyone use this version. At first it was totally unusable, adding "change notify = no" + "kernel change notify = no" to the CIFS config made it slightly bareable, but I have constant samba panics and terrible performance or a 20 user file server.

my question is.. samba was still at 3.x on freenas 9.2; can I go back to this 9.2 version but still use the same 2TB ZFS (lz4 enabled) volume I created in 9.2.1.3?

or is there any way to install samba 3x on freenas 9.2.1.3? that would fix all my problems!

 

[marcevan]

You can set the maximum Samba level in play at the bottom of the CIFS settings. Samba 3_00 is in play with 9.2.1.3 as is Samba3 but I'm not sure the difference between the two.

 

[rk1]

thank you marcevan - yeah i already have it set to SMB2 min & max. i just wish i could somehow switch back to samba 3x :|

 

[marcevan]

You should be able to...in 9.2.1.3 it's just a matter of picking that and restarting the service.

 

[rk1]

You should be able to...in 9.2.1.3 it's just a matter of picking that and restarting the service.

i meant the actual samba version. currently it's 4.1.6. I want to use 3.6.17 for example.

 

[marcevan]

Best bet is to monitor the freenas development threads and see if Samba gets a further extension into v4 territory.

I'm staying put though, as first into the pool isn't always the best position.

 

[rk1]

Best bet is to monitor the freenas development threads and see if Samba gets a further extension into v4 territory.

I'm staying put though, as first into the pool isn't always the best position.

yes, my mistake for sure for thinking a 'release' version would be stable.

can only blame myself.

 

[Gavin]

I'm using 9.2.1.4.1.

So as others have suggested, setting maximum protocol to SMB2 fixed the issue with Windows 8.1 not connecting to CIFS shares. Plex works on my Samsung SmartTV, too. However, I am unable to connect to the CIFS shares on my Android phone using FolderSync no matter what. I used to have my phone copy itself to my NAS server every night, but it hasn't been able to do that ever since I upgraded to 9.2.1.4.1. Trying to scan the network for shares just has it keep on searching. Are they actually addressing the issue with Samba?