Announcing FreeNAS 9.2.1-RELEASE

[jyavenard]

Installed yesterday, very smooth upgrade as usual.

And got hit with the CIFS problem as well, no sure if I just should wait or go back to 9.2.0 for the time being.

Quick question: is NFSv4 enabled in 9.2.1 ?

 

[cyberjock]

NFSv4 doesn't exist in FreeNAS at all.

 

[jyavenard]

NFSv4 doesn't exist in FreeNAS at all.

well, not quite...
https://bugs.freenas.org/issues/3546

thought it was going to be official in 9.2.1; but it's for 9.2.2

 

[cyberjock]

well, not quite...
https://bugs.freenas.org/issues/3546

thought it was going to be official in 9.2.1; but it's for 9.2.2

No. I've never been told it was in 9.2.1. I've always been told:

9.2.0 - updated afp service
next release - updated samba
following release - updated nfs

/shrug

It doesn't matter. NFSv4 isn't available in any release(beta or otherwise) I've seen.. yet. I know LOTS of people have been asking about NFSv4 here and IRC. And when 9.2.0 came out with an updated AFP(the least used of them all) and I thought we were gonna have a revolt over it. Plenty of people asked "why the hell do you update the least used when the other 2 need updated and have FAR more users. I bet NFS( the middle of the road for "most used" from what I've seen) would have affected an order of magnitude(or two) more users than the AFP update did. But, eh, i'm not the boss. For that, blame jkh.

 

[jyavenard]

the trick of touching file /etc/nfsv4_enable seems to work so far. just mounted some directories over nfsv4. Will see how reliable that is

 

[jkh]

Installed yesterday, very smooth upgrade as usual.

And got hit with the CIFS problem as well, no sure if I just should wait or go back to 9.2.0 for the time being.

Quick question: is NFSv4 enabled in 9.2.1 ?

Anyone having CIFS problems, please chime in on https://bugs.freenas.org/issues/4148 - we need to figure out what is going on here!

As others have noted, NFSv4 is not a supported feature of FreeNAS right now. There's the "easter egg" file you can touch, but there's no UI for it and unless you know exactly what you're doing, any configuration changes you make will go away, so definitely an "at your own risk" sort of feature.

 

[jyavenard]

this isn't the ticket related to the read-only issue...

 

[jkh]

this isn't the ticket related to the read-only issue...

Please open a new ticket (or comment in another existing one) as appropriate then. Thanks.

"Me too" comments are useful - they let us know how severe a problem is an give us a wider corpus of repro cases to work with. Don't be afraid of filing duplicate reports (if you can't find one suitable) either. We will take care of marking them thusly.

 

[Cosmo_Kramer]

Anyone having CIFS problems, please chime in on https://bugs.freenas.org/issues/4148 - we need to figure out what is going on here!

I reverted back to 9.2.0, but is there still something I can do to help with troubleshooting?

 

[GaiusBaltar]

just finished upgrading (from 9.2.0). no issues so far. CIFS looks good, jails all up and running.

hopefully the update NUT to 2.7.1 gets rid of my UPS disconnected messages in syslog :)

 

[Milkwerm]

GUI upgrade from 9.1.1 to 9.2.1 all good here. Using Active Directory for the CIFS shares. Not seeing any issues with it.

<EDIT>
OK.. seeing a lot of these entries now

Feb 11 10:37:31 WFANAS01 smbd[25884]: [2014/02/11 10:37:31.509904, 0] ../source3/smbd/oplock.c:333(oplock_timeout_handler)
Feb 11 10:37:31 WFANAS01 smbd[25884]: Oplock break failed for file <PATH TO FILE>.xlsx -- replying anyway

any Idea how to get rid of the Oplock messages?

 

[GaiusBaltar]

update. i do appear to have one CIFS related issue. I'm seeing the following get spammed in syslog when accessing my CIFS shares:

Code:

Feb 10 15:56:50 freeNAS smbd[17938]: [2014/02/10 15:56:50.212862,  0] ../lib/util/charset/convert_string.c:438(convert_string_talloc_handle)
Feb 10 15:56:50 freeNAS smbd[17938]:  Conversion error: Illegal multibyte sequence(é)
Feb 10 15:56:50 freeNAS smbd[17938]: [2014/02/10 15:56:50.212887,  0] ../lib/util/charset/convert_string.c:438(convert_string_talloc_handle)
Feb 10 15:56:50 freeNAS smbd[17938]:  Conversion error: Illegal multibyte sequence(é)

UPDATE: scratch that. looks like there was an offending folder with illegal naming convention. once it was deleted via ssh then CIFS restarted via gui, error seems to have stopped.

Just a warning to those who are considering upgrading to this version, CIFS gave read-only access to nonowners even though they had write permission given to them.
The bug is reported here:

https://bugs.freenas.org/issues/4151

confirmed this myself. my robocopy script to copy data from my local machine to my freeNAS CIFS share errored out with Error 5 due to having group ownership on the freenas side, but not user ownership.

 

[Savell Martin]

I have the opportunity to move my data off my FreeNAS server (as im still in the process of setting it up).
My question is, would it be better to download and do a totally clean install of 9.2.1 rather than upgrading from 9.2?
As in re-create new clean volumes and everything with the new Release?

Or is there no difference with upgrading?

 

[Rich N]

the ability for FreeNAS to be a Windows Domain Controller

What does this mean exactly? It can literally be a domain controller? Or does it mean that its suitable for an active directory file system supporting snapshots? I dont get it.

Edit.
Thank you for the quick release.

 

[jkh]

What does this mean exactly? It can literally be a domain controller?

Correct. It can literally be a Domain Controller.

 

[Rich N]

Correct. It can literally be a Domain Controller.

Thanks. Still confused but thanks. I'll be looking through the docs tomorrow. Active directory domain controller, hmm.

 

[SeaFox]

Ubuntu jails still appear to be worthless on x86 (can't access shell).
Thought that was one of the tickets that was supposed to be fixed in this update. :-/

 

[jyavenard]

Have there been any changes in regards to intel network drivers for i210 controller?

I haven't tested immediately before the upgrade.
But using iperf between linux -> freenas: I now only get 437Mbit/s
freenas -> linux and I get 942Mbit/s using LAN1 (gigabit) and 990Mbit/s using LAN2 (gigabit with jumbo frames)

used to get exactly the same values both ways :(

 

[Sir.Robin]

Wow it's released!! Been busy with a FW issue on my board.

Anyhow: Congrats!! Downloading straight away. :)

Have the "copy from snapshots" been fixed? Couldn't find the ticket for it.

 

[Savell Martin]

Question is this a bug that needs to be filed?
Feb 11 22:12:19 freenas smbd[24674]: [2014/02/11 22:12:19.534761, 0] ../source3/lib/util_sock.c:941(matchname)
Feb 11 22:12:19 freenas smbd[24674]: matchname: host name/name mismatch: 192.168.1.8 != (NULL)
Feb 11 22:12:19 freenas smbd[24674]: [2014/02/11 22:12:19.534802, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Feb 11 22:12:19 freenas smbd[24674]: matchname failed on 192.168.1.8

Im seeing this quite a bit, its from my Sonos since the upgrade to 9.2.1.
But some other machines are also doing it.

Also I get this report every day:
Feb 11 17:07:01 freenas kernel: ugen0.3: <vendor 0x0451> at usbus0
Feb 11 17:07:01 freenas kernel: uhub4: <vendor 0x0451 product 0x8043, class 9/0, rev 2.10/1.00, addr 3> on usbus0
Feb 11 17:07:01 freenas kernel: uhub4: MTT enabled
Feb 11 17:07:02 freenas kernel: uhub4: 4 ports with 4 removable, self powered
Feb 11 22:06:14 freenas kernel: ugen0.3: <vendor 0x0451> at usbus0 (disconnected)
Feb 11 22:06:14 freenas kernel: uhub4: at uhub2, port 2, addr 3 (disconnected)
Feb 11 22:06:24 freenas kernel: ugen0.3: <vendor 0x0451> at usbus0
Feb 11 22:06:24 freenas kernel: uhub4: <vendor 0x0451 product 0x8043, class 9/0, rev 2.10/1.00, addr 3> on usbus0
Feb 11 22:06:24 freenas kernel: uhub4: MTT enabled
Feb 11 22:06:29 freenas kernel: uhub_attach: getting USB 2.0 HUB descriptor failed,error=USB_ERR_TIMEOUT
Feb 11 22:06:29 freenas kernel: device_attach: uhub4 attach returned 6