Where did you read about 3.1 ?

Read it

http://www.nexenta.com/corp/newsflashes/102-2011/942-nexenta-releases-namespace-cluster-for-simplifying-management-of-scaleout-storage-environments

and

http://www.nexenta.com/corp/nexentastor-overview/nexentastor-releases/nexentastor-31

David

Im sure its not really available yet despite what the press release says.

What I have been told (by 2 people in nexenta), was around 1 month ago, the 3.1 release would be out shortly and then last week that it was imminet.

See @gedamore on Twitter why 3.1 hasn't been released yet - but yes, it really looks imminent. http://twitter.com/#!/gedamore/status/83772599867420672

Thanks for the info.

Any update on the release of 3.1? Any news on what will be changing (specifically, what version of zpool will be included and whether or not vmxnet3 will work?)?

What was made public is the SCSI UNMAP support for COMSTAR so ZFS according to the illumos-dev list this is was said to be included in 3.1 and was integrated in illumos after some polishing.

And there is also another update from @gedamore: https://twitter.com/#!/gedamore/status/87890242627051520

So the show-stopper must have been something quite important - what is clear now is that it's not something in the closed part of NexentaStor but something in the core OS/Net. - Let's see if some of the ZFS-corruption bugfixes from Delphix(1) and Joyent(2) people will also be part of it.

(1) http://lists.illumos.org/pipermail/illumos-commits/2011-May/000182.html (2) http://lists.illumos.org/pipermail/illumos-commits/2011-April/000159.html

What I have been told was that it is an iSCSI failover bug that's holding it back.

Does anyone know if there is update as to the 3.1 release date? We are eagerly awaiting the release - specificially the CIFS changes to further improve our Veeam backup target.

If you join the box to the domain Veeam works great with it. This is more of a Veeam issue in how it connects to shares. I've had trouble with machines (windows included) that are not joined to the domain. You also need administrative access to the share, full permissions.

Nexenta has a good doc on joining to a Win200* domain and works. Just follow step by step. http://www.nexenta.com/corp/static/docs-stable/NexentaStor-WindowsAD-Integration.pdf

some others that can help.... http://www.nexenta.com/corp/nexentastor-faq-table/651-how-to-join-nexentastor-to-active-directory-windows-2008-domain http://solori.wordpress.com/2010/06/15/nexentastor-cifs-shares-with-active-directory-authentication/

I to am awaiting 3.1 ;-)

It appears to have been release, the CE version:

http://www.nexentastor.org/news/18

The "upgrade -r 3.1" command didn't work for me. I have done all the updates/upgrade for version 3.0.5, but this is what I got:

nmc@nexenta3:/$ setup appliance upgrade -r 3.1 Cleanup upgrade caches (note: cleanup is generally not required and can be skipped in most cases; if you say Yes, prepare to wait for software upgrade to complete a bit longer) ? Yes Warning: Use of uninitialized value in hash (element) Warning: Use of uninitialized value in concatenation (.) or (string) OperationFailed: Release '' is not available

Peter Valadez wrote:

The "upgrade -r 3.1" command didn't work for me. I have done all the updates/upgrade for version 3.0.5, but this is what I got:

nmc@nexenta3:/$ setup appliance upgrade -r 3.1 Cleanup upgrade caches (note: cleanup is generally not required and can be skipped in most cases; if you say Yes, prepare to wait for software upgrade to complete a bit longer) ? Yes Warning: Use of uninitialized value in hash (element) Warning: Use of uninitialized value in concatenation (.) or (string) OperationFailed: Release '' is not available

3.1 was pulled, no eta that I'm aware of on getting it back up for download.

Thanks Jason!

What does that mean for already deployed CE 3.1? Can they be updated the usual way when 3.1 wil be fixed?

Regards, Gernot

Jason Litka wrote:

3.1 was pulled, no eta that I'm aware of on getting it back up for download.

Hello, is there information available, why it was pulled? Would be interested in serious probs as I have already two setups running and even if they are small and not mission critical, knowing what happend might be good.

Thanks and greetings,

Chris

Upgrade problems, failing, or missing components: http://www.nexentastor.org/boards/2/topics/2955#message-2960

I'm a little confused on the current status of 3.1 CE. We had a box that was randomly dropping out on CIFS under 3.0.5 under heavy load. We upgraded to 3.1 - everything has been running fine since - apart from the iSCSI LUN mappings UI which didn't work under 3.1 (so we had to issue the LUN mappings from the CLI). If I look at the download options from this page , they are still pointing to the 3.1 iso. http://www.nexentastor.org/projects/site/wiki/CommunityEdition

Is it just the upgrade via the "upgrade" command that has been pulled, or should it be the iso as well?

Indeed it looks like that. The CE 3.1 ISO is still available, EE points to 3.0.5.

According to the Link by David it seems there have been issues with the "the software delivery mechanism" - which I'd interpret as problem with the packaging and/or update mechanism. - But it isn't clear if your COMSTAR-related problem is also part of this.

Honestly I also been able to bust the LUN mapping configuration so STMF and iscsi-target didn't come up. I havent found out if it was an update or a problem with the SCSI target mode framework. (I had to get a virgin stmf config from a fresh install, import it and re-do the LUN-Mapping because It didn't want to use the previously working configuration)

A bird has tweeted that NexentaStor 3.1 is coming back as 3.1.1:

https://twitter.com/#!/craigmorgan/status/104281513000054784

great stuff! Just upgraded from 3.1 to 3.1.1 via "setup appliance upgrade" and "setup appliance upgrade nms" and rebooted the SAN, and now the iSCSI LUN mappings are working as they should and the UI is reflecting the correct mappings. Now if only NexentaStor could support VAAI for ESXi4.1 (I believe it is supported under ESXi5).

Upgrading now as well. Will report back any findings.

Ashley Watson wrote:

great stuff! Just upgraded from 3.1 to 3.1.1 via "setup appliance upgrade" and "setup appliance upgrade nms" and rebooted the SAN, and now the iSCSI LUN mappings are working as they should and the UI is reflecting the correct mappings. Now if only NexentaStor could support VAAI for ESXi4.1 (I believe it is supported under ESXi5).

v3.1.1 still works on ESXi 5.0 but still not supported on 4.1 :(

Ashley Watson wrote:

great stuff! Just upgraded from 3.1 to 3.1.1 via "setup appliance upgrade" and "setup appliance upgrade nms" and rebooted the SAN, and now the iSCSI LUN mappings are working as they should and the UI is reflecting the correct mappings. Now if only NexentaStor could support VAAI for ESXi4.1 (I believe it is supported under ESXi5).

Why is there a separate command to update NMS? Is there more to upgrade than 'appliance' and 'nms'. I've never done that before the only upgrade command that I know is 'setup appliance upgrade'. I think this is also the only option mentioned in the user-manual.

"setup appliance upgrade" upgrades NMS too, so I'm not too sure what the point of the separate command is.

FWIW I now have problems connecting to my iSCSI targets from my Mac's now. The initiator software throws an error. I had to roll back to 3.0.5. But that's not Nexenta's fault nearest I can tell.

Also... I noticed you can now modify target and initiator groups from within the GUI rather than having to rely on CLI, even in the CE edition.

I've never seen the setup appliance upgrade nms either, but seems to work in the CE edition. To do the upgrade to 3.1 I still had to run "setup appliance upgrade -r 3.1". However, after doing this I got an error report saying my volumes are older than set value. What's up with that?

FAULT: FAULT: Appliance : nexenta3 (OS v3.1.1, NMS v3.1.0 (r9356)) FAULT: Machine SIG : D45D9EBLF FAULT: Primary MAC : 0:e0:81:46:24:88 FAULT: Time : Fri Aug 19 10:08:18 2011 FAULT: Trigger : volume-check FAULT: Fault Type : ALARM FAULT: Fault ID : 1500 FAULT: Fault Count : 1 FAULT: Severity : NOTICE FAULT: Description : Versions of the volumes volume1, volume2 are older than FAULT: : set value (28) FAULT:

! ! For more detais on this trigger click on link below: ! http://10.100.1.201:2000/data/runners?selected_runner=volume-check !

volume1 version is 26 volume2 version is 26

All right- to answer my own question...

See the end of 3.1 release notes: http://www.nexenta.com/corp/images/stories/pdfs/releasenotes3%201_v4.pdf

It's not required in 3.1, but you can upgrade the volume version with this:

nmc@nexenta3:/$ setup volume volume1 version-upgrade -r Upgrade volume 'volume1' from version '26' to system version '28'? Yes

For more explanation, see: setup volume version version-upgrade -h