Philip Robar | 5 Dec 01:35 2014
Picon

Inconsistent GUI reporting of used/free space

I'm running: "FreeNAS 9.3 2014-12-03 01:41:59 GM" nightly.

I have a 1.1 TB zpool with one file system dataset in it:

    space2/backups

which had ~900GB of data in the backups dataset composed of 2 Apple sparse images used for Time Machine backups. space2 had no user data of its own. backups had one snapshot which I used to zfs send/receive it to a different pool. (The dataset was about 450 MB in the copy.) After destroying backups' snapshot and dataset via the GUI the pool still showed roughly the same amount of space being used/free as when the backups dataset still existed. (Note: space2 has never been snapshotted.)

I then tried to destroy the space2 file system dataset and it wouldn't go away. (Should I even be able to do that?) Each time I tried the GUI indicated used space would go down and the free space increased. This is what the GUI showed after two attempts:

                       Used        Available
    space2        355 GiB    800 GiB
        space2    302 GiB    817 GiB

When I choose to destroy the entire pool the "Detach Volume" dialog box said, "You have 821 MiB of used space within this volume."

I canceled the destruction of the pool, switched to another part of the GUI and came back to "Storage - Volumes" and now I see:

                        Used        Available
    space2        821 GiB    1.1 TiB
        space2    818 GiB    1.1 TiB

On the other hand du(1) and df(1) show:

    [root <at> server /mnt/space2] # df -h .
    Filesystem    Size    Used   Avail Capacity  Mounted on
    space2        1.1T    730M    1.1T     0%    /mnt/space2

    [root <at> server /mnt/space2] # du -sh /mnt/space2
    730M    /mnt/space2

Here's a similar situation with non-sparse data:

    space3/Media

Before deleting Media:

                          Used        Available
    space3          444 GB    15 GB
        space3      444 GB    1.5 GB
            Media    444 GB    1.5 GB

After deleting Media (and rebooting):

                        Used        Available
    space3        444 GB    16 GB
        space3    413 GB    32 GB

But, when I choose to destroy the space3 pool: "You have 6.8 MiB of used space within this volume."

    [root <at> server ~]# cd /mnt/space3                                       
    [root <at> server /mnt/space3] # df -h .
    Filesystem    Size    Used   Avail Capacity  Mounted on                 
    space3        445G    188k    445G     0%    /mnt/space3
                     
    [root <at> server /mnt/space3] # du -sh /mnt/space3
    5.0k    /mnt/space3
                                  
It certainly seems like the GUI is not calculating space statics correctly and is not even self consistent.

Phil


<div><div dir="ltr">
<div>I'm running: "FreeNAS 9.3 2014-12-03 01:41:59 GM" nightly.</div>
<div><br></div>I have a 1.1 TB zpool with one file system dataset in it:<div><br></div>
<div>&nbsp; &nbsp; space2/backups</div>
<div><br></div>
<div>which had ~900GB of data in the&nbsp;backups&nbsp;dataset composed of 2 Apple sparse images used for Time Machine backups.&nbsp;space2 had no user&nbsp;data of its own.&nbsp;backups&nbsp;had one snapshot which I used to zfs send/receive it to a different pool. (The dataset was about 450 MB in the&nbsp;copy.) After destroying&nbsp;backups'&nbsp;snapshot and dataset via the GUI the pool still showed roughly the same amount of space being used/free&nbsp;as when the&nbsp;backups&nbsp;dataset still existed. (Note: space2 has never been snapshotted.)</div>
<div><br></div>
<div>I then tried to destroy the space2 file system dataset and it wouldn't go away. (Should I even be able to do that?) Each time I tried the GUI indicated used space would go down and the free space increased. This is what the GUI showed after two attempts:</div>
<div><br></div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Used &nbsp; &nbsp; &nbsp; &nbsp;Available<br>&nbsp; &nbsp; space2 &nbsp; &nbsp; &nbsp; &nbsp;355 GiB &nbsp; &nbsp;800 GiB<br>&nbsp; &nbsp; &nbsp; &nbsp; space2 &nbsp; &nbsp;302 GiB &nbsp; &nbsp;817 GiB<div>
<br><div>When I choose to destroy the entire pool the "Detach Volume" dialog box said, "You have 821 MiB of used space within this volume."</div>
<div><br></div>
<div>I canceled the destruction of the pool, switched to another part of the GUI and came back to "Storage - Volumes" and now I see:</div>
<div><br></div>
<div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Used &nbsp; &nbsp; &nbsp; &nbsp;Available</div>
<div>&nbsp; &nbsp; space2 &nbsp; &nbsp; &nbsp; &nbsp;821 GiB &nbsp; &nbsp;1.1 TiB</div>
<div>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp;space2&nbsp; &nbsp; 818 GiB &nbsp; &nbsp;1.1 TiB</div>
</div>
<div><br></div>
<div>On the other hand du(1) and df(1) show:</div>
<div><br></div>
<blockquote></blockquote>&nbsp; &nbsp; [root <at> server /mnt/space2] # df -h .<br><blockquote></blockquote>&nbsp; &nbsp; Filesystem &nbsp; &nbsp;Size &nbsp; &nbsp;Used &nbsp; Avail Capacity &nbsp;Mounted on<br><blockquote></blockquote>&nbsp; &nbsp; space2 &nbsp; &nbsp; &nbsp; &nbsp;1.1T &nbsp; &nbsp;730M &nbsp; &nbsp;1.1T &nbsp; &nbsp; 0% &nbsp; &nbsp;/mnt/space2<br><br>&nbsp; &nbsp; [root <at> server /mnt/space2] # du -sh /mnt/space2<br><div>&nbsp; &nbsp; 730M &nbsp; &nbsp;/mnt/space2</div>
<div><br></div>
<div>Here's a similar situation with non-sparse data:</div>
<div><br></div>&nbsp; &nbsp; space3/Media<br><blockquote><div><br></div></blockquote>Before deleting Media:<br><div><br></div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Used &nbsp; &nbsp; &nbsp; &nbsp;Available</div>&nbsp; &nbsp; space3 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;444 GB &nbsp; &nbsp;15 GB<br><div><div>&nbsp; &nbsp; &nbsp; &nbsp; space3 &nbsp; &nbsp; &nbsp;444 GB &nbsp; &nbsp;1.5 GB</div></div>
<div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Media &nbsp; &nbsp;444 GB &nbsp; &nbsp;1.5 GB</div></div>
<br>After deleting Media (and rebooting):</div>
<div><br></div>
<div>
<div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Used &nbsp; &nbsp; &nbsp; &nbsp;Available</div>&nbsp; &nbsp; space3 &nbsp; &nbsp; &nbsp; &nbsp;444 GB &nbsp; &nbsp;16 GB</div>
<div>
<div><div>&nbsp; &nbsp; &nbsp; &nbsp; space3 &nbsp; &nbsp;413 GB &nbsp; &nbsp;32 GB</div></div>
<div><br></div>
<div>But, when I choose to destroy the space3 pool:&nbsp;"You have 6.8 MiB of used space within this volume."</div>
<div><br></div>&nbsp; &nbsp; [root <at> server ~]# cd /mnt/space3 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;<br>&nbsp; &nbsp; [root <at> server /mnt/space3] # df -h .<br>&nbsp; &nbsp; Filesystem &nbsp; &nbsp;Size &nbsp; &nbsp;Used &nbsp; Avail Capacity &nbsp;Mounted on &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;<br>&nbsp; &nbsp; space3 &nbsp; &nbsp; &nbsp; &nbsp;445G &nbsp; &nbsp;188k &nbsp; &nbsp;445G &nbsp; &nbsp; 0% &nbsp; &nbsp;/mnt/space3</div>
<div>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;<br>&nbsp; &nbsp; [root <at> server /mnt/space3] # du -sh /mnt/space3<br>&nbsp; &nbsp; 5.0k &nbsp; &nbsp;/mnt/space3<br>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;<div>It certainly seems like the GUI is not calculating space statics correctly and is not even self consistent.</div>
<div><br></div>
<div>Phil</div>
<div><br></div>
<div><br></div>
</div>
</div></div>
Ulf Panten | 12 Nov 22:42 2014
Picon

Update problem 9.2.1.8 -> 9.3 BETA

Hello,

I tried to upgrade my freenas box from 9.2.1.8 to 9.3 BETA.

Unfortunately, it doesn't find the encrypted volume anymore. If I try to import it, it asks for the
encryption key, which I didn't save. Is there any chance to recover the data on this volume?

I didn't see any instructions to save it before updating in the readme either.

--

-- 
Regards,
  Ulf Panten
Jordan Hubbard | 5 Oct 17:00 2014

Re: SMB is broken in recent FreeNAS 9.3 M4 builds

Thanks for reporting this, Philip!  A fix has been checked in and will be in today's build.

- Jordan 

Sent from my iPad

> On Oct 4, 2014, at 23:32, Philip Robar <philip.robar@...> wrote:
> 
> Starting with build FreeNAS-9.3-M4-4bae40c-x64 SMB sharing has stopped working on my home LAN for both
Windows 8.1 and OS X 10.10 RC1. If I downgrade to build FreeNAS-9.3-M4-4989948-x64 the problem goes away.
The issue seems to center around this error:
> 
> Oct 5 00:31:28 server smbd[3574]: [2014/10/05 00:31:28.234444, 0] ../lib/util/modules.c:48(load_module)
> Oct 5 00:31:28 server smbd[3574]: Error loading module
'/usr/local/lib/shared-modules/vfs/aio_pthread.so': Cannot open "/usr/local/lib/shared-modules/vfs/aio_pthread.so"
> Oct 5 00:31:28 server smbd[3574]: [2014/10/05 00:31:28.234569, 0] ../source3/smbd/vfs.c:184(vfs_init_custom)
> Oct 5 00:31:28 server smbd[3574]: error probing vfs module 'aio_pthread': NT_STATUS_UNSUCCESSFUL
> Oct 5 00:31:28 server smbd[3574]: [2014/10/05 00:31:28.234758, 0]
../source3/smbd/vfs.c:349(smbd_vfs_init) Oct 5 00:31:28 server smbd[3574]: smbd_vfs_init:
vfs_init_custom failed for aio_pthread
> Oct 5 00:31:28 server smbd[3574]: [2014/10/05 00:31:28.234830, 0]
../source3/smbd/service.c:640(make_connection_snum) Oct 5 00:31:28 server smbd[3574]: vfs_init
failed for service Media1
> 
> Is this a known problem?
> 
> 
> Phil
> 
> _______________________________________________
> FreeNAS-testing mailing list
> FreeNAS-testing@...
> http://lists.freenas.org/mailman/listinfo/freenas-testing
Philip Robar | 5 Oct 08:32 2014
Picon

SMB is broken in recent FreeNAS 9.3 M4 builds

Starting with build FreeNAS-9.3-M4-4bae40c-x64 SMB sharing has stopped working on my home LAN for both Windows 8.1 and OS X 10.10 RC1. If I downgrade to build FreeNAS-9.3-M4-4989948-x64 the problem goes away. The issue seems to center around this error:

Oct 5 00:31:28 server smbd[3574]: [2014/10/05 00:31:28.234444, 0] ../lib/util/modules.c:48(load_module)
Oct 5 00:31:28 server smbd[3574]: Error loading module '/usr/local/lib/shared-modules/vfs/aio_pthread.so': Cannot open "/usr/local/lib/shared-modules/vfs/aio_pthread.so"
Oct 5 00:31:28 server smbd[3574]: [2014/10/05 00:31:28.234569, 0] ../source3/smbd/vfs.c:184(vfs_init_custom)
Oct 5 00:31:28 server smbd[3574]: error probing vfs module 'aio_pthread': NT_STATUS_UNSUCCESSFUL
Oct 5 00:31:28 server smbd[3574]: [2014/10/05 00:31:28.234758, 0] ../source3/smbd/vfs.c:349(smbd_vfs_init) Oct 5 00:31:28 server smbd[3574]: smbd_vfs_init: vfs_init_custom failed for aio_pthread
Oct 5 00:31:28 server smbd[3574]: [2014/10/05 00:31:28.234830, 0] ../source3/smbd/service.c:640(make_connection_snum) Oct 5 00:31:28 server smbd[3574]: vfs_init failed for service Media1

Is this a known problem?


Phil

<div><div dir="ltr">Starting with build FreeNAS-9.3-M4-4bae40c-x64 SMB sharing has stopped working on my home LAN for both Windows 8.1 and OS X 10.10 RC1. If I downgrade to build FreeNAS-9.3-M4-4989948-x64 the problem goes away. The issue seems to center around this error:<br><br>Oct 5 00:31:28 server smbd[3574]: [2014/10/05 00:31:28.234444, 0] ../lib/util/modules.c:48(load_module)<br>Oct 5 00:31:28 server smbd[3574]: Error loading module '/usr/local/lib/shared-modules/vfs/aio_pthread.so': Cannot open "/usr/local/lib/shared-modules/vfs/aio_pthread.so"<br>Oct 5 00:31:28 server smbd[3574]: [2014/10/05 00:31:28.234569, 0] ../source3/smbd/vfs.c:184(vfs_init_custom)<br>Oct 5 00:31:28 server smbd[3574]: error probing vfs module 'aio_pthread': NT_STATUS_UNSUCCESSFUL<br>Oct 5 00:31:28 server smbd[3574]: [2014/10/05 00:31:28.234758, 0] ../source3/smbd/vfs.c:349(smbd_vfs_init) Oct 5 00:31:28 server smbd[3574]: smbd_vfs_init: vfs_init_custom failed for aio_pthread<br>Oct 5 00:31:28 server smbd[3574]: [2014/10/05 00:31:28.234830, 0] ../source3/smbd/service.c:640(make_connection_snum) Oct 5 00:31:28 server smbd[3574]: vfs_init failed for service Media1<br><br>Is this a known problem?<br><br><br>Phil<div><br></div>
</div></div>
Sean Fagan | 18 Sep 22:38 2014

Re: 9.3 M4 updating is sloooooow

>> 
> From: Philip Robar <philip.robar@...>
> To: freenas-testing@...
> Subject: [FreeNAS-testing] 9.3 M4 updating is sloooooow
> 
> I recently manually updated from the latest or next to latest 9.3 M3 to 9.3 M4 32a2e11 9/16 nightly. Even
taking into account that I'm now using a very slow 4GB flash drive to accommodate the increased size of 9.3
it seemed like it took a very long time. Since I wasn't expecting this big increase in time I wasn't
specifically keeping track, but I think it took an hour or more to finish.
> 
> Now I'm trying to update to 9.3 M4 eae2f5f 9/17 nightly and the update has been running for 2 or 3 hours. In
both cases the Manual Update progress window stops showing any updates after it gets to this point: "Step 2
of 2" "(2/3) Extracting update" "33%". The successful update never showed anymore progress, it just
suddenly rebooted.
> 
> Is there anything that I can look for in a log file or something like top to have an idea if the update is
actually making progress?
> 
> At what point should I just give up?
> 
> Are upgrades now going to take much longer then they have in the past?

The Manual Update is doing this:

1) Download the tarball containing everything
2) Store it on the specified dataset
3) Extract it.
4) Extract the package files.
5) Creates a new boot environment.
6) Install.
6a) For each package:
	freenas-install sees that it is doing an update, and it is not a delta package,
	so it first removes all of the files (and possibly directories) owned by the package
	in the package database -- from the filesystem and from the package database.
	It runs any scripts this process.  Then it installs each file and directory, into the
	filesystem and database.

A slow thumb drive will in fact be very slow as a result.  (I went and got a PNY USB 3
thumb drive, and enabled xhci via a loader configuration.  Things go much faster
with that.  But that particular thumb drive requires a kernel change, which just got
checked in, so it'll be a day or two.)

You can see what it's doing by "ps auxwww | grep freenas; you should see a python
freenas-install program running.  You can truss or ktrace that if you want to check its
progress.

Using the recommended update will be faster in general, since it not all of the packages
change all the time, and the delta packages, if available, are much smaller.

> Also since switching to 9.3 M3 I've noticed that my system hangs during a reboot after the boot USB2 flash
device is detached--at least that's the last thing printed on the screen. Is this a known problem?

Yes, it has to do with FreeBSD's kernel not releasing the device.  I think it's weird that
the post-database-reboot doesn't hang.

Sean.

Philip Robar | 18 Sep 06:37 2014
Picon

9.3 M4 updating is sloooooow

I recently manually updated from the latest or next to latest 9.3 M3 to 9.3 M4 32a2e11 9/16 nightly. Even taking into account that I'm now using a very slow 4GB flash drive to accommodate the increased size of 9.3 it seemed like it took a very long time. Since I wasn't expecting this big increase in time I wasn't specifically keeping track, but I think it took an hour or more to finish.

Now I'm trying to update to 9.3 M4 eae2f5f 9/17 nightly and the update has been running for 2 or 3 hours. In both cases the Manual Update progress window stops showing any updates after it gets to this point: "Step 2 of 2" "(2/3) Extracting update" "33%". The successful update never showed anymore progress, it just suddenly rebooted.

Is there anything that I can look for in a log file or something like top to have an idea if the update is actually making progress?

At what point should I just give up?

Are upgrades now going to take much longer then they have in the past?

Also since switching to 9.3 M3 I've noticed that my system hangs during a reboot after the boot USB2 flash device is detached--at least that's the last thing printed on the screen. Is this a known problem?


Phil

Supermicro X7DCA-L
Intel Xeon 5420L x 2 [8 cores total] (Geekbench: single core ~= Sempron 140)
8 GB RAM

<div><div dir="ltr">I recently manually updated from the latest or next to latest 9.3 M3 to 9.3 M4 32a2e11 9/16 nightly. Even taking into account that I'm now using a very slow 4GB flash drive to accommodate the increased size of 9.3 it seemed like it took a very long time. Since I wasn't expecting this big increase in time I wasn't specifically keeping track, but I think it took an hour or more to finish.<div><br></div>
<div>Now I'm trying to update to 9.3 M4 eae2f5f 9/17 nightly and the update has been running for 2 or 3 hours. In both cases the Manual Update progress window stops showing any updates after it gets to this point: "Step 2 of 2" "(2/3) Extracting update" "33%". The successful update never showed anymore progress, it just suddenly rebooted.</div>
<div><br></div>
<div>Is there anything that I can look for in a log file or something like top to have an idea if the update is actually making progress?</div>
<div><br></div>
<div>At what point should I just give up?</div>
<div><br></div>
<div>Are upgrades now going to take much longer then they have in the past?</div>
<div><br></div>
<div>Also since switching to 9.3 M3 I've noticed that my system hangs during a reboot after the boot USB2 flash device is detached--at least that's the last thing printed on the screen. Is this a known problem?</div>
<div><br></div>
<div><br></div>
<div>Phil</div>
<div><br></div>
<div>Supermicro X7DCA-L</div>
<div>Intel Xeon 5420L x 2 [8 cores total] (Geekbench: single core ~= Sempron 140)</div>
<div>8 GB RAM</div>
<div><br></div>
</div></div>
Philip Robar | 17 Sep 02:08 2014
Picon

Updating from FreeNAS 9.3 M3 to M4?

I tried to use the new Check For Updates option, but it didn't work. It detects the updates, but then fails in a couple of different ways if I proceed. Is this ready for testing and bug reports?

Phil

<div><div dir="ltr">I tried to use the new Check For Updates&nbsp;option, but it didn't work. It detects the updates, but then fails in a couple of different ways if I proceed. Is this ready for testing and bug reports?<div><br></div>
<div>Phil</div>
<div><br></div>
</div></div>
Turbo Fredriksson | 23 Aug 14:55 2014

FreeNAS-10.0.0-ALPHA-d2d986a-x64.img can't seem to mount the root fs

... it just say "waiting for ufs:/dev/ufs/FreeNAS0s1" or something like that and eventually
gives me a prompt where I should enter the root fs. But it doesn't look like my USB memstick
is recognized/loaded....

I _think_ (I'm a Linux tech and not very good at *BSD yet) I can see my two SATA SSD disks (one
is an [very] old Linux installation that I don't use any more and the other is (was) used for 
ZFS cache) and the SATA platter disk being recognized by the kernel.

I have one USB memstick to boot my Linux machine (loads the kernel and initrd from usb, but root
fs on the SATA platter disk) and the other USB memstick is the FreeNAS10 USB image... None of
which is seen/recognized/loaded that I can see (it scrolls by quite fast, but I'm quite used to
that from Linux as well :).

I'm waiting for a 9.3-ALPHA image to finish writing to the FreeNAS stick to try, but I just wanted
someone to know of possible problems with the v10 image...
--
Michael Jackson is not going to buried or cremated
but recycled into shopping bags so he can remain white,
plastic and dangerous for kids to play with.

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


Gmane