Jordan Hubbard | 17 Jun 06:46 2014

http://download.freenas.org/nightlies/9.2.1.6/BETA/20140616/

In the wake of 9.2.1.6-BETA, we have quite a few more fixes to this build, in particular the experimental Kernel iSCSI (CTL) support in this build is substantially improved by these tickets being resolved:


The tl;dr version of the above is that we think that Windows 2012 clustering support now works with Kernel ISCSI and the issue that caused flipping between istgt (userland iSCSI) and CTL to make VMWare think you'd actually changed the LUNs should be fixed (so folks wanting to test the new Kernel iSCSI support with VMWare can do so easily but still revert back to istgt in the event of any problems).

We fixed the GRUB boot loader USB image (https://bugs.freenas.org/issues/5222).

AD / LDAP also now supports I18N characters, so folks like Jürgén Hørnqvôss-Schißtein should be happier trying to log into FreeNAS (https://bugs.freenas.org/issues/5015), but we are somewhat concerned about any possible regressions as a result of this change.  We don’t see any obvious ways in which this might have broken AD/LDAP support for english users, but we would still really appreciate folks taking special care to test this case.  If you use AD or LDAP with FreeNAS (particularly if you are outside the US), we would really appreciate you taking some time to test this nightly build!

Thanks!

- The FreeNAS Development Team






<div>In the wake of 9.2.1.6-BETA, we have quite a few more fixes to this build, in particular the experimental Kernel iSCSI (CTL) support in this build is substantially improved by these tickets being resolved:<div><br></div>
<div>
<span class="Apple-tab-span">	</span><a href="https://bugs.freenas.org/issues/5230">https://bugs.freenas.org/issues/5230</a>
</div>
<div>
<span class="Apple-tab-span">	</span><a href="https://bugs.freenas.org/issues/5217">https://bugs.freenas.org/issues/5217</a>
</div>
<div>
<span class="Apple-tab-span">	</span><a href="https://bugs.freenas.org/issues/5216">https://bugs.freenas.org/issues/5216</a>
</div>
<div>
<span class="Apple-tab-span">	</span><a href="https://bugs.freenas.org/issues/5205">https://bugs.freenas.org/issues/5205</a>
</div>
<div>
<span class="Apple-tab-span">	</span><a href="https://bugs.freenas.org/issues/4003">https://bugs.freenas.org/issues/4003</a>
</div>
<div>
<span class="Apple-tab-span">	</span><a href="https://bugs.freenas.org/issues/5230">https://bugs.freenas.org/issues/5230</a>
</div>
<div><div>
<span class="Apple-tab-span">	</span><a href="https://bugs.freenas.org/issues/4003">https://bugs.freenas.org/issues/4003</a>
</div></div>
<div>
<span class="Apple-tab-span">	</span><a href="https://bugs.freenas.org/issues/4929">https://bugs.freenas.org/issues/4929</a>
</div>
<div><br></div>
<div>The tl;dr version of the above is that we think that Windows 2012 clustering support now works with Kernel ISCSI and the issue that caused flipping between istgt (userland iSCSI) and CTL to make VMWare think you'd actually changed the LUNs should be fixed (so folks wanting to test the new Kernel iSCSI support with VMWare can do so easily but still revert back to istgt in the event of any problems).</div>
<div><br></div>
<div>We fixed the GRUB boot loader USB image (<a href="https://bugs.freenas.org/issues/5222">https://bugs.freenas.org/issues/5222</a>).</div>
<div><br></div>
<div>AD / LDAP also now supports I18N characters, so folks like J&uuml;rg&eacute;n H&oslash;rnqv&ocirc;ss-Schi&szlig;tein should be happier trying to log into FreeNAS (<a href="https://bugs.freenas.org/issues/5015">https://bugs.freenas.org/issues/5015</a>), but we are somewhat concerned about any possible regressions as a result of this change. &nbsp;We don&rsquo;t see any obvious ways in which this might have broken AD/LDAP support for english users, but we would still really appreciate folks taking special care to test this case. &nbsp;If you use AD or LDAP with FreeNAS (particularly if you are outside the US), we would really appreciate you taking some time to test this nightly build!</div>
<div><br></div>
<div>Thanks!</div>
<div><br></div>
<div>- The FreeNAS Development Team</div>
<div><br></div>
<div><br></div>
<div><br></div>
<div>
<br><div><br></div>
<div><br></div>
</div>
</div>
Philip Robar | 11 Jun 09:36 2014
Picon

Recovering from FreeNAS 10.0.0 breaking my server.

Since Samba/SMB/CIFS is broken by FreeNAS-10.0.0-ALPHA-99827dc-x64 and 9.2.2 nightlies (what I was running) have disappeared and 9.3 doesn't exist in the downloads can I use my saved 9.2.2 db file with 9.2.1.6 or do I have to start over from scratch?

Phil

<div><div dir="ltr">Since Samba/SMB/CIFS is broken by FreeNAS-10.0.0-ALPHA-99827dc-x64 and 9.2.2 nightlies (what I was running) have disappeared and 9.3 doesn't exist in the downloads can I use my saved 9.2.2 db file with 9.2.1.6 or do I have to start over from scratch?<div>

<br>
</div>
<div>Phil</div>
<div><br></div>
</div></div>
Jordan Hubbard | 10 Jun 08:03 2014

http://download.freenas.org/nightlies/9.2.1.6/BETA/20140609/

We’re getting down to our last handful of bugs for 9.2.1.6-BETA (and very close to an “official BETA”
release at this point).  Nonetheless, the 20140609 build is a really good one and fixes a number of AD
problems that crept in due to an incomplete merge from the master branch and also imports OpenSSL 0.9.8za,
which fixes a number of security vulnerabilities.
See https://bugs.freenas.org/projects/freenas/issues?query_id=78 for a complete list of all bugs
closed in 9.2.1.6 so far, 9 being closed today in this build alone (Hmm, 9 on 6/09 - nice symmetry!).

Thanks, as always, for your testing efforts - they’re all helping to make 9.2.1.6 a very good build!

- Jordan

Jonathon Royle | 9 Jun 00:11 2014
Picon

9.2.1.6/BETA/20140607 testing results

Jordan,

I have not had chance for an extensive test but for this latest release is a backward step for me

FreeNAS-9.2.1.6-BETA-d78e1f0-x64

#5162  FreeNAS crashes when trying to do clean install on Xenserver host

#5163 AD Groups not in permissions drop down list (owners are) on 9.2.1.5 upgrade

When 9.2.16 is released will there be a guide on how to correctly reset CIFS permissions when upgrading from a 9.2.1.5 (or earlier) release ?  I used the GUI option "Apply Default Permissions" on CIFS share however I note that 'Inherit ACL's' is still checked (but I believe this is not recommended)


Regards,

Jon

 
From: freenas-testing-bounces-PD4FTy7X32mTkUHaTc9RUQ@public.gmane.orgas.org [freenas-testing-bounces-PD4FTy7X32lNMZ+623a0Tti2O/JbrIOy@public.gmane.org] on behalf of Jordan Hubbard [jkh-IxGJvsi74X2akBO8gow8eQ@public.gmane.org]
Sent: 08 June 2014 04:02
To: freenas-testing-PD4FTy7X32lNMZ+623a0Tti2O/JbrIOy@public.gmane.org
Subject: [FreeNAS-testing] Another good build to test: http://download.freenas.org/nightlies/9.2.1.6/BETA/20140607/

This build features some key improvements over the last "semi-official nightly" we asked everyone to test:
  • Samba updated to 4.1.8, ldv to version 1.1.17, and tdb to version 1.3.0
  • Netatalk updated to 3.1.2
  • Added extra safety belts and sane ACL behavior for CIFS sharing.
    • Now when a ZFS dataset is created with the type set to Windows, or a Windows share is created on an existing dataset with "Apply Default Permissions" checked (a new GUI option in the CIFS sharing dialog), FreeNAS will make sure that the ACLs / ownerships are set properly for Windows and it will also make sure that the behavior of chmod(2) is set in ZFS such that it does not also destroy the Inherit, Delete or Delete Child ACLs whenever it's used.
  • The ISO installation image can, in addition to being used as CD install media, can also be written to a USB device and booted directly now. To facilitate this, the installer now uses the GRUB boot manager.
  • The .system dataset code has been completely refactored, hopefully addressing some of the reporting graph issues people havebeen seeing.
As always, a principle goal of 9.2.1.6 is to make CIFS more useable, and more bullet-proof, than in previous releases. Any emphasis on testing CIFS and AFP would therefore be appreciated!

Thanks!

The FreeNAS Development Team
<div>
<div>Jordan,<br><br>
I have not had chance for an extensive test but for this latest release is a backward step for me<br><br>
FreeNAS-9.2.1.6-BETA-d78e1f0-x64<br><br><a href="https://bugs.freenas.org/issues/5162" title="FreeNAS crash on ISO boot/installation">#5162</a>&nbsp; FreeNAS crashes when trying to do clean install on Xenserver host<br><br><a href="https://bugs.freenas.org/issues/5163" title="Windows AD Group not available in permissions function">#5163</a> AD Groups not in permissions drop down list (owners are) on 9.2.1.5 upgrade<br><br>
When 9.2.16 is released will there be a guide on how to correctly reset CIFS permissions when upgrading from a 9.2.1.5 (or earlier) release ?&nbsp; I used the GUI option "<span><span>Apply Default&nbsp;</span></span><span><span>Permissions"</span></span>
 on CIFS share however I note that 'Inherit ACL's' is still checked (but I believe this is not recommended)
<br><br><br>
Regards,<br><br>
Jon<br><br>
&nbsp;<br><div>
<div>From: freenas-testing-bounces@...as.org [freenas-testing-bounces@...] on behalf of Jordan Hubbard [jkh@...]<br>Sent: 08 June 2014 04:02<br>To: freenas-testing@...<br>Subject: [FreeNAS-testing] Another good build to test: http://download.freenas.org/nightlies/9.2.1.6/BETA/20140607/<br><br>
</div>
<div></div>
<div>
<div class="messageContent">
<blockquote class="messageText ugc baseHtml">
This build features some key improvements over the last "semi-official nightly" we asked everyone to test:<br><ul>
<li><span><span>Samba updated to 4.1.8,&nbsp;</span><span>ldv</span><span>&nbsp;to version 1.1.17, and tdb to version
 1.3.0</span></span></li>
<li><span><span>Netatalk updated to 3.1.2</span></span></li>
<li>
<span><span>Added extra safety belts and sane ACL behavior for CIFS sharing.</span></span>
<ul><li>
<span><span>Now when a ZFS dataset is created with the type set to Windows, or a&nbsp;</span></span><span><span>Windows
 share is created on an existing dataset with "Apply Default&nbsp;</span></span><span><span>Permissions" checked (a new GUI option in the CIFS sharing dialog),&nbsp;</span></span><span><span>FreeNAS
 will make sure that the ACLs / ownerships are set properly f</span></span><span><span>or Windows and it will also make sure that the behavior of chmod(2)&nbsp;</span></span><span><span>is
 set in ZFS such that it does not also destroy the Inherit, Delete&nbsp;</span></span><span><span>or Delete Child ACLs whenever it's used.</span></span>
</li></ul>
</li>
<li>
<span><span>The ISO installation image can, in addition to being used as CD install&nbsp;</span></span><span><span>media,
 can also be written to a USB device and booted directly now. To&nbsp;</span></span><span><span>facilitate this, the installer now uses the GRUB boot manager.</span></span>
</li>
<li><span><span>The .system dataset code has been completely refactored, hopefully addressing some of the reporting graph issues people&nbsp;</span><span>have</span><span>been
 seeing.</span></span></li>
</ul>
As always, a principle goal of 9.2.1.6 is to make CIFS more useable, and more bullet-proof, than in previous releases. Any emphasis on testing CIFS and AFP would therefore be appreciated!<br><br>
Thanks!<br><br>
The FreeNAS Development Team</blockquote>
</div>
<div class="messageMeta">
<div class="privateControls"></div>
</div>
</div>
</div>
</div>
</div>
Jordan Hubbard | 8 Jun 05:02 2014

http://download.freenas.org/nightlies/9.2.1.6/BETA/20140607/

This build features some key improvements over the last "semi-official nightly" we asked everyone to test:
  • Samba updated to 4.1.8, ldv to version 1.1.17, and tdb to version 1.3.0
  • Netatalk updated to 3.1.2
  • Added extra safety belts and sane ACL behavior for CIFS sharing.
    • Now when a ZFS dataset is created with the type set to Windows, or a Windows share is created on an existing dataset with "Apply Default Permissions" checked (a new GUI option in the CIFS sharing dialog), FreeNAS will make sure that the ACLs / ownerships are set properly for Windows and it will also make sure that the behavior of chmod(2) is set in ZFS such that it does not also destroy the Inherit, Delete or Delete Child ACLs whenever it's used.
  • The ISO installation image can, in addition to being used as CD install media, can also be written to a USB device and booted directly now. To facilitate this, the installer now uses the GRUB boot manager.
  • The .system dataset code has been completely refactored, hopefully addressing some of the reporting graph issues people havebeen seeing.
As always, a principle goal of 9.2.1.6 is to make CIFS more useable, and more bullet-proof, than in previous releases. Any emphasis on testing CIFS and AFP would therefore be appreciated!

Thanks!

The FreeNAS Development Team
<div>
<div class="messageContent"><blockquote class="messageText ugc baseHtml">This build features some key improvements over the last "semi-official nightly" we asked everyone to test:<br><ul>
<li><span><span>Samba updated to 4.1.8,&nbsp;</span><span>ldv</span><span>&nbsp;to version 1.1.17, and tdb to version 1.3.0</span></span></li>
<li><span><span>Netatalk updated to 3.1.2</span></span></li>
<li>
<span><span>Added extra safety belts and sane ACL behavior for CIFS sharing.</span></span><ul><li>
<span><span>Now when a ZFS dataset is created with the type set to Windows, or a&nbsp;</span></span><span><span>Windows share is created on an existing dataset with "Apply Default&nbsp;</span></span><span><span>Permissions" checked (a new GUI option in the CIFS sharing dialog),&nbsp;</span></span><span><span>FreeNAS will make sure that the ACLs / ownerships are set properly f</span></span><span><span>or Windows and it will also make sure that the behavior of chmod(2)&nbsp;</span></span><span><span>is set in ZFS such that it does not also destroy the Inherit, Delete&nbsp;</span></span><span><span>or Delete Child ACLs whenever it's used.</span></span>
</li></ul>
</li>
<li>
<span><span>The ISO installation image can, in addition to being used as CD install&nbsp;</span></span><span><span>media, can also be written to a USB device and booted directly now. To&nbsp;</span></span><span><span>facilitate this, the installer now uses the GRUB boot manager.</span></span>
</li>
<li><span><span>The .system dataset code has been completely refactored, hopefully addressing some of the reporting graph issues people&nbsp;</span><span>have</span><span>been seeing.</span></span></li>
</ul>As always, a principle goal of 9.2.1.6 is to make CIFS more useable, and more bullet-proof, than in previous releases. Any emphasis on testing CIFS and AFP would therefore be appreciated!<br><br>Thanks!<br><br>The FreeNAS Development Team</blockquote></div>
<div class="messageMeta"><div class="privateControls"></div></div>
</div>
Rich | 3 Jun 04:25 2014
Picon

HP Microserver N40L and Freenas 9.2.1.6 Beta & -cead1b-x64.iso install

Hello,

I currently run Freenas 8.3.2 Release on an HP Microserver N40L.
I am running with 8GB ECC DRAM booting from a 4GB USB stick.
I currently run (2) 2TB Hitachi drives in a mirror configuration with SSH, SFTP and CIFS services running.

I have new upgraded drives waiting and, as opposed to upgrading the system, I grabbed a new USB stick and attempted to install 9.2.1.5. fresh.
It failed and I put the old usb stick and drives ba ck into the chassis.
I upgraded the bios a few days later.

I tried the process again tonight using 9.2.1.6 Beta 7.

When I first tried 9.2.1.5, it hung with the message:
freenas mDNS responder : mDNS_Register_internal: ERROR! Tried to register AuthRecord 0000000800D01180 78.68.94.10.in-addr.arpa (PTR) that's already in the list.

This message still came up tonight. I unplugged the ethernet, and after a few minutes, the system came up.
Once the system came up, I changed the IP and reset the static DHCP entry for FREENAS on my router and then logged in to the server at the new IP.

The subsequent and first reboot with the ethernet attached did not hang and the system booted properly to 9.2.1.6 beta 7.
It appears the system is useable, but will be reverting back to 8.3.2 for a bit longer. Hopefully not too much longer.

Could there be an issue with Freenas? Is there something I should check?

I didn't try installing again without unplugging the ethernet, but I can if it will help.

Rich












<div><div>
<div>Hello,</div>
<div><br></div>
<div>I currently run Freenas 8.3.2 Release on an HP Microserver N40L.</div>
<div>I am running with 8GB ECC DRAM booting from a 4GB USB stick.</div>
<div>I currently run (2) 2TB Hitachi drives in a mirror configuration with SSH, SFTP
 and CIFS services running.</div>
<div><br></div>
<div>I have new upgraded drives waiting and, as opposed to upgrading the system, I grabbed a new USB stick and attempted to install 9.2.1.5. fresh.</div>
<div>It failed and I put the old usb stick and drives ba
 ck into the chassis. <br>
</div>
<div>I upgraded the bios a few days later.</div>
<div><br></div>
<div>I tried the process again tonight using 9.2.1.6 Beta 7.</div>
<div><br></div>
<div>When I first tried 9.2.1.5, it hung with the
 message:</div>
<div>freenas mDNS responder : mDNS_Register_internal: ERROR! Tried to register AuthRecord 0000000800D01180 78.68.94.10.in-addr.arpa (PTR) that's already in the list.</div>
<div><br></div>
<div>This message still came up tonight. I unplugged the
  ethernet, and after a few minutes, the system came up.</div>
<div>Once the system came up, I changed the IP and reset the static DHCP entry for FREENAS on my router and then logged in to the server at the new IP.</div>
<div><br></div>
<div>The subsequent and first reboot with the ethernet attached did not hang and the system booted properly to 9.2.1.6 beta 7.</div>
<div>It appears the system
 is useable, but will be reverting back to 8.3.2 for a bit longer. Hopefully not too much longer.</div>
<div><br></div>
<div>Could there be an issue with Freenas? Is there something I should check?</div>
<div><br></div>
<div>I didn't try installing
 again without unplugging the ethernet, but I can if it will help.</div>
<div><br></div>
<div>Rich</div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div></div>
</div></div>
Jonathon Royle | 1 Jun 21:00 2014
Picon

Testing of 9.2.1.6 Beta

Following Jordan's note I have done some more testing on clean install of  FreeNAS-9.2.1.6-BETA-ec7b399-x64

Possible Bugs - feedback appreciated

The interfaces datagrid is empty after initial installation, though system has auto configured and found interface re0 and re1 and set via DHCP (also set nameserver and default route).  I was able to manually add the interface so that in future showed correctly.  Alternatively adding a vlan which uses re0 or re1 as physical interface will auto create physical interface record

Having set interface re0 with a static IP of 192.168.1.151/24 it would not allow me to set re1 in same subnet “The network 192.168.1.0/24 is already in use by another NIC”.  However it would allow configuration to 192.168.1.0/24 range via DHCP or via net console.  The error message suggests this is an intentional behaviour but I can’t think why.  Pls advise

 


Observations

All good on CIFS – I was not able to use chmod on freenas server or from Linux client to corrupt windows shares – share access granted via defined windows permissions.

 

NB Previous comments stand on Everyone being default allowed read access to new dataset as poor security practice, CIFS Local Master and Time Server for domain being default checked even for an AD deployment

 

 

Regards,

 

Jon

 

 

<div>
<div class="WordSection1">
<div>
<div>
<p class="MsoNormal"><span>Following Jordan's note I have done some more testing on clean install of&nbsp; FreeNAS-9.2.1.6-BETA-ec7b399-x64<br><br>Possible Bugs - feedback appreciated<br><br>
The interfaces datagrid is empty after initial installation, though system has auto configured and found interface re0 and re1 and set via DHCP (also set nameserver and default route).&nbsp; I was able to manually add the interface so that in future showed correctly.&nbsp;
 Alternatively adding a vlan which uses re0 or re1 as physical interface will auto create physical interface record<br><br>
Having set interface re0 with a static IP of 192.168.1.151/24 it would not allow me to set re1 in same subnet &ldquo;The network 192.168.1.0/24 is already in use by another NIC&rdquo;.&nbsp; However it would allow configuration to 192.168.1.0/24 range via DHCP or via net console.&nbsp;
 The error message suggests this is an intentional behaviour but I can&rsquo;t think why.&nbsp; Pls advise<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span><br>Observations<br><br><p></p></span></p>
<p class="MsoNormal"><span>All good on CIFS &ndash; I was not able to use chmod on freenas server or from Linux client to corrupt windows shares &ndash; share access granted via defined windows permissions.<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>NB Previous comments stand on Everyone being default allowed read access to new dataset as poor security practice, CIFS Local Master and Time Server for domain
 being default checked even for an AD deployment<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>Regards,<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>Jon<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
</div>
</div>
</div>
</div>
Jordan Hubbard | 30 May 00:22 2014

http://download.freenas.org/nightlies/9.2.1.6/BETA/20140529: This is another fine build you've gotten us into, Ollie.

Hi folks!

Well, it’s been awhile since a good candidate for 9.2.1.6-BETA testing was announced, and we are happy to say that http://download.freenas.org/nightlies/9.2.1.6/BETA/20140529/ is that build!

Lots of good stuff in this one.  We’ve fixed 41 tickets so far in 9.2.1-BRANCH since 9.2.1.5 was released, some of the most notable bugs/features being:

o  Added extra safety belts and sane ACL behavior for CIFS sharing.

Now when you create a ZFS dataset with the type set to Windows, or you create a Windows share on an existing dataset with “Default Permissions” checked (that’s a new GUI option in the CIFS sharing dialog), FreeNAS will make sure that the ACLs / ownerships are set properly for Windows and it will also make sure that the behavior of chmod(2) is set in ZFS such that it does not also destroy the Inherit, Delete or Delete Child ACLs whenever it’s used.  That was the old behavior, making chmod essentially a destructive operation as far as ACLs were concerned, and we’re pretty sure this explains a good number of the “I upgraded from 9.2.0->9.2.1.x and now my permissions are all broken in Windows!” reports, because one of the first thing folks try to do when they have a permission problem is reach for chown/chgrp/chmod, and that made Windows very unhappy up until now because Unix permissions and ACLs fought.

o The System Dataset now has its own Settings UI that allows you to control the placement of various sub-datasets under it.  RRD (collectd) data, for example, can now live on it’s own sub-dataset of the .system dataset 
 
o The System Dataset will now migrate if you change the pool assignment, preserving your data and also moving it off the previous pool.

o A new Virtualbox jail template has been added.  Supporting Virtualbox in a jail is as easy as creating an instance of this template.

Please test this build and let us know what your experience is like.  We’re down to just 11 tickets for 9.2.1.6-RELEASE, and some of them are pretty obscure, so we’re hoping that this build is actually pretty close to release quality for 99% of the FreeNAS user community!

Thanks,

- The FreeNAS Development Team



<div>Hi folks!<div><br></div>
<div>Well, it&rsquo;s been awhile since a good candidate for 9.2.1.6-BETA testing was announced, and we are happy to say that&nbsp;<a href="http://download.freenas.org/nightlies/9.2.1.6/BETA/20140529/">http://download.freenas.org/nightlies/9.2.1.6/BETA/20140529/</a> is that build!</div>
<div><br></div>
<div>Lots of good stuff in this one. &nbsp;We&rsquo;ve fixed&nbsp;<a href="https://bugs.freenas.org/projects/freenas/issues?query_id=78">41 tickets</a>&nbsp;so far in 9.2.1-BRANCH since 9.2.1.5 was released, some of the most notable bugs/features being:</div>
<div><br></div>
<div>o &nbsp;Added extra safety belts and sane ACL behavior for CIFS sharing.</div>
<div><br></div>
<div>Now when you create a ZFS dataset with the type set to Windows, or you create a Windows share on an existing dataset with &ldquo;Default Permissions&rdquo; checked (that&rsquo;s a new GUI option in the CIFS sharing dialog), FreeNAS will make sure that the ACLs / ownerships are set properly for Windows and it will also make sure that the behavior of chmod(2) is set in ZFS such that it does not also destroy the Inherit, Delete or Delete Child ACLs whenever it&rsquo;s used. &nbsp;That was the old behavior, making chmod essentially a destructive operation as far as ACLs were concerned, and we&rsquo;re pretty sure this explains a good number of the &ldquo;I upgraded from 9.2.0-&gt;9.2.1.x and now my permissions are all broken in Windows!&rdquo; reports, because one of the first thing folks try to do when they have a permission problem is reach for chown/chgrp/chmod, and that made Windows very unhappy up until now because Unix permissions and ACLs fought.</div>
<div><br></div>
<div>o The System Dataset now has its own Settings UI that allows you to control the placement of&nbsp;various sub-datasets under it.&nbsp;&nbsp;RRD (collectd) data, for example, can now live on it&rsquo;s own sub-dataset of the .system dataset&nbsp;<br>&nbsp;<br>o The System Dataset will now migrate if you change the pool assignment, preserving your data&nbsp;and also moving it off the previous pool.<br><br>
</div>
<div>o A new Virtualbox jail template has been added. &nbsp;Supporting Virtualbox in a jail is as easy as creating an instance of this template.</div>
<div><br></div>
<div>Please test this build and let us know what your experience is like. &nbsp;We&rsquo;re down to just&nbsp;<a href="https://bugs.freenas.org/projects/freenas/issues?query_id=59">11 tickets</a>&nbsp;for 9.2.1.6-RELEASE, and some of them are pretty obscure, so we&rsquo;re hoping that this build is actually pretty close to release quality for 99% of the FreeNAS user community!</div>
<div><br></div>
<div>Thanks,</div>
<div><br></div>
<div>- The FreeNAS Development Team</div>
<div><br></div>
<div><br></div>
<div><br></div>
</div>
Jonathon Royle | 27 May 00:28 2014
Picon

Re: Testing of FreeNAS-9.2.1.6-BETA-5429442-x64

Further update on the read-only andy deny issue on 9.2.1.5.  This does not relate to use of chmod, and pleasingly is not prevalent in 9.2.1.6 – not sure if intentional fix or not.  Issue for 9.2.1.6 is how best to unwind the permissions errors.

 

In 9.2.1.5

Create new file

# file: test.txt

# owner: jonathon

# group: domain admins

                group:jonathon:rwxpDdaARWcCo-:------:allow

                group:route:rwxpDdaARWcCo-:------:allow

                owner <at> :rw-p--aARWcCos:------:allow

                group <at> :rw-p--a-R-c--s:------:allow

                everyone <at> :rw-p--a-R-c--s:------:allow

 

Hmm this is not correct permissions to inherit but we know of this bug.  I need to edit as I don’t want everyone to be able to read files by default.

 

Reset permissions (via windows 7 client) to remove everyone read and just set to traverse folder

# file: test.txt

# owner: jonathon

# group: domain admins

                group:jonathon:rw-p--aARWcCo-:------:allow

                group <at> :rw-p--a-R-c---:------:allow

                everyone <at> :--x-----------:------:allow

                group:jonathon:rwxpDdaARWcCo-:------:allow

                group:route:rwxpDdaARWcCo-:------:allow

 

The file is now set read-only and there are unexpected permission changes!  Removed read only flag

 

# file: test.txt

# owner: jonathon

# group: domain admins

                owner <at> :r-x-----------:------:deny

                group:jonathon:rw-p--aARWcCo-:------:allow

                group:jonathon:rwxpDdaARWcCo-:------:allow

                group:route:rwxpDdaARWcCo-:------:allow

                owner <at> :-w-p--aARWcCos:------:allow

                group <at> :rwxp--a-R-c--s:------:allow

                everyone <at> :-wxp--a-R-c--s:------:allow

 

 

Same actions on 9.2.1.6

Original, set read-only, remove read-only.  Permission don’t change

# file: test.txt

# owner: ROYLEMINNS\jonathon

# group: ROYLEMINNS\domain admins

group:ROYLEMINNS\jonathon:rwxpDdaARWcCo-:------:allow

group:ROYLEMINNS\route:rwxpDdaARWcCo-:------:allow

                group <at> :rwxpDdaARWcCo-:------:allow

                everyone <at> :--x-----------:------:allow

 

 

Jon

 

 

 

From: Jonathon Royle
Sent: 26 May 2014 22:43
To: 'freenas-testing-PD4FTy7X32lNMZ+623a0Tti2O/JbrIOy@public.gmane.org'
Subject: Testing of FreeNAS-9.2.1.6-BETA-5429442-x64

 

Hi,

 

I have been testing CIFS on above release and have a few observations

 

9.2.1.6 default install, join Win 2008R2 domain.  Create Dataset and then share – all default values

·         CIFS service - local master is default checked – Docs advise against this in AD mode

·         CIFS service - Time server for domain – Docs advise against this in AD mode

·         FILE access default is to enable everyone to have read access to files – convenient yes, secure no!

·         An unusual  bug (can’t find documented) in 9.2.1.5 which causes some files to acquire a deny rule for owner (this was post a full permissions blitz from gui and re-build) is not prevalent – this is causing significant issues**

·         Inheritance permission issue appears resolved (#4961)

·         Bug #4962 is present/repeatable

 

**

# file: spider.sav

# owner: route

# group: domain admins

                owner <at> :r-x-----------:------:deny

                group:jonathon:rwxpDdaARWcCo-:------:allow

                group:route:rwxpDdaARWcCo-:------:allow

                owner <at> :-w-p--aARWcCos:------:allow

                group <at> :rwxp--a-R-c--s:------:allow

                everyone <at> :-wxp--a-R-c--s:------:allow

 

 

Probably like many people I have had lots of issues in 9.2.1.x versions with CIFS shared in my attempt to fix I somehow have managed to set all files to readonly (probably a chmod error) – not sure if this is known output but took me a while to find/fix. 

 

Is there a proposed approach to re-set CIFS permissions post-upgrade to 9.2.1.6 to fix the myriad of issues?

 

 

Regards,

 

Jon

 

 

 

 

Jonathon Royle

Director and Principal Consultant

RoyleMinns Consulting Ltd

 

Tel: +44 (0) 7793 586 132

 

Registered Office: The Gatehouse, Wick Drive, New Milton, Hampshire, BH25 6SJ. RoyleMinns Consulting Ltd Company Registration Number 08494073 (England and Wales)  VAT No 170 1024 63

© 2013 All rights reserved. This message (including any attachments) is confidential and may be legally privileged. If you are not the intended recipient, you should not disclose, copy or use any part of it - please delete all copies immediately and notify RoyleMinns Consulting on 07793 586132.

 

 

<div>
<div class="WordSection1">
<p class="MsoNormal"><span>Further update on the read-only andy deny issue on 9.2.1.5.&nbsp; This does not relate to use of chmod, and pleasingly is
not prevalent in 9.2.1.6 &ndash; not sure if intentional fix or not.&nbsp; Issue for 9.2.1.6 is how best to unwind the permissions errors.<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>In 9.2.1.5 <p></p></span></p>
<p class="MsoNormal"><span>Create new file<p></p></span></p>
<p class="MsoNormal"><span># file: test.txt<p></p></span></p>
<p class="MsoNormal"><span># owner: jonathon<p></p></span></p>
<p class="MsoNormal"><span># group: domain admins<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; group:jonathon:rwxpDdaARWcCo-:------:allow<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; group:route:rwxpDdaARWcCo-:------:allow<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; owner <at> :rw-p--aARWcCos:------:allow<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; group <at> :rw-p--a-R-c--s:------:allow<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; everyone <at> :rw-p--a-R-c--s:------:allow<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>Hmm this is not correct permissions to inherit but we know of this bug.&nbsp; I need to edit as I don&rsquo;t want everyone to be able to read files by default.<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>Reset permissions (via windows 7 client) to remove everyone read and just set to traverse folder<p></p></span></p>
<p class="MsoNormal"><span># file: test.txt<p></p></span></p>
<p class="MsoNormal"><span># owner: jonathon<p></p></span></p>
<p class="MsoNormal"><span># group: domain admins<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; group:jonathon:rw-p--aARWcCo-:------:allow<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; group <at> :rw-p--a-R-c---:------:allow<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; everyone <at> :--x-----------:------:allow<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; group:jonathon:rwxpDdaARWcCo-:------:allow<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; group:route:rwxpDdaARWcCo-:------:allow<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>The file is now set read-only and there are unexpected permission changes!&nbsp; Removed read only flag<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span># file: test.txt<p></p></span></p>
<p class="MsoNormal"><span># owner: jonathon<p></p></span></p>
<p class="MsoNormal"><span># group: domain admins<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; owner <at> :r-x-----------:------:deny<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; group:jonathon:rw-p--aARWcCo-:------:allow<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; group:jonathon:rwxpDdaARWcCo-:------:allow<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; group:route:rwxpDdaARWcCo-:------:allow<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; owner <at> :-w-p--aARWcCos:------:allow<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; group <at> :rwxp--a-R-c--s:------:allow<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; everyone <at> :-wxp--a-R-c--s:------:allow<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>Same actions on 9.2.1.6<p></p></span></p>
<p class="MsoNormal"><span>Original, set read-only, remove read-only.&nbsp; Permission don&rsquo;t change<p></p></span></p>
<p class="MsoNormal"><span># file: test.txt<p></p></span></p>
<p class="MsoNormal"><span># owner: ROYLEMINNS\jonathon<p></p></span></p>
<p class="MsoNormal"><span># group: ROYLEMINNS\domain admins<p></p></span></p>
<p class="MsoNormal"><span>group:ROYLEMINNS\jonathon:rwxpDdaARWcCo-:------:allow<p></p></span></p>
<p class="MsoNormal"><span>group:ROYLEMINNS\route:rwxpDdaARWcCo-:------:allow<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; group <at> :rwxpDdaARWcCo-:------:allow<p></p></span></p>
<p class="MsoNormal"><span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; everyone <at> :--x-----------:------:allow<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>Jon<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-US">From:</span><span lang="EN-US"> Jonathon Royle
<br>Sent: 26 May 2014 22:43<br>To: 'freenas-testing@...'<br>Subject: Testing of FreeNAS-9.2.1.6-BETA-5429442-x64<p></p></span></p>
</div>
</div>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Hi,<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">I have been testing CIFS on above release and have a few observations<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">9.2.1.6 default install, join Win 2008R2 domain.&nbsp; Create Dataset and then share &ndash; all default values<p></p></p>
<p class="MsoListParagraph"><span><span>&middot;<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span>CIFS service - local master is default checked &ndash; Docs advise against this in AD mode<p></p></p>
<p class="MsoListParagraph"><span><span>&middot;<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span>CIFS service - Time server for domain &ndash; Docs advise against this in AD mode<p></p></p>
<p class="MsoListParagraph"><span><span>&middot;<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span>FILE access default is to enable everyone to have read access to files &ndash; convenient yes, secure no!<p></p></p>
<p class="MsoListParagraph"><span><span>&middot;<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span>An unusual&nbsp; bug (can&rsquo;t find documented) in 9.2.1.5 which causes some files to acquire a deny rule for owner (this was post a full permissions blitz from gui and re-build) is not prevalent &ndash; this is causing significant issues**≤p></p></p>
<p class="MsoListParagraph"><span><span>&middot;<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span>Inheritance permission issue appears resolved (#4961)<p></p></p>
<p class="MsoListParagraph"><span><span>&middot;<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span>Bug #4962 is present/repeatable<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">**≤p></p></p>
<p class="MsoNormal"># file: spider.sav<p></p></p>
<p class="MsoNormal"># owner: route<p></p></p>
<p class="MsoNormal"># group: domain admins<p></p></p>
<p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; owner <at> :r-x-----------:------:deny<p></p></p>
<p class="MsoNormal">&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; group:jonathon:rwxpDdaARWcCo-:------:allow<p></p></p>
<p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; group:route:rwxpDdaARWcCo-:------:allow<p></p></p>
<p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; owner <at> :-w-p--aARWcCos:------:allow<p></p></p>
<p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; group <at> :rwxp--a-R-c--s:------:allow<p></p></p>
<p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; everyone <at> :-wxp--a-R-c--s:------:allow<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Probably like many people I have had lots of issues in 9.2.1.x versions with CIFS shared in my attempt to fix I somehow have managed to set all files to readonly (probably a chmod error) &ndash; not sure if this is known output but took me a
 while to find/fix.&nbsp; <p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Is there a proposed approach to re-set CIFS permissions post-upgrade to 9.2.1.6 to fix the myriad of issues?<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Regards,<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Jon<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><span>Jonathon Royle<p></p></span></p>
<p class="MsoNormal"><span>Director and Principal Consultant<p></p></span></p>
<p class="MsoNormal"><span>RoyleMinns Consulting Ltd<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>Tel: +44 (0) 7793 586 132<p></p></span></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p></p></p>
<p class="MsoNormal"><span>Registered Office: The Gatehouse, Wick Drive, New Milton, Hampshire, BH25 6SJ. RoyleMinns Consulting Ltd Company Registration Number 08494073 (England and Wales)&nbsp; VAT No 170 1024 63</span><span><p></p></span></p>
<p class="MsoNormal"><span>&copy; 2013 All rights reserved. This message (including any attachments) is confidential and may be legally privileged. If you are not the intended recipient, you should not disclose, copy or use
 any part of it - please delete all copies immediately and notify RoyleMinns Consulting on 07793 586132.
<p></p></span></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
</div>
Jordan Hubbard | 15 May 08:42 2014

Follow-up to yesterday's request for 9.2.1.6-BETA testing

Hi folks,

Just to follow-up, there are also a couple of additional resources people can use to see what’s been fixed
in 9.2.1.6-BETA.  First, there’s the list of bugs already closed between 9.2.1.5 and 9.2.1.6-BETA:
	https://bugs.freenas.org/projects/freenas/issues?query_id=78
If you have experienced any of the bugs on that list, verifying that they’re truly fixed is always very
helpful to us!

Second, there’s the list of bugs that still need to be fixed before 9.2.1.6-RELEASE goes out:
	https://bugs.freenas.org/projects/freenas/issues?query_id=59

If you run into a bug in 9.2.1.6-BETA that you feel to be significant (or, even more importantly, a
show-stopper) please be sure to report it, also citing the date of the release you’re running (e.g.
9.2.1.6-BETA-20140514) so we can correlate it against our ongoing efforts.

Finally, if you have tested a BETA to any great degree and want to confirm this by sending an email to this
list, or if you have any questions / concerns with things you’ve found during your testing, please by all
means mail them to freenas-testing@...  This is a
very low-traffic list and I’m sure the subscribers would like to see more feedback about releases that
other folks found good / bad / other.

Thanks!

- Jordan

Jordan Hubbard | 14 May 09:10 2014

http://download.freenas.org/nightlies/9.2.1.6/BETA/20140513/

Hi folks,

So, the first “blessed” nightly for testing (though most of them have been pretty good) is the 20140513
build (build hash: 4014d52).  We still don’t have an official test plan ready for everyone yet (it’s
hard work and still in progress), but those of you who wish to simply do ad-hoc testing on it, we’d really
appreciate your impressions and opinions!

As folks can see from the MANIFEST file, the git repos/hashes which correspond to this build are:

git@...:/git/repos/freenas-build/freenas.git 4014d52023f395c7925711a46a51449e6b36d21a
git <at> gitserver:/git/repos/freenas-build/trueos.git 93134bf3014b8dfa3cdf27d649c55599beeef504
git <at> gitserver:/git/repos/freenas-build/ports.git ba29abffb2b9cfa40af44cddcb8ea70432ac12e3

What this translates to on github, for those following along in the external repo, is:

https://github.com/freenas/freenas.git 4014d52023f395c7925711a46a51449e6b36d21a
https://github.com/trueos/trueos.git 93134bf3014b8dfa3cdf27d649c55599beeef504
https://github.com/freenas/ports.git ba29abffb2b9cfa40af44cddcb8ea70432ac12e3

Fairly straight-forward mapping!

Now, for those of you who don’t really speak code or git log, don’t worry - that’s not a prerequisite
for membership / participation in this list!  It’s simply one good way of finding out everything that has
changed between the 9.2.1.5-RELEASE tag and the tip of 9.2.1-BRANCH, which is what the nightly
9.2.1.6-BETA build are rolled from!

The most salient points to pay attention to with this build are:
	- Samba updated to 4.1.7
	- More control over the system dataset (especially now that RRD information can be stored there).  See
Settings->System Dataset screen
	- Support for multithreaded iSCSI
	- Pool import times substantially improved
	- CIFS service disable bug fixed
	- Various AD/LDAP bugs fixed

Appended is a lightly formatted (and edited for length and content) list of git log commit messages
cross-referenced to tickets addressed.  Thanks for your testing!

    Ability to rename warden templates added
    Groups for samba
        - use groupmap for classic mode
	- add group to domain for domain controller mode
	- import users in domain mode
	    Ticket: #4771
	    Ticket: #4181

    Only save rrds to tar file when not using the rrd dataset
    Catch up reporting module with rrd dataset
        Ticket:	#4698

    Nuke the previous system dataset when migrating

    Don't crash if netmask is not configured correctly
        Ticket: #4265

    If create isn't checked, don't create the directory
        Ticket: #4958

    The system dataset is all grown up now and has moved into it's own house

    Delete plugins if on volume or dataset that is being destroyed
        Ticket: #4879

    Custom interface status for LACP LAGG
        Ticket:	#4855

    Handle case of not available CAP in zpool list
        Ticket:	#4968

    Use simple text input for FTP passive ports
        Ticket:	#4956

    Only move the rrd directory if it's archived

    Use system dataset for rrd graphics
        Ticket: #4634

    Use -m 2 for istgt in case multithread is enabled
        Ticket:	#4935

    Add a GUI field to enable istgt in multithreaded mode
    Defaults to off.
        Ticket:	#4935

    Fix sync_disk to get the enabled disk first
        Ticket:	#4430

    Add FREENAS:STATE to snapshot info in freenas-debug output.
    This can be useful in diagnosing snapshot replication problems.
        Ticket: #4809

    Nuke freenas and freenas.local from /etc/hosts
        - This is causing issues with AD joining domains... gethostbyname() is
    	  returning names from these 127.0.0.1 entries and setting the wrong
	  servicePrincipalName.

    Set the From address according to what is in Settings -> email
        Ticket: #4566

    Remove "delete_child" from default acl for everyone
        Ticket: #4910

    Fix the plugin update button problem
        Ticket: #4590

    Remove trailing slash
        Ticket: #4669

    Enable the virtualbox networking.
        Ticket: #4814

    Allow re-configuration of a samba4 domain
        Ticket: #4595

    Yet another acl setting program, much faster than python version.

    fix jails shutdown sequence
        Ticket: #4851

    Remaining deprecated usage of xml nodes
        Ticket:	#4869

    Deprecated test of xml element
        Ticket:	#4868

    Update django to 1.6.4

    Add istgt_args to istgt rc script
        Ticket:	#4935
        Ticket:	#4935

    Update aria2 port
        Ticket: #4348

    Hookup with pam
        Ticket: #4628


Gmane