FreeNAS 8.2.0-BETA3 is now available

Discussion in 'Archived Announcements' started by jpaetzel, Apr 19, 2012.

  1. Offline

    jpaetzel FreeNAS Core Team

    Member Since:
    May 27, 2011
    Messages:
    194
    Message Count:
    194
    Likes Received:
    28
    Trophy Points:
    28
    Occupation:
    IT
    Location:
    Gilroy, CA
    Home page:
    jpaetzel, Apr 19, 2012

    I've just completed uploading FreeNAS 8.2.0-BETA3.

    https://sourceforge.net/projects/freenas/files/FreeNAS-8.2.0/BETA3/

    Upgrades from BETA2 work, but most likely any plugin stuff that is working in BETA2 will stop working

    You'll want to use the plugins in the BETA3 directory with this beta, don't mix and match.

    Notable highlights are a complete refactor of plugins, iSCSI target reload, and the samba security fix.

    Release Notes for FreeNAS 8.2.0-BETA3

    *** IMPORTANT ***

    - The image size increased in 8.0.1-BETA3. The new size requires a 2 GB
    storage device. The GUI upgrade can be used to upgrade a system from
    BETA3, BETA4, or RC1 but upgrades from earlier releases can only be
    done from the CD. The other option is to save the config, reinstall
    the new version, then restore the config.
    - FreeBSD can be really touchy with hardware. Please be sure to update
    your BIOS/BMC firmware when upgrading / installing FreeNAS if you run
    into OS hang issues. There have been cases identified where a BIOS
    upgrade has fixed driver hangs, and/or other issues with FreeNAS; one
    such example was with an Intel 82578DC motherboard, as noted in the
    FreeNAS 8 forum thread titled "8.0.3-RELEASE coming soon..":
    http://bit.ly/rq78Q3 , post # 70-88. Again, please only do this if you
    experience booting / runtime issues, as some vendors don't test
    FreeBSD interoperability as much as others between major firmware
    releases.
    - Previous builds were branded as i386/amd64 (32-bit and 64-bit
    respectively). 8.0.3-RC1+ rebranded the architectures as x86 and x64,
    respectively.
    - 8.0.1 and 8.0.2 images advertised CIFS shares to Macs by default but
    8.0.3 and later images don't advertise CIFS shares by default. If you
    want to advertise CIFS shares in 8.0.3 and later, be sure to turn on
    "Zeroconf" support in the CIFS global settings.
    - Builds prior to 8.0.3-RELEASE with 'CIFS' didn't actually have AIO
    (asynchronous I/O) enabled. So, if you experience performance
    degradation after upgrading from prior versions of FreeNAS to
    8.0.3-RELEASE or newer, turn off AIO or tune the AIO size from '1' to
    something more reasonable (the new default in 8.0.3-RELEASE-p1 is 4096
    or 4kB).

    Changes in the 8.2 branch versus 8.0.x


    Overview
    ========================

    The 8.2 branch of FreeNAS introduces many functional changes when
    compared with the 8.0.x releases.

    ZFS can be manipulated from the CLI, and changes for supported items
    tracked by FreeNAS will be reflected in the GUI. zvols, datasets, and
    entire volumes can be created, destroyed, or manipulated on the CLI and
    will be propagated to the GUI.

    The GUI now supports active-passive multipath capable hardware, which
    targets mainly SAS drives on dual expander backplanes. Any multipath
    capable devices that are detected will be placed in multipath units
    which are then exposed to the GUI, and the parent devices will be
    hidden.

    Plugins are now available. Third party modules can be added to FreeNAS
    which will persist across upgrades and can be manipulated and configured
    from the GUI. Documentation on using and creating plugins is available
    at http://doc.freenas.org/index.php/Plugins_Configuration . BitTorrent,
    DLNA/uPNP, and iTunes plugins are available as of this writing.

    The GUI now includes a webshell, which allows you to access a root
    shell from within a web browser.

    The "Create Volume" modal was renamed to "Volume Manager". Extending
    existing pools is more intuitive than it was previously; selecting
    multiple disks for a storage volume is now done via a multiselect
    widget instead of checkboxes to improve ease of use when creating
    volumes.

    ZFS volumes can now have periodic scrub tasks configured for them; the
    default is set to 35 days to be consistent with the OS default.

    An autotuning script is now available -- disabled by default. It sets
    various tunables and sysctls based on system resources and components.
    The predetermined values are exposed through the GUI from the Sysctls
    and Tunables panes.

    A newer web toolkit is used, which behaves better with modal dialogs
    and more intuitively in general when compared with older versions.
    It also has better browser compatibility, including compatibility with
    Android / iOS mobile devices!

    A more responsive service state detection mechanism was added to
    improve FreeNAS interoperability in VM software (VMware, VirtualBox,
    etc).

    Changes since 8.2.0-BETA2:

    Enhancements
    ========================

    GUI
    ------------------------

    1. A major refactoring of the plugin structure has been done.

    iSCSI
    ------------------------

    1. Target reload is now supported for adding and removing (but not changing)
    targets on the fly. The Logical Unit Controller is used for this, reload
    wil not function if the LUC is not enabled.

    CIFS
    ------------------------

    1. Samba has been upgraded to 3.6.4 to address the security issues in 3.6.3

    Bugfixes
    ========================

    GUI
    ------------------------

    1. Fix a javascript error that affected IE8



    Changes since 8.0.4-RELEASE:

    Enhancements
    ========================

    Build
    ------------------------

    1. Refactoring of the build system was done to ease release
    engineering and make FreeNAS software development easier, faster,
    and more deterministic.

    2. Plugin jail generation was integrated into the build system.


    GUI
    ------------------------

    1. The current password box for changing the admin password is hidden
    when there isn't an admin password set.

    2. Adding users allows for placing users into additional groups, as well
    as greater clarity about the primary group the user will be in.

    3. The NTP configuration fields are split in to separate fields instead
    of overloading a single field.

    4. Create Volume is now renamed to Volume manager, and has a different
    widgit for selecting multiple disks, as well as a better GUI for
    extending existing volumes versus adding new volumes.

    5. Create dataset and create zvol are now buttons listed per pool, in
    addition nested datasets can be created as a dataset has an add
    dataset button.

    6. Deleting volumes and datasets properly cascades to shares and
    services; notification is provided if a filesystem is in use and
    the configuration database is guaranteed to be more consistent with
    the system state.

    7. Update the GUI to reflect the fact that the dynamic DNS update period
    is in seconds, not milliseconds.

    8. Add the ability to enable or disable the autotuner to system ->
    settings -> advanced.

    9. Alias IPs are displayed in the interface configuration screen.

    10. ZFS scrubs can be scheduled via the GUI.

    11. The IP address used to connect to the FreeNAS box is displayed in
    the GUI.

    Middleware
    ------------------------

    1. Significant refactoring of the middleware was done to support
    various changes made to the GUI.


    OS/Third party
    ------------------------

    1. Add the iSCSI initiator kernel module to the system.


    Plugins
    ------------------------



    AFP
    ------------------------



    CIFS
    ------------------------



    iSCSI
    ------------------------

    1. Use configured IPs on the system as candidates for portal addresses.


    NFS
    ------------------------



    Tools
    ------------------------



    Bugfixes
    ========================

    Build
    ------------------------



    GUI
    ------------------------

    1. Exclude snapshots with existing clones from the pending delete list.
    This fixes an issue where a clone will prevent an existing snapshot
    from being deleted by the autosnapper.

    2. Browser cache can become confused when the same browser is used to
    access multiple versions of FreeNAS. Version specific cache data
    was added to mitigate this issue.


    Middleware
    ------------------------



    OS/Third party
    ------------------------



    Plugins
    ------------------------



    AFP
    ------------------------



    AD/CIFS/LDAP
    ------------------------

    1. Disable directory name caching, which improves performance on BSD.

    2. Remove the ability to set a guest account per share, this is a global
    setting only.

    3. Change the default guest account to nobody.

    4. Add anonymous LDAP bind support.

    iSCSI
    ------------------------

    1. Ensure that a file extent resides in a volume.


    NFS
    ------------------------



    Tools
    ------------------------




    Changes since 8.0.4-RC1:

    Enhancements
    ========================

    GUI
    ------------------------

    1. Rename 'loaders' to 'tunables' to target the FreeBSD concept under
    inspection (kernel tunables) (SF r10235, r10236).

    Bugfixes
    ========================

    OS/Third party
    ------------------------

    1. Remove sane caps for minimum ZFS requirements for lower spec'ed home
    user machines added in 8.0.4-BETA1. A better solution will be devised
    in 8.2.0 with automatic system tuning, similar to legacy's
    zfskerntune (SF r10271).

    CIFS
    ------------------------

    1. Correct guest parameter setting in the GUI as it's a global option,
    not a per-share option (SF r10296).
    2. Allow Guest Only parameter only makes sense when Allow Guest is
    specified (SF r10300).
    3. Validate guest setting prior to accepting POST to ensure that the
    value set for Guest is sane.


    Changes since 8.0.4-BETA2:

    Enhancements
    ========================

    Build
    ------------------------

    1. Remove Full_Install from the compressed disk image name to avoid
    potential confusion when looking at the disk image vs the GUI
    upgrade image (SF r10154).

    Middleware
    ------------------------

    1. Do not restart collectd (reporting backend) when deleting snapshots
    in the GUI (SF r10139).

    Tools
    ------------------------

    1. Add arcstat.py and arc_summary.py tools originally contributed by
    jhell (FreeBSD contributor), ported by jhixson to FreeNAS 8.x.

    Bugfixes
    ========================

    GUI
    ------------------------

    1. Correct window title for snapshot deletion GUI (SF r10138).

    Middleware
    ------------------------

    1. Catch ZFS snapshot errors when snapshots are done via the GUI instead of
    failing silently (SF r10152).
    2. Work around interoperability issues with user / group population in the
    GUI by failing silently in certain cases if AD/LDAP users cannot be
    retrieved (SF r10140).
    3. Fix case where local and remote paths passed to rsync in Rsync tasks
    weren't quoted, so paths with spaces in them would not work (FN 1285).


    Changes since 8.0.4-BETA1:

    Enhancements
    ========================

    OS/Third party
    ------------------------

    1. Update transmission to 2.42 (SF r10093).
    2. Add MegaCLI tool (SF r10072, r10073).
    3. Disable periodic tasks in the base system that would negatively
    impact system performance on NAS boxes with large directory
    structures (SF r10113).

    Bugfixes
    ========================

    Middleware
    ------------------------

    1. Fix handling for 'every day' SMART tasks created in the GUI
    (SF r10088).
    2. Add in several robustness fixes to reduce potential for filesystem
    corruption on root / boot device. In some scenarios this would also
    improve performance when fetching data from the root device as well
    (SF r10095, r10109, r10129).

    CIFS
    ------------------------
    1. Fix vfs objects modules ordering so shadow copy (aka previous
    versions) support functions again (FN 935, FN 1186, FN 1275).
    2. Update samba to 3.6.3 to resolve several bugs (both security and
    non-security related) (SF r10127).

    iSCSI
    ------------------------

    1. Network field from iSCSI initiator could contain multiple IP
    addresses, CIDR addresses, or ANY keyword (SF r10082).
    2. Generate istgt.conf properly if and when multiple initiators were
    specified (SF r10081).


    Changes since 8.0.3-RELEASE-p1:

    Enhancements
    ========================

    Build
    ------------------------
    1. Add .img suffix to simplify mounting full disk image for Windows and
    OSX users (FN # 1236).

    OS/Third party
    ------------------------

    1. Update firefly to 1696_6 for iTunes 10.5.2+ compatibility.
    2. Add in sane caps for minimum ZFS requirements for lower spec'ed home
    user machines.

    AD/CIFS
    ------------------------

    1. Automatically create AD/LDAP user home directories (FN # 1203).
    2. Add 'allow trusted domains' knob in the CIFS global configuration
    (FN # 998).

    iSCSI
    ------------------------

    1. Restrict portal input in the GUI to prevent scenarios where
    incorrect input would prevent iSCSI from starting (FN # 1231).

    Rsync
    ------------------------

    1. Add rsync+SSH functionality (FN # 990).
    2. Add functionality to differentiate rsync pushing from pulling
    (FN # 394).

    Bugfixes
    ========================

    GUI
    ------------------------

    1. Fix disks / partition parsing when importing volumes (FN # 1202).
    2. Restrict users from creating cronjobs / rsync tasks with long
    usernames (FN # 1061).

    Middleware
    ------------------------

    1. Correct smbpasswd parsing when debug level isn't set to minimum
    logging (FN # 1224).

    AD/CIFS
    ------------------------

    1. Escape samba AD/LDAP passwords (FN # 1225).
    2. Ensure guest accounts are disabled if checked (SF r8276).


    Changes since 8.0.3-RELEASE:

    Enhancements
    ------------------------

    OS/Third party
    ========================

    1. Update ataidle from 2.6 to 2.72 based on maintainer's (brucec@FreeBSD)
    recommendation due to interoperabilities with 2.6 and certain chipsets.
    2. Fix the inadyn port so that it works on i386.

    Bugfixes
    ------------------------

    Middleware
    ========================
    1. Fix a regression for DHCP users where /etc/resolv.conf would be nulled
    out if DNS servers weren't specified in the GUI.

    AD/CIFS
    ========================
    1. Disable AIO by default and change the default AIO read / write size to
    4kB. This was done provided feedback and the fact that the build fixes
    actually enabled AIO, whereas prior releases didn't enable it by
    default. This can cause issues with machines that don't have the
    resources to service AIO requests quickly enough, where previously they
    would be able to service requests at near line speeds, whereas after
    they are unable to service requests that quickly.

    NFS:
    ========================
    1. Add in logic to start lockd and mountd when NFS is enabled s.t. FreeNAS
    doesn't need to be manually prodded to start the services, or rebooted
    in order for the services to become effective.

    Changes since 8.0.2-RELEASE:

    Enhancements
    ------------------------

    OS/Third party
    ========================

    1. Use smaller block and frag sizes for /etc and /var .
    2. Import a build tweak to nuke /var/db/pkg to save ~7MB space.
    3. Other build tweaks to remove non-essential features and packages from
    the image.
    4. Disable output to /var/log/console.log in non-debug builds to avoid
    unnecessary duplication in /var/log/messages .
    5. Upgrade ataidle to 2.6.
    6. Upgrade nut / net-snmp to 2.6.2 and 5.7.1, respectively.
    7. Import omnibus build system fixes to fix the fact that the 8.0.3-BETA1
    image was broken due to the environment of the build machine where it
    was produced on. This also fixes other items, such as DDNS because of
    build environment tainting.
    8. Increase the /var md size from 74MB to 160MB s.t. samba will be able
    to service requests copying large sets of files, and the rest of the
    system will be able to play nicely with samba to a certain degree.
    More tuning is required for larger samba userbases.

    GUI
    ========================

    1. Add kernel tunable / sysctl support.

    Middleware
    ========================

    1. Hide Etc/GMT* timezones as they're behavior is counterintuitive and
    conflicts with Windows 7 semantics (see r8707).

    AD/CIFS
    ========================

    1. Bump samba from 3.5.11 to 3.6.1.
    2. Address simple failure cases with getting Kerberos tickets (clock
    skew) and joining AD domains (invalid passwords, bad short domain names,
    etc) so that users could better rectify improperly configured NAS boxes;
    this means that if either of these cases fail, the GUI will now inform
    the user that the 'Active Directory' service is stopped.
    3. Fix cachetool to better prevent potential race condition at boot between
    winbindd and ix-cache.
    4. Add knob for enabling/disabling Zeroconf/Bonjour (avahi) support in the
    GUI. For technical reasons outside of the author's control, this
    feature defaults to off when upgrading FreeNAS. FreeNAS admins
    anticipating that they will have Mac users attempting to connect to CIFS
    shares should enable this feature.

    AFP
    ========================

    1. Bump netatalk to 2.2.1.
    2. Add knob for controlling the maximum number of configurable connections
    (see ticket: 847).
    3. Only advertise services via avahi if they're enabled (see ticket: 852).

    Rsync
    ========================

    - NFSv4 ACL support (see: r8375, r8414).

    Bugfixes
    ------------------------

    OS/Third party
    ========================

    1. Fix NTFS volume imports.

    GUI
    ========================

    1. ZFS volume deletion failed when trying to delete zvol with the name
    'zvol'.
    2. SSH pubkey saving was broken unless you manually add a newline to the
    text box.
    3. Fix traceback when trying to edit user if ssh public key was not
    specified.
    4. Fix the bug in rsync tasks where it would strip the trailing '/' off
    the end of the destination path.
    5. Fix a validation error when editing users / groups in 8.0.2+ where
    if one entered in a path that wasn't valid, the GUI would traceback
    instead of punting the actual validation error.
    6. Fix an issue where if one entered in an invalid path, the GUI would
    traceback instead of providing feedback stating that the directory
    provided was invalid.

    Middleware
    ========================

    1. Rsync task/crontab generation was broken with AD usernames and other
    unsanitized input.
    2. Fix email regressions since 8.0.2-RELEASE-p1 (SMART emails now work
    with more than one recipient, non-SMTP authentication based emails
    work again).
    4. Fix an issue where if one autosnap process was killed uncleanly, more
    autosnap processes could back up and eventually deadlock the system.
    5. Fix an issue where the ZFS scrub cronjobs would execute every 30 days
    instead of a number divisible by 7, so what would generally happen is
    that ZFS scrubs would generally execute in the middle of the week.
    6. Fix setting httpd to listen on an interface which is not the first
    interface.
    7. Add logic to create home directories on demand instead of failing
    'silently' if the path to the directory didn't already exist.
    8. Fix 'detaching' NTFS/UFS volumes so that it unmounts the volume in
    the FreeBSD backend.

    AD/CIFS
    ========================

    1. Change the default workgroup from FREENAS to WORKGROUP as having the same
    name for the workgroup and the hostname is illegal per the SMB/CIFS
    protocol.

    Cosmetic items
    ------------------------

    1. Change "SSH key" in GUI to "SSH Public Key".
    2. Fix GUI trademarks and branding to be more consistent with proper
    branding, similar to what TrueNAS does today.



    Major changes since 8.0.1-RELEASE:

    - The email subsystem was not working correctly in 8.0.1-RELEASE, which
    resulted in the system not being able to send mail, as well as of the
    alerting system in the GUI.

    Changes since 8.0.1-RELEASE:

    - Allow decimal numbers for a dataset quota. (r8728)

    - Fix setting recursive ACLs. (r8270)

    - Start proftpd after ix-ssl to use the correct SSL cert. (r8246)

    - Use wildcards in cron and rsync jobs instead of listing all values. (r8214, r8211)

    - Fix case in iSCSI targets to match the behavior specified by RFC 3722. (r8120)

    Changes since 8.0-RELEASE:

    There's too much to list here, but the high points are:

    - Divorced the volume members in the database from the FreeBSD devices.
    This resolves an issue where FreeBSD can change devices names and the
    GUI doesn't pick up the updates due to the devices names being hard-wired
    in the database.

    - Support exporting ZFS zvols (virtual devices) as device extents via iSCSI.
    8.0 was only able to export physical device nodes or file based extents.

    - The GUI now has an event notification system.

    - The email backend has been refactored.

    - Many many changes in the GUI to help it validate and sanitize inputs that
    are passed to the backend daemons.

    - Added UPS functionality.

    - Added rsync client and server functionality.

    - Added the ability to schedule cron jobs in the GUI.

    - Vastly improved and reworked snapshot replication.

    Errata:

    - CHAP doesn't work with GlobalSAN initiators on OS X.

    - Upgrades from FreeNAS 0.7 aren't supported.

    - The installer doesn't check the size of the install media before attempting
    an install. A 2 GB device is required, but the install will appear to
    complete successfully on smaller devices, only to fail at boot.

    - The installer will let you switch from i386 to amd64 architecture and
    vice-versa, but some files, such as the rrd files used by the statistics
    graphing package are architecture dependent.

    - There are known interoperability issues with FreeNAS and Samba 4.x being
    used as a PDC due to Samba 4.x not conforming to the Microsoft CIFS
    specification and the way LDAP queries are executed on FreeNAS. Please see
    the following support ticket for more details:
    http://support.freenas.org/ticket/1135 .

    Filename:
    FreeNAS-8.2.0-BETA3-x64.GUI_Upgrade.xz
    SHA256 Hash:
    4fb9671652897afb3a0fda3e4cca94ab589575803339a6df68fda961ab9cb824

    Filename:
    FreeNAS-8.2.0-BETA3-x64.img.xz
    SHA256 Hash:
    70e0c196cf5f40c20ebc30e50ebd08006d9acfa550906082918534c1a5eda5c0

    Filename:
    FreeNAS-8.2.0-BETA3-x64.iso
    SHA256 Hash:
    c4e297a7eb848145a5badc673c9645ccf631cf9120d6598d7fc158da2c76e89d

    Filename:
    FreeNAS-8.2.0-BETA3-x86.GUI_Upgrade.xz
    SHA256 Hash:
    7c29463b13032dc53826f570e4c8ace09650d88b1256d6362c5fa4af42ebe101

    Filename:
    FreeNAS-8.2.0-BETA3-x86.img.xz
    SHA256 Hash:
    23c3d02f6f0dd462ea1610926754db30e1bc3f442840e7106b3e14b305ad8155

    Filename:
    FreeNAS-8.2.0-BETA3-x64.iso
    SHA256 Hash:
    c4e297a7eb848145a5badc673c9645ccf631cf9120d6598d7fc158da2c76e89d
  2. Offline

    zygoptera

    Member Since:
    Nov 3, 2011
    Messages:
    4
    Message Count:
    4
    Likes Received:
    0
    Trophy Points:
    0
    zygoptera, Apr 19, 2012

    I understand it as this beta is to (mainly) test that the refactoring did not introduce any bugs. Does this imply we are pretty close to a 8.2-RC ??

    I am dying for the release of the stable 8.2 release...

    edit:To avoid any misunderstanding; I really like FreeNAS and love the work the developers put in - no whining intended...
  3. Offline

    William Grzybowski FreeNAS Guru

    Member Since:
    May 27, 2011
    Messages:
    1,666
    Message Count:
    1,666
    Likes Received:
    23
    Trophy Points:
    38
    Location:
    Curitiba, Brazil
    William Grzybowski, Apr 19, 2012

    There were hundreds of commits between BETA2 and BETA3... I would expect at least a BETA4 before the RC1...
  4. Offline

    zygoptera

    Member Since:
    Nov 3, 2011
    Messages:
    4
    Message Count:
    4
    Likes Received:
    0
    Trophy Points:
    0
    zygoptera, Apr 19, 2012

    Just curious not being a programmer, were can I check these "commits" to have an idea of the work being done between the releases? I don't get were the real development discussions are held.
  5. Offline

    William Grzybowski FreeNAS Guru

    Member Since:
    May 27, 2011
    Messages:
    1,666
    Message Count:
    1,666
    Likes Received:
    23
    Trophy Points:
    38
    Location:
    Curitiba, Brazil
    William Grzybowski, Apr 19, 2012

    Basically http://support.freenas.org, there are mailing lists but are not being really used...
    Feel free to join #freenas in irc.freenode.net as well.
  6. Offline

    warri FreeNAS Guru

    Member Since:
    Jun 6, 2011
    Messages:
    1,068
    Message Count:
    1,068
    Likes Received:
    44
    Trophy Points:
    48
    Location:
    Germany
    warri, Apr 19, 2012

    At https://support.freenas.org you can see all open bug tickets, the developing process and the actual source code including all commits.
  7. Offline

    sirdir

    Member Since:
    Apr 20, 2012
    Messages:
    16
    Message Count:
    16
    Likes Received:
    0
    Trophy Points:
    0
    sirdir, Apr 20, 2012

    BETA3 latest version?

    Hi!

    I wonder why BETA3 is listed as 'latest version' on the main page? I was tempted to install it as 'stable'...
  8. Offline

    jpaetzel FreeNAS Core Team

    Member Since:
    May 27, 2011
    Messages:
    194
    Message Count:
    194
    Likes Received:
    28
    Trophy Points:
    28
    Occupation:
    IT
    Location:
    Gilroy, CA
    Home page:
    jpaetzel, Apr 20, 2012

    There is a commit mailing list you can subscribe to if you want to get an email for each commit, along with the diff of it.

    You can also browse changesets at http://support.freenas.org

    I've notified our web team, I agree that the download links should not be pointing at 8.2.0-BETA3
  9. Offline

    StephenFry FreeNAS Aware

    Member Since:
    Apr 9, 2012
    Messages:
    136
    Message Count:
    136
    Likes Received:
    0
    Trophy Points:
    16
    StephenFry, Apr 20, 2012

    Updated BETA2 from the GUI to BETA3 - no weirdness to report, which is how I like it!

    Thanks guys.
  10. Offline

    StephenFry FreeNAS Aware

    Member Since:
    Apr 9, 2012
    Messages:
    136
    Message Count:
    136
    Likes Received:
    0
    Trophy Points:
    16
    StephenFry, Apr 20, 2012

    Ouch, sadly some weirdness after all:

    The "Advanced Mode" button for CIFS shares doesn't do anything anymore, which means I can't edit my block/allow access by IP address.
  11. Offline

    drinking12many

    Member Since:
    Apr 8, 2012
    Messages:
    7
    Message Count:
    7
    Likes Received:
    0
    Trophy Points:
    1
    drinking12many, Apr 21, 2012

    Any idea what would cause this error while upgrading from BETA2?

    [MiddlewareError: The update failed: Command '['sh', '-x', '/root/update']' returned non-zero exit status 1]

    Here was the last couple lines in the terminal

    Apr 21 13:20:30 freenas notifier[3066]: Executing: /usr/bin/xz -t /var/tmp/firmware/firmware.xz
    Apr 21 13:20:49 freenas middleware[3066]: Popen()ing: /sbin/sha256 -q /var/tmp/firmware/firmware.xz
    Apr 21 13:20:51 freenas updater[3066]: Executing: /usr/bin/xzcat /var/tmp/firmware/firmware.xz | sh -x /root/update



    *edit Got this today think this is just a bug when using more than one ip - WARNING: The following IPs are bind to iSCSI Portal but were not found in the system: 0.0.0.0
  12. Offline

    Mitez

    Member Since:
    Apr 28, 2012
    Messages:
    1
    Message Count:
    1
    Likes Received:
    0
    Trophy Points:
    0
    Mitez, Apr 29, 2012

    Got a problem with the Authentication Model in Services - CIFS enabled the "Anonymous" option. The username and password are the same on client machine

    When signed into Windows 7 it doesn't pop-up with "Windows security" window asking for credentials.

    It looks like the Anonymous and Local user Authentication are similar.

    Is this a bug?
  13. Offline

    William Grzybowski FreeNAS Guru

    Member Since:
    May 27, 2011
    Messages:
    1,666
    Message Count:
    1,666
    Likes Received:
    23
    Trophy Points:
    38
    Location:
    Curitiba, Brazil
    William Grzybowski, Apr 29, 2012

    You are using anonymous option and is not asked for username or password. What is the issue?
  14. Offline

    duckman

    Member Since:
    Jan 24, 2012
    Messages:
    15
    Message Count:
    15
    Likes Received:
    0
    Trophy Points:
    0
    duckman, May 1, 2012

    I don't think you can have a share that is both Anonymous (ie no access restrictions) and also Authenticated (where it will ask who you are).

    I've tried, and it doesn't work. The documentation for samba isn't especially clear on this though...
    I agree it would be nice to have - my plan was Read for anonymous & Write for authenticated. Sadly no.
  15. Offline

    jgreco Resident Grinch

    Member Since:
    May 29, 2011
    Messages:
    3,862
    Message Count:
    3,862
    Likes Received:
    370
    Trophy Points:
    83
    Location:
    WHO(1)ville, Unixland
    jgreco, May 10, 2012

    Yes, you can, kinda. Use two different shares pointing to the same files. For our anonymous read-only shares, we have corresponding shares named ${share}rw for maintenance and management purposes, and it works fine.
  16. Offline

    duckman

    Member Since:
    Jan 24, 2012
    Messages:
    15
    Message Count:
    15
    Likes Received:
    0
    Trophy Points:
    0
    duckman, May 10, 2012

    @jgreco Yes, that's what I did too in the end.

    It's odd though - in the CIFS share options there is Allow Anonymous (which suggests that anonymous are allowed, perhaps in addition to authenticated as well?)
    And also, and this is the kicker, Only Allow Anonymous. This definitely suggests that you can have a single share that is authenticated and also allow Anonymous, else why even have this option at all? Ticking it on or off makes no odds...
  17. Offline

    jgreco Resident Grinch

    Member Since:
    May 29, 2011
    Messages:
    3,862
    Message Count:
    3,862
    Likes Received:
    370
    Trophy Points:
    83
    Location:
    WHO(1)ville, Unixland
    jgreco, May 11, 2012

    I won't pretend to understand it either, don't feel bad.
  18. Offline

    tmacka88 FreeNAS Aware

    Member Since:
    Jul 5, 2011
    Messages:
    234
    Message Count:
    234
    Likes Received:
    2
    Trophy Points:
    18
    tmacka88, May 11, 2012

    any idea when a stable RC version will be released? I want to upgrade but dont want to have to re do all the plug in mods every time i upgrade.

    cheers
  19. Offline

    ProtoSD FreeNAS Guru

    Member Since:
    Jul 1, 2011
    Messages:
    3,358
    Message Count:
    3,358
    Likes Received:
    7
    Trophy Points:
    38
    Location:
    Leaving FreeNAS
    ProtoSD, May 11, 2012

    There's probably going to be another beta sometime soon. I suspect we won't see an RC until the end of May or beginning of June at the earliest. Apparently they're working on a way to upgrade plugins before the next beta, so if you don't want to redo your plugins, wait a bit longer. You'll probably have to redo them at least one more time anyway if you upgrade before the 8.2 Release.
  20. Offline

    jgreco Resident Grinch

    Member Since:
    May 29, 2011
    Messages:
    3,862
    Message Count:
    3,862
    Likes Received:
    370
    Trophy Points:
    83
    Location:
    WHO(1)ville, Unixland
    jgreco, May 12, 2012

    I'd expect that you'd have to redo them at least one more time anyways regardless.

Share This Page