OneFS 7.0.1.5 Release Notes

Isilon OneFS
Release number 7.0.1.5
Release notes
April, 2013
New features and changes......................................................................................... 2 Environment and system requirements...................................................................... 6 Resolved issues......................................................................................................... 8 Known issues and limitations.................................................................................. 21 Upgrading OneFS..................................................................................................... 31 Where to go for support............................................................................................37 Pre-OneFS 7.0 command mapping........................................................................... 38
u u u u u u u
Release notes
New features and changes

This release includes a number of new features and enhancements.
New in OneFS 7.0.1.5

This version of Isilon OneFS includes the following new features and enhancements, and changes the functionality that was present in earlier versions of OneFS.
u
Support for Smart Modular boot drives

Adds support for Smart Modular 8 GB boot drives.
Support for Mars-K Plus ACO firmware

Adds support for Mars-K Plus ACO disk firmware.
Support for Seagate Megalodon hard drive

Adds support for Seagate Megalodon 4 TB drive firmware.
Support for Western Digital boot drives

Adds support for Western Digital 8 GB boot drives.

No new features are introduced in this release. This release resolves issues found in the previous release of OneFS.

This version of Isilon OneFS includes the following new features and enhancements, and changes to functionality that was present in earlier versions of OneFS.
u
Disconnected battery detection

Node batteries that disconnect during shipping are detected.
Support for Cobra-E drive firmware

Adds support for version A350 of the Cobra-E drive firmware.
Support for Seagate Manta Ray firmware

Adds support for Seagate Manta Ray 3 TB drive firmware.
Antivirus scan enhancement

Antivirus policy scans open files with less impact to the system.
Bash shell upgrade

The bash shell is upgraded from version 3.3.39 to version 4.1.

u
Onsite Verification Test (OVT) Support

Adds OVT support for firmware included in Isilon Firmware Package 8.2.
OneFS 7.0.1.5
Release notes

No new features are introduced in this release. This release resolves an issue found in the previous release of OneFS.
New in OneFS 7.0.1

u
Aspera support
Reintroduces support for the Aspera high-performance file transfer software.
Microsoft Windows 8 support

Reintroduces support for clients running Microsoft Windows 8.
IQ 32000X-SSD support
Support for IQ 32000X-SSD storage nodes.
New in OneFS 7.0

u
Access zones
Access zones provide a method for users from different authentication providers to access different cluster resources based on the IP address that they connect to. In this version of OneFS, all user access to the cluster is controlled through access zones. OneFS includes a built-in access zone called system that by default provides the same behavior as that in OneFS 6.5, using all available authentication providers, NFS exports, and SMB shares. You can partition the cluster into additional access zones and configure each zone with its own SMB namespace and list of providers; however, NFS users can authenticate only through the system zone. Multiple access zones can be particularly useful for server consolidation, for example when merging multiple Windows file servers that are potentially joined to different untrusted forests. For more information, see Access zones in the OneFS 7.0 Administration Guide.
Role-based administration
In versions of OneFS earlier than OneFS 7.0, only the root user and the admin user could administer the cluster through the web administration interface and the command-line interface (CLI). In OneFS 7.0, you can grant web and SSH login and configuration access to nonroot users by assigning them to administrator roles. A role is a collection of OneFS privileges, usually associated with a configuration subsystem, that are granted to members of that role as they log in to the cluster through the OneFS Platform API, the OneFS CLI, or the OneFS web administration interface. In addition to built-in roles that are included for security, auditing, and system administration, you can create custom roles with their own sets of privileges. By default, only the root and admin user accounts can log in to the cluster and perform administrative tasks, and only root and admin users can add members to roles. For more information, see Roles and privileges in the OneFS 7.0 Administration Guide.
SmartLock
Isilon SmartLock operation modes enable you to archive your data according to your retention requirements. Compliance mode provides "immutable archiving," which enables compliance with SEC 17a-4 regulations. Enterprise mode provides less-restrictive archiving, which is not
Release notes
compliant with SEC regulations. SmartLock functionality requires a separate SmartLock software license.
u
Automatic provisioning and SmartPools

Automatic configuration of disk pools simplifies administration and improves disk performance when protecting larger clusters. Isilon SmartPools tiers simplify data-policy creation and management. For more information, see ifs_c_smartpools_changes on page 6.
SyncIQ automated failover and failback

Isilon SyncIQ provides continuous data availability through automated failover and failback of data sets across clusters. Failover migrates data, with minimal interruption, to a secondary cluster in the event of an outage. Failback restores the original source data to a consistent state after the primary cluster becomes available again. This functionality requires separate SyncIQ software licenses for both the source and target clusters.
Snapshot revert
Isilon SnapshotIQ enables you to revert an entire snapshot to its top-level directory through the OneFS user interfaces. This functionality requires a separate SnapshotIQ software license.
Fast upgrade
Major OneFS upgrades and reboots finish in significantly less time than in earlier versions, regardless of cluster size and composition.
Endurant cache
An improved cache delivers stable, low-latency NFS writes. Uncommitted writes are protected across the cluster with the specified level of mirrored protection while in the write cache.
Multi-threaded I/O
Random write performance is improved for large files. By providing byte-range write locking, multiple threads per node can simultaneously write to regions of the same large file.
Platform API
The Isilon OneFS Platform API provides a RESTful programmatic interface that enables you to automate cluster management, configuration, and monitoring. The OneFS Platform API integrates with the OneFS role-based authentication functionality for increased security and fine-grained control. The earlier version of the OneFS Platform API, which required a license, is no longer supported. The new OneFS Platform API does not require a license.
VMware API integration

OneFS supports the VMware vStorage API for Storage Awareness (VASA) and the VMware vSphere API for Array Integration (VAAI). VAAI for NFS support requires an ESXi plug-in.
File clones
OneFS provides rapid, efficient provisioning of full read/write copies of files, LUNs, and other clones. OneFS also provides simple virtual machine (VM) "linked cloning" through tight VMware API integration. This functionality requires a separate Isilon SnapshotIQ software license.
OneFS command-line interface

The OneFS command-line interface (CLI) is being reorganized starting in OneFS 7.0. The goal of this reorganization is to increase ease of use through consistency. Reorganized commands reuse options and argument formats across multiple commands to ensure a cohesive experience. Eventually all commands will be reorganized to fit the patterns established for the new CLI. In some cases, you might want to run a command from an earlier version of OneFS through the OneFS 7.0 CLI. You can do this by running isi_classic commands. For example, the following command is valid in OneFS 7.0: isi_classic snapshot create newSnap /ifs/data/media
OneFS 7.0.1.5
Release notes
The isi_classic command is a temporary tool that will be deprecated in a later version of OneFS.
u
OneFS web administration interface

This version of OneFS introduces a redesign of the OneFS web administration interface. If you are unable to connect to the OneFS web administration interface after upgrading OneFS, clear the browser cache and then try again.
InsightIQ support
OneFS 7.0 is compatible with InsightIQ 2.1 and later. Versions of InsightIQ earlier than 2.1 are not compatible with OneFS 7.0. If you are upgrading InsightIQ to version 2.1 and OneFS to version 7.0, it is recommended that you upgrade InsightIQ first and then upgrade OneFS.
SMB 2.1
OneFS delivers improved SMB performance and reliability through its support for client oplocks and leases, and large (1 MB) MTU sizes.
NFS
OneFS provides single-node lookup for streamlined initial verification and mounting, improved netgroup performance, and enhanced handling of stale exports.
iSCSI
Isilon iSCSI performance is improved through a redesigned architecture, parallel LUN allocation, and zero-copy support. Logical unit cloning operations are now handled by file system clones. Shadow volumes are no longer supported. This functionality requires a separate Isilon iSCSI software license.
Shadow volumes
OneFS 7.0 adds file system support for cloned LUNs, duplicating the functionality of shadow volume clones in earlier versions of OneFS. Neither the OneFS CLI nor the OneFS web administration interface offers options for displaying shadow volume clones.
Job management
This version of OneFS introduces three new jobs. The DomainMark job associates a path and its contents with a domain. The ShadowStoreDelete job creates free space from space associated with a shadow store. The SnapRevert job replaces the contents of a directory with the data stored in a snapshot.
LDAP provider
When the current LDAP provider was introduced in OneFS 6.5, the legacy LDAP provider was retained for backward compatibility. In this version of OneFS, the legacy LDAP provider is no longer supported. If you are upgrading from OneFS 6.5 to OneFS 7.0, only the configuration settings for the current LDAP provider are migrated. If you are upgrading to OneFS 7.0 from a pre-6.5 version of OneFS, no LDAP configuration settings are migrated. In OneFS 6.5, you could specify a predefined set of attributes for the LDAP provider based on the RFC 2307, Active Directory, or ldapsam schema. In this version of OneFS, you must configure each attribute separately.
64-bit userspace
This version of OneFS includes a 64-bit userspace. If you are running any custom tools that are based on a 32-bit userspace, you must recompile them after upgrading OneFS.
Telnet_d support removed

Telnet service has been removed from OneFS. Telnet is an inherently insecure protocol, and it can negatively affect the overall security of the system. SSH should be used for all shell access.
New in OneFS 7.0
Release notes
SmartPools changes
The design of SmartPools is different from earlier versions and may require changes to the cluster configuration before you begin the upgrade process. The primary technical design of SmartPools design was enhanced to meet the following goals:
u
Provide file storage in a single logical container that can safely scale to larger than 15 PB with no disruption. Simplify the configuration, management, monitoring, and performance optimization of the cluster. Increase performance for network-based I/O for data files in the single large container. This version of OneFS includes two new types of logical storage pools: node pools and tiers. Node pools are groups of equivalence-class nodes that are associated in a single storage pool. A tier is a user-defined collection of node pools that can be used as a target for a file pool policy. Disk pools cannot contain mixed node types; however, mixed node types can be combined in tiers. For a list of compatible node types, see "OneFS 7.0 Node Provisioning Equivalences" in the Isilon Supportability and Compatibility Guide. Disk pools can no longer be viewed or targeted directly through the web administration interface or the command-line interface; disk pools are managed exclusively by the system through autoprovisioning. Autoprovisioning is the process through which the system automatically assigns nodes to node pools and drives to disk pools, replacing manual disk pool creation and management. For more information, see the OneFS Administration Guide. To avoid overloading node pools with SSDs, certain thresholds must be satisfied for global namespace acceleration to be enabled. Global namespace acceleration can be enabled if 20% or more of the nodes in the cluster contain at least one SSD and 1.5% or more of the total cluster storage is SSD-based. For best results, ensure that at least 2.0% of the total cluster storage is SSD-based before enabling global namespace acceleration.
As a result, the following changes were made to SmartPools in this version of OneFS:
u
Environment and system requirements

Before installing OneFS, verify that your cluster and operating environment meet the minimum system requirements.
Supported Isilon nodes

OneFS runs only on supported Isilon hardware platforms. This version of OneFS supports the following hardware platforms:
u u u u u u u
IQ 1920X IQ 3000X IQ 6000X EX 6000 IQ 9000X EX 9000 IQ 12000X
OneFS 7.0.1.5
Release notes
u u u u u u u u u u u u u u u u u u
EX 12000 IQ 10000X-SSD IQ 32000X-SSD IQ 36000X IQ 5400S IQ 5000S-SSD IQ 72000X IQ 108000X IQ 36NL IQ 72NL IQ 108NL Backup Accelerator IQ Accelerator IQ Accelerator-X X200 S200 X400 NL400
Upgrade compatibility
Upgrades are available only between supported OneFS versions. If the cluster is not running a supported version of OneFS, contact Isilon Technical Support before attempting an upgrade. Upgrades are supported for the following OneFS versions. Version OneFS 6.0 OneFS 6.0.1 OneFS 6.0.2 OneFS 6.0.3 OneFS 6.0.4 OneFS 6.0.5 OneFS 6.5.0 OneFS 6.5.1 OneFS 6.5.2 OneFS 6.5.3 OneFS 6.5.4 OneFS 6.5.5
Simultaneous upgrade Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Rolling upgrade No No No No No No No No No No No No
Upgrade compatibility
7
Release notes
Version OneFS 7.0 OneFS 7.0.1
Simultaneous upgrade Yes Yes
Rolling upgrade Yes Yes
Browser compatibility
The OneFS web interface supports most modern web browsers with JavaScript, cookies, and SSL enabled. Adobe Flash is required to view charts. Browser Microsoft Internet Explorer Mozilla Firefox Google Chrome Apple Safari
Version 8 and 9 Latest stable version Latest stable version 5.1.x and 6 on Mac OS X
Resolved issues
This release resolves a number of issues found in earlier releases.
Resolved issues in OneFS 7.0.1.5

The following issues are resolved in OneFS 7.0.1.5. ID
98041
Description
Attempts to send an email report resulted in the error: Too many
positional arguments for function call.

100060 During an upgrade to 7.0.1, the backslash character was removed from SMB configuration options. If the Impersonate User option was set to DOMAIN \user, the configuration failed. Nodes connected to a network that supported Appletalk wrote kernel logging to /var/log/message every forty seconds. The isi hdfs commands failed to read the encoded configuration file, which resulted in a Corrupted configuration error. The Flexprotect drive scan phase performed more write operations than were needed, which resulted in longer job runtime. Onsite Verification Test (OVT) failed if a motherboard had a twelve-digit serial number. After an upgrade to OneFS 7.0.1, SyncIQ policies were left with an invalid Snapshot alias name configuration value and could no longer run. The SMB service became unavailable and generated a core file when a zerocopy write operation unsuccessfully executed. Following an upgrade from OneFS 6.5.5 to 7.0, if an SMB share had the name Security, you could not view the configuration for the share.
100489 101203
101292 101783 101905 101910 101938
OneFS 7.0.1.5
Release notes
ID
102018 102020 102139
Description
SMB workflows that relied on a large number of SMB change notifications experienced client disconnections and service restarts. The timeout value for disk drives was equal to the lock timeout used for multinode operations, which resulted in a multi-node reboot event when a drive became unresponsive on a single node. Could not add decimal values for quotas through the web interface. The wait time associated with identity mapping calls to an authentication source could not be lowered to a value of 0. A caller holding a lock was blocked, which affected cluster performance. When attempting to view Smartpools, the web interface crashed during license verification. NFS configuration options that were available only in the CLI displayed inaccurately in the web interface and resulted in inconsistent handling of unresolvable clients. When attempting to view Smartpools, the web interface failed to load after referencing a target pool policy that did not exist. The isi_vol_copy utility applied incorrect ACLs to migrated alternate data streams. The output of the isi status command displayed an inaccurate Virtual HotSpare (VHS) size due to calculation errors. If the Primary Group attribute for a user referenced a non-existent group name, running the isi auth mapping token command against the user failed. All NFS connections were considered root clients and were given root privileges. The SMB auditing function did not log delete operations. Following an upgrade from OneFS 6.5.5 to 7.0, SMB configuration contained incompatible values related to client credit allocation. OneFS disabled a SyncIQ policy after several failed attempts to run the policy. After a cluster was added to the list of trusted sites in Internet Explorer, error messages continued to appear. Memory consumed by the SMB server service increased over several days and resulted in a node reboot due to memory exhaustion. The SMB server indicated to a client that a file closed successfully while the server file was still seen by the server as in use. This condition prevented other clients from writing to the file until the first client disconnected. HDFS 2 clients could not connect to the cluster. If a FlexProtectLin job was running for a smartfailed drive when a second drive failed, data on the second drive was not repaired. If SMB clients that were connected to a single node opened a file more than 65,533 times without ever closing the file, the node rebooted.
102309 102467
102479 102482
102557 102583 102650 102657
102790 102794 102825 102912 102914 103000 103024
103137 103260 103262
Release notes
ID
103372
Description
Memory consumed by the SMB server service increased over several days and resulted in a restart of the service due to memory exhaustion.

The following issues are resolved in OneFS 7.0.1.4. ID 97669
Description If a quota is added while the QuotaScan job is running, the new quota is prematurely marked as ready. Clusters in compliance mode only allowed the Onsite Verification Test (OVT) to run with the -local option. If the cluster filesystem encoding was set to a value other than UTF8, the DomainMark and SnapRevert jobs failed. Following a failed battery test and node restart, batteries were not immediately tested. Changing permissions on an SMB share did not grant the user or group permissions for delete or rename. Incorrect lock request responses from the OneFS iSCSI service led to unexpected behavior in connections from ESX clients. Support IQ did not deliver a weekly status update. Quotas were unable to be associated with custom email templates from the CLI. The NFS client lock data did not replicate correctly between all cluster nodes, leading to inconsistent locking data and an unresponsive lockd thread on one node. The configuration for SMB share permissions in the web interface displayed user IDs instead of usernames for users who were not included in the system access zone. From the web interface, the LDAP configuration page incorrectly specified that an LDAP server must be entered as an IP or hostname. The LWIO daemon crashed and wrote a core file during node shutdown.
99153
99382
100328 100332
100399
100434 100559 100765
100860
100944
100964
10
OneFS 7.0.1.5
Release notes
ID 101032 101053
Description You could not clone the most recent version of a file. When searching for open files with psfile tools, the LWIO daemon restartsed and caused an error. The NetBIOS Name Service (NBNS) did not start after being enabled. The isi_vol_copy utility terminated after encountering an unreadable inode in the data stream. A user account was unable to log in with SSH if the account was mapped to a different UID. The isi_vol_copy utility did not support the migration of special character files. A node was placed in a read-only state after a single failed battery test. Running DomainMark on an invalid path produced an unhandled error. DomainMark and SnapRevert did not run without a SyncIQ license activated. A node panic occurred after a drive failed during the MediaScan job. A high SMB1 connection load caused the SMB service to write a core file when generating a session response code. When working on a wide directory, SyncIQ returned the error Failed to delete
101055 101077
101117 101170 101206 101299 101300 101397 101430
101546
user attribute.
101566 A timing error allowed SMB locks to be taken out of order, which resulted in a node becoming unresponsive. Users were unable to log in with SSH when a process held an exclusive lock on /ifs. The Onsite Verification Test (OVT) did not support a 12-digit serial number on new motherboards.
101588
101783
11
Release notes

Description NDMP restore failed if the requested file list contained an empty path. Empty paths occur when a restore of an entire backup is needed. During an incremental backup, directories leading to backed up files were not backed up. Email addresses were not pulled from Active Directory domains by lsass NIS providers, which resulted in incorrect email addresses populated in quota notifications. Invalid NDMP user names for authentication caused the NDMP server to crash. NDMP backups included a copy of an ADS file for the associated file and any hard links to that file. If a root user typed the su command to mimic a local user, that local user retained the permission level of the root user. Backed up WORM data created duplicate calls to rebuild header information, which consumed additional tape space and CPU cycles. Incremental NDMP backups backed up a file as a hardlink if hardlinks pointed to the file. If a file with the immutable bit set was included in a SyncIQ policy, the policy failed because the file could not be modified. SMB I/O file operations updated the "last modified" timestamp. Partial adds of a netgroup timed out. An NFS client released all of its locks approximately 45 seconds before a nodecaused group change, which resulted in failures of nfs.lockd to respond to requests. A cluster in compliance mode could not install firmware or userspace patches. NDMP restore failed if the directory path was longer than 1024 characters.
87699 89123
92272 92491
94132
94396
94838 96111
97399 97817 98093
99154 99247
12
OneFS 7.0.1.5
Release notes
ID 99344
Description Files with a user ID higher than 65535 defaulted to 65535 when copied by the isi_vol_copy utility. The FSAnalyze job did not complete. OneFS incorrectly displayed time zone revisions made between March 2nd, 2010 and March 24th, 2012. NL400 nodes configured with 48 GB of memory did not pass OVT. The following commands failed to generate lists in JSON format: isi auth roles list -format=json and isi quota quotas list --format=json. The compadmin user could not delete files from /var/crash in compliance mode. If a cluster contained nodes with no external network and the remaining nodes lost communication with the target during a SyncIQ job, the job continued to run on only the nodes with no network rather than fail and generate an alert. An Apache error did not include path information for troubleshooting. An incremental SyncIQ job failed if the job included a file of the same name as a previously-synced, empty directory. NDMP restore failed when the cluster had an aggregate interface configured. Users with "run-as-root" access to an SMB share were not assigned the correct permissions. A 60-second delay was experienced when SMB files were copied to paths subject to a "scanon-close" antivirus policy. When an NFS export was configured to maplookup-uid, the map root setting was applied to unknown users. If the /ifs directory became unavailable during a backup, the reader process failed and the writer process became unresponsive.
99437 99654
99709 99765
99784
99785
99892 100012
100066 100092
100127
100139
100145
13
Release notes
ID 100158
Description When Node 1 of a source cluster was not reachable by all nodes through the external interface, SyncIQ jobs failed. SMB share ACL entries added from the command line were placed above the last entry, instead of becoming the last entry. The host-acl option for SMB shares did not support subnets for the allow and deny options. The SMB server allowed multiple clients to modify a file simultaneously. Before an upgrade, there was no confirmation that the disk pool policy was set correctly on / ifs/.ifsvar. SyncIQ failed with the error message Too
100240
100248 100252 100267
100353
many links when the source file had at

least one hard link, and the matching destination file was a soft link directed at an external file system. 100398 An NFS file owner could override the lack of write permissions for a file, but was denied access when setting the new size attribute. A SyncIQ transfer of duplicate paths resulted in an Error while transferring message. 100421 Incremental backups with FH_REPORT_FULL_DIRENTS turned on did not complete. A node 10 GigE network interface was unresponsive until the node was restarted. Email alerts failed when clients did not send a
quit command before closing the connection
100413
100427 100438
to the mail server. 100445 100557 An SMB file created with a Mandatory Integrity Control ACE failed due to an unknown ACE type. The AVScan job failed to keep pace with realtime scanning, which resulted in a large work queue and, in rare cases, a node panic. Quota email message templates formatted in HTML were sent as plain text. OneFS failed to look up the email address attribute of an LDAP user account.
100561 100585
14
OneFS 7.0.1.5
Release notes
ID 100605
Description If the SMB configuration option ClientCreditMinimum had a value of less than 4 when a cluster was upgraded from OneFS 6.5.5 to 7.0.1, SMB connections failed until the value was reset to 4 or higher. When the recovery shell was entered, the following error appeared: File "/usr/
100631
local/lib/python2.6/ subprocess.py", line 1106, in _execute_child: OSError: [Errno 2] No such file or directory
100661 The dynamic attribute INATTR_SNAPIDS grew too large, which led to a kmem_map too
small error.
100670 Rolling upgrades from OneFS 7.0.0 to 7.0.1 resulted in an incorrect diskpool database version, which prevented new nodes from being added to diskpools. Request to open srvsvc pipe failed. SyncIQ backup files were removed when an error occurred during an upgrade to OneFS 7.0.1. Users were repeatedly disconnected from an SMB share. If the SMB --host-acl option was set on hidden shares, the option was honored, but could not be viewed. When more than one NFS v3 clients mounted the same node using Kerberos authentication, the node panicked. SMB file operations were not logged as expected when audit logging was enabled.
100721 100722
100735 100798
100848
100899

Description SSH connections with public key authentication were not authenticated with role-based access control.
15
Release notes
ID 97131
Description NDMP hardlinks containing non-ASCII characters and symlinks linking to file names containing non-ASCII characters failed to be restored. The number of events for each event category was not summarized correctly on the Notification Rules page in the OneFS web administration interface. After an upgrade to from OneFS 6.0 or 6.5 to OneFS 7.0, a setting that dynamically creates home directories no longer worked for users who connected through FTP. An NFS client, when defined in an NIS netgroup, was assigned the wrong permissions when the client was specified as both a rootclient and a client on an export. Netgroup memberships were checked every 24 hours or after an export change. They are now expired and refreshed every 60 minutes or after an export change. Incremental backups did not back up modified files in a directory if that directory was renamed. Modified files in a renamed directory were captured only by a full backup. HDFS jobs failed due to a timeout when a compute node did not recognize the closed socket state of a work thread. The file provider configuration value to normalize user lookups was not carried over when upgrading from OneFS 6.5.5 to 7.0.1. SyncIQ failed to update a synchronized file when new data was written at an offset of 4 GB. SyncIQ job directories that were created or moved with encoding other than UTF-8 caused the DomainMark and SnapRevert jobs to not start. An SMB search pattern that included a forwardslash character did not return results. A user could not connect to a Windows homedirectory share if the user's name was the share name. When logged in to the OneFS web interface as an administrator, an Active Directory (AD)
97505
98176
98299
98458
98549
98593
99051
99233 99382
99596 99660
99666
16
OneFS 7.0.1.5
Release notes
ID -
Description
search query that contained wildcard characters did not return results. LSI2008 firmware contained in Firmware Package 8.2 was not supported. Excessive error messages were stored in the /var/log/messages directory. Backup and restore tasks stayed in QUEUED status for an excessively long time before they began to process. Group memberships based on the GSID did not register, and produced incorrect permissions. Running the pw -a command resulted in looped output. OneFS could not look up users in OpenLDAP servers because the base search scope for the user was incorrect. OneFS 7.0 requires clusters running Global Namespace Acceleration (GNA) to meet an SSDto-capacity ratio of 1.5%, up from .5% in earlier versions of OneFS. On clusters with a ratio of less than 1.5% that were upgraded to OneFS 7.0, GNA was disabled automatically with no notification. An NDMP backup job did not respond when a tape device returned a write error. The job became unresponsive until it was manually cancelled. OneFS 7.0.1.0 was not compatible with a rolling upgrade to OneFS 7.0.1.1. When a LIN reached its storage limit, an 8k extension block was created at equivalent protection levels. Because no automated process maintained the storage limit, the extension blocks filled the disk pool to capacity.
99758 99789 99790
99827 99832
99837
99878
99975
99988 100009

The following issue is resolved in OneFS 7.0.1.1. ID 99721
Description Copying files with the SMB protocol and access control lists caused the kernel to leak memory.
17
Release notes
ID -
Description
Eventually this would result in a node panic unless the node was rebooted.
Resolved issues in OneFS 7.0.1

The following issues are resolved in OneFS 7.0.1. ID 96581 97743
Description Field upgrades of disks or RAM were not supported. In clusters that contained both nodes with solid state drives (SSDs) and nodes without SSDs, OneFS increased running time by applying jobs that were optimized for SSDs across all nodes. 32000X-SSD nodes were not supported. Under stress, NFS lock information leaked, leading to Fatal trap 12 node panics in lkfi_client_remove.
97400 98008
98018 98128
SnapshotIQ setting changes appeared to take effect, but advanced settings were not preserved after the node was restarted. Performing a chgrp operation on a file in a SmartLock domain that was either the source or target of a SyncIQ operation caused the synchronization job to fail with the following message: syncattr error: Read-only file
system.
98533 98566 When a group change, such as a drive stall, occurred during a FlexProtect job, another FlexProtect job was queued even if it was unnecessary. SMB2 loads of more than 65,536 files led to the error: Too many open
files.
98726 The cluster did not log login attempts over SMB2 in /var/log/audit/ smb.log. Aspera for Isilon was not supported. SupportIQ did not honor proxy configuration settings. In compliance mode, running the sudo isi auth users modify -user=root command re-enabled the root account. After an upgrade, the failback action ran continuously without transferring any files. In the OneFS web administration interface, the SmartPools page did not display large, non-sequential group statements correctly. Windows 8 clients were not supported. 1 GigE and 10 GigE aggregate interfaces could not be included in separate network pools. The system incorrectly concluded that the interfaces overlap and cannot be split into different pools.
98969 98987 99073
99132 99162 99186 99219
18
OneFS 7.0.1.5
Release notes
ID 99285
Description InsightIQ did not collect performance data from clusters that were configured with advanced time-zone settings, including all localized European and Asian time zones. When a write failed due to an exceeded disk quota or a full cluster, the node became unresponsive.
99618
Resolved issues in OneFS 7.0

The following issues are resolved in OneFS 7.0. ID 18467 / 65272 68670 N/A
Description Automatic creation of a home directory upon initial SMB login was not supported. A third-party component of SupportIQ consumed high levels of node CPU time. Inherited ACEs on files that were created over NFS did not receive the inherited_ace flag. This prevented NFS clients from deleting files that they should have been allowed to delete. After a rolling upgrade, the isi pkg info command returned a list of previously installed patches. A firmware update of SanDisk boot drives did not succeed. Importing an iSCSI LUN from a snapshot returned a read-only error. When editing export options in the OneFS web administration interface, if you selected and then cleared a grayed-out option, it appeared to be a default option. When contacting domain controllers over a secure channel, leaked sockets occasionally occurred. The NFS Export page in the OneFS web administration interface displayed incorrect security options after reverting to default settings. Case normalization over SMB was not supported. If a master node lost external network connectivity, it took up to 24 hours for the cluster to send an event notification. In certain workflows, the ntp.drift file filled up the root partition, triggering critical alerts. An issue in the srvsvcd process caused it to core, which resulted in the disconnection of clients that were using the srvsvc API, such as the Microsoft MMC console. Windows 7 clients were unable to use Offline Folders over SMB 2. Updated events lost quiet and end status. Under heavy NFS load, some locks were ignored, resulting in a node panic.
70097
70943 72319 72339 / 92140 72410 72709 72871 75103 76009
76500
77017 77917 78183
Resolved issues in OneFS 7.0
19
Release notes
ID 79740 79809 80083 80860 81189
Description SyncIQ policies failed if a rule had an exclude path that contained a symbolic link on the source. When backing up a directory that contained more than one million files, the job became unresponsive and the backup operation eventually timed out. After a node rebooted, it started up in shutdown_read_only mode when it rejoined a group. An NFS-mounted directory responded incorrectly to a POSIX W_OK query by indicating that the directory was writable when it was not writable. The OneFS web administration interface indicated that a working aggregate interface was inoperative ("down") and prevented the proper configuration of aggregate interfaces. If a SyncIQ policy included a large number of exclude directories, the associated jobs failed to run. State transition timeouts occurred in the job engine. If you attempted to modify an SMB share name that contained both uppercase and lowercase characters, the share was deleted. The SyncIQ scheduler failed to start all policies. NDMP three-way restoration performance was slow. The user mapper ignored GIDs that were provided by NFS clients. File ownership was incorrect, even after running the system PermissionRepair job. Stuck reservations caused iSCSI volumes to be unmountable with ESXi 5.x. OneFS responded to the deprecated SMB_COM_QUERY_INFORMATION request with STATUS_NOT_SUPPORTED. The OneFS web administration interface incorrectly reported loss of quorum after a OneFS upgrade. TREE_CONNECT failed when the user name provided through NTLM was in the form user@domain_fqdn. Hadoop MapReduce speculative execution did not work with OneFS. Solaris clients mounting the cluster using NFSv4 resulted in an ACCESS
81312 81553 81687 82394 82721 82919 82925 83051 83195
83290 83527
83540 83553
FAILED error.
83629 84166 84702 84706 85136 A single node transition to read-only caused write failures. Authentication failures occurred after upgrading from a pre-6.5 version of OneFS. A single node panic caused multiple node panics. Snapshots failed with the EDEADLK message appearing in the logs. A specific event for the SAS Controller was not triggered.
20
OneFS 7.0.1.5
Release notes
ID 85851 85974 86163
Description Quota email message templates that were formatted in HTML were sent as plain text. A kernel panic occurred when an export update operation was running. In certain situations with large numbers of Kerberos clients per node, a node crashed with a stack trace in svc_rpc_gss_forget_client. The cluster failed to handle the OTHER error code that was returned from the Centrify LDAP server. A rare deadlock was triggered by SyncIQ. When running NDMP restores, the user sticky bit was not set on the restored file. In X200 and S200 nodes, the LCD panel did not display anything. Statistic counters for file sizes larger than 1 MB were incorrect. If the isi_archive process ran out of memory, the process printed a message to the console and exited silently. Because the NDMP daemon did not have a console connection, NDMP backup or restore jobs failed for no apparent reason. DMAs detected an incorrect mover record count during an NDMP tape copy job and failed the operation. In addition, during an NDMP tape copy or a three-way restoration, insufficient bytes were moved to the target. When restoring backed-up files, the DOS_NOINDEX bit was ignored and all files were capable of being indexed. Due to memory corruption, NDMP processes crashed when multiple
86181 86281 86469 86533 86639 86640
86729
87477 87601
NDMP_CONFIG_GET_SCSI_INFO or NDMP_CONFIG_GET_TAPE_INFO messages were processed.

87781 Running the isi_gather logs command produced an error message that contained incorrect information: ILLEGAL REQUEST ... Invalid
field in CDB.
90890 91739 93606 Running the isi sync pol delete all command did not delete all policies. Rolling upgrades failed if each node was not in each SmartConnect pool. The OneFS web administration interface and the isi sync target ls command displayed incorrect SyncIQ source-cluster information. A risk of local privilege escalation attack existed for various operating systems running on an Intel processor, including OneFS, as identified in CVE-2012-0217. By default, the SmartPools and SetProtectPlus jobs no longer automatically reported space used in association with various policies.
95866 97110
Known issues and limitations

The following issues and limitations are known to be present in OneFS.
21
Release notes
ID 18901
Description File names that contain non-standard Unicode characters might appear incorrectly when viewed with File System Explorer. Workaround: Rename files with standard Unicode characters.
24504
You might receive an alert that a temporary license is expired even though a permanent license is installed. Workaround: Use the command-line interface or the web administration interface to quiet the alert.
24621
The command-line wizard requires a default gateway to set up a cluster. You may not have a default gateway if your network uses a local DNS server instead. Workaround: Enter 0.0.0.0 for your default gateway.
39124
The web administration interface displays only 100 quotas, even if more exist. Workaround: Run the isi quota command to view all of the quotas.
48930
The isi_migr_scheduler command periodically consumes too many CPU cycles. There is no known workaround at this time. A usage error with the shutdown command results in a shutdown failed message and puts the node in read-only mode. There is no known workaround at this time.
54120
54477
In the web administration interface, if you click the Start job link more than once, multiple instances of the job might start. Workaround: Click the link once.
55247
The SNMP MIB might report incorrect speeds for aggregated network interfaces. In particular, the snmpwalk command displays 100 Mb for the fec0 interface. There is no known workaround at this time. The netstat -rs command reports inaccurate information. There is no known workaround at this time. If an IPv6 subnet includes two or more NICs, one NIC might become unresponsive over IPv6. There is no known workaround at this time. Isolated external networks on a single cluster can cause SyncIQ policies to fail. There is no known workaround at this time. While a cluster processes a heavy I/O load, graphs in the web administration interface might display an Unreliable Data message. Workaround: Wait until the cluster is less heavily loaded to view graphs or run the
isi statistics command.
55576
57880 60142 62736
63330
Idle SMB session objects are not timed out by the server. Workaround: Running the isi smb sessions command manually closes the connection.
64712
You cannot enter DNS search domains that contain underscores from the commandline interface or the web administration interface.
22
OneFS 7.0.1.5
Release notes
ID -
Description
Workaround: Edit the /ifs/.ifsvar/modules/flexnet/flx_config.xml file to add an element that contains the target domain to <dns-domains>. The final phase of the FSAnalyze job runs on one node and can consume excessive resources on that node. There is no known workaround at this time. If the /etc/isilon_system_config file or any etc VPD file is blank, an isi_dongle_sync -p operation will not update the VPD EEPROM data. There is no known workaround at this time. Monitoring with SNMP, InsightIQ, or the isi statistics command can fail when a cluster is heavily loaded. Quota imports that are issued from the web administration interface might fail. Workaround: Run the isi quota import command.
64854 67932
68559
68602
68656
In the web administration interface, the Job History summary page does not display end times for jobs. Workaround: Look for the last entry in the history of a job ID. The time given in the entry's timestamp is when the job ended.
69503 69816 69917
A newly created cluster might not appear to unconfigured nodes for up to three minutes. Writing files past the quota limit over NFSv4 generates an input-output error. There is no known workaround at this time. The default number of NFS server threads was changed to address a potential issue in which the NFS server monopolizes node resources. NFS performance might be lower than expected. Workaround: Adjust the number of nfsd threads by running the following commands, where x is an integer. It is recommended that you set threads_min and threads_max to the same value. Increasing the number of threads can improve performance, but can also cause node stability issues. Modify the minimum number of threads by running the following command:
isi_sysctl_cluster vfs.nfsrv.rpc.threads_min=x
Modify the maximum number of threads by running the following command:
isi_sysctl_cluster vfs.nfsrv.rpc.threads_max=x
70334 After an FSAnalyze job starts, a snapshot is created by default. If the job is paused by higher-priority jobs or takes a long time to complete, the associated snapshot might be kept for a long time. Because the snapshot is on all of /ifs, the snapshot can affect quota, performance, and usage. Workaround: If you are not using InsightIQ, disable all FSAnalyze jobs. You can cancel paused FSAnalyze jobs to reclaim the snapshot. 70413 When you add a node to the cluster, the master control program does not load the sysctl.conf file before the external interfaces have IP addresses. As a result, NFS clients that require 32-bit file handles might encounter issues connecting to newly added nodes.
23
Release notes
ID -
Description
Workaround: On NFS clients that encounter this issue, unmount and then remount the directory. In the web administration interface, if you attempt to verify invalid HTTP or FTP hosts in the cluster diagnostic settings, a connection testing message displays indefinitely. Workaround: Ensure that the HTTP or FTP host settings are correct before trying to verify settings.
70448
70616
Moving files between exports in an NFSv4 overriding-exports scenario may cause unforeseen consequences. Workaround: Configure exports so that they are not exporting similar paths or mapping to two different credentials.
71218
In the web administration interface, the SyncIQ Performance page might not work on clusters larger than 60 nodes. Workaround: Run the isi sync command to set the bandwidth and throttling rules.
71354
OneFS splits a node from a cluster after the node joins the cluster without a valid system configuration number in /etc/isilon_system_config. Workaround: Use Smartfail to remove the node from the cluster. Contact Isilon Technical Support to apply a valid system configuration number to the node and then add the node to the cluster again.
71399
A network interface that is configured as a standby without an IP address triggers an interface down event. Workaround: Quiet the event manually.
71687
OneFS can reassign a static external IP address from a smartfailed node, and replace the static IP address assignment on another node. There is no known workaround at this time. The event subsystem stores historical events in several databases, and some databases might fail to upgrade properly. If this happens, the database is replaced by an empty database with the new format. Historical events are lost. When you create a new target after you move iSCSI shadow clone LUNs, the web administration interface can lock up. Job engine operations can occasionally fail on heavily loaded or busy clusters. Workaround: If an operation fails, wait a moment and then retry the operation.
71840
71919 72109
72200
Reconfiguring aggregate interfaces can leave active events for inactive interfaces. Workaround: Cancel the events manually.
72271
Using the NDMP FILES environmental variable sometimes results in additional directories backing up that do not match the pattern specified by the NDMP FILES variable. The additional directories are always empty, and directories matching the pattern are correctly backed up. This behavior is not harmful. When you add a new ACE that grants run-as-root to an ACL on an SMB share, OneFS adds a duplicate ACE if there is already an entry granting full control to the identity. The extra ACE grants no extra permissions.
72337
24
OneFS 7.0.1.5
Release notes
ID -
Description
Workaround: You can remove the extra ACE by running the isi smb permissions command. In VLAN configurations, the nmbd process generates excessive log entries in /var/log/nmbd.log that say, WARNING: no network interfaces
72652
found. The entries may occur when there are interfaces without IP addresses. There
is no known workaround at this time. 72864 73038 73050 73090 Following a node panic and reboot, a node can become unresponsive after running disk discovery. There is no known workaround at this time. The iSCSI Summary page in the web administration interface may load slowly. An internal sensor monitoring lock-up may not be detected and will not generate an alert. After a node restarts, the mountd process starts before authentication, leading to failed user lookups. Immediately after the node restarts, users might experience permission problems or receive the wrong credentials when they mount a directory over NFS. Workaround: On the client, unmount and remount the directory. 73274 If a media changer device is reserved by a SCSI reservation from another initiator at the time device discovery is performed, the device will fail to be discovered. The device is discovered after the reservation cancels. After an upgrade, when FlexProtect is run with verify upgrade check enabled and one or more drives are down, OneFS might report false data corruption. If this issue occurs, contact Isilon Technical Support. The web administration interface does not display the new settings of the NFSv4 domain name sysctl. Workaround: Use the command-line interface to determine the NFSv4 domain name value. 73531 If domain servers are down, the Active Directory page of the web administration interface might load slowly. Workaround: Run the isi auth refresh command in the command-line interface. 73554 The sum of the per-node throughput and the cluster throughput that the isi status command shows might differ because of caching. The discrepancy is only temporary. Workaround: Run the command again. 73605 73790 74090 If SmartConnect detects that it is in an inconsistent state, it will restart. Attempting to create a hard link to a file in a WORM directory returns the wrong error message. A quieted event might appear in the wrong pane on the Events Summary page of the web administration interface. Workaround: Look for quieted events under Ended Events as well as Quieted Events. 74191 When you rest the pointer over the siblings of a WORM-ready directory, the File System Explorer displays incorrect text.
25
73276
73333
Release notes
ID 74251
Description Workaround: Determine WORM domains by running the isi worm command. LDAP settings that expect a numeric value might fail if given a large integer. Workaround: Assign smaller values to LDAP settings.
74252
LDAP settings that accept string values might accept invalid values. Workaround: Make sure that the values are correct.
74272 74303 75345 75917
When a cluster's capacity reaches 99 percent, there is insufficient space for configuration changes. As a result, the cluster might stop working. VSS 32-bit installation succeeds on a Windows initiator, but the provider doesn't appear in the list of installed providers. Exceeding SmartQuotas thresholds while the file system is under a heavy load might affect the cluster's performance. After a cluster upgrade, old events might appear as current. These alerts do not indicate that an event has recurred. Workaround: Cancel each event by running the isi events cancel <id> command, or cancel all events by running the isi events cancel all command.
75980
Under certain error conditions, some events might be updated with incorrect information, resulting in inconsistent results when listing events. For example, the event type might not match the event message. There is no known workaround for this issue. On the Cluster Overview page of the web administration interface, clicking the ID of a node that requires attention, as indicated by a yellow Status icon, does not provide details about the status. Workaround: In the list of events, sort the nodes by the Scope column or by the
77470
Severity column, and then click View details.

Alternatively, run the isi events list --nodes <id> command to view the events. See article 3828 in the Isilon Knowledge Base, "How to determine why a node is in an attention state." 78827 79341 The isi statistics command displays incorrect NFS protocol latency information. If you have a large number of LUNs active, the event processor might produce a warning about open file descriptors held by the iSCSI daemon. You can safely ignore this warning. 81183 81598 Although SNMP requests can reference multiple object IDs, the OneFS subtree responds only to the first object ID. If a snapshot revert or replication domain exists for a directory, File System Explorer incorrectly displays the directory as a SmartLock directory. This is a display issue only. 83444 User and group details cannot be edited in the web administration interface. If you attempt to modify a user or group, for example by setting the expiration date for a user's password, you will receive an error similar to the following:
26
OneFS 7.0.1.5
Release notes
ID -
Description Error #1: Failed to modify user <username>: The authentication request could not be handled
or
Error #1: Failed to modify group <group_name>: The authentication request could not be handled
Workaround: Do not attempt to edit a user or group unless it is within a local authentication provider. 83537 On rare occasions, the iSCSI protocol can log a data digest error in the iSCSI log. No workaround is required; the protocol will recover and reconnect. 84234 NetApp data migration does not support paths that exceed 1023 characters in length. Attempting to migrate paths longer than 1023 characters from a NetApp Storage System causes migrations to fail with the following message: Connection
halted: HALT: Connect error! Path length exceeds 1023 char.

84376 84457 86328 87092 The web administration interface does not prevent multiple rolling upgrades from starting simultaneously. Some SMB 1 clients send a Tree Connect AndX Request using ASCII to specify a path. The cluster rejects the connection with STATUS_DATA_ERROR. Nodes without subpools appear in the per-node storage statistics but are not in the cluster totals because you cannot write data to unprovisioned nodes. After you perform a successful backup, restoring a large number of files (in the tens of millions) with Symantec's NBU DMA results in a database system error. The error is due to issues with the Symantec NetBackup DMA. The isi smb shares permission create command fails if --permission and -permission-type are not included. The arguments are not optional. The isi events notifications modify <test_rule> --email= <email ID> command fails to add the specified email ID and overwrites the existing email addresses. When you use SmartConnect to log in to the web administration interface, the session fails or returns you to the login page. Workaround: Connect to the cluster with a static IP address instead of a hostname. 92180 93061 SyncIQ may reduce to a single worker thread in the last 1% of a sync, which delays the completion of a job. SyncIQ allows a maximum of five jobs to run at a time. If a SnapRevert job starts while five SyncIQ jobs are running, the SnapRevert job might appear to hang instead of pauseing until the SyncIQ job queue can accept the new job. The SnapRevert job uses a maximum of 40 spawned job threads, regardless of the job engine policies. No workaround is available at this time. Users who mount through NFSv4 and use a non-Active Directory Kerberos server are not recognized in the form of user@realm.
87117
89086
91640
93603 93663
27
Release notes
ID 93753
Description Impact: users are authenticated as nobody. The isi_gather_info utility treats sparse files as regular files when creating the compressed tar archive, which consumes more space than necessary. The default SSL port (8080) for the web administration interface cannot be modified. If an NFS client renames or deletes a file with a handle that is open on an SMB client, the SMB client might be unable to close the handle. The conflict stems from an inherent race condition in SMB that prevents oplocks from breaking on the SMB client. Impact: The SMB client reads data from a stale handle until the handle is closed and reopened. Workaround: Disable oplocks on the SMB share for these types of workflows.
94026 94168
94614
If you use SyncIQ to synchronize data to a target cluster, and this data is later freed on the source cluster because a file reduced in size, the data is not freed on the target cluster when the file is next synchronized. As a result, the space consumed on the target cluster might be greater than the space consumed on the source. The quota configuration import-export functionality is missing from the command-line interface. Workaround: Use the web administration interface.
94797
95493
If the SMB --host-acl option is set on hidden shares, the option is honored but is not viewable. Impact: This makes administration difficult because you cannot see what the --host acl option was previously set to. Since subsequent --host -acl additions overwrite rather than append, you might not know what to re-add when you next modify the -host-acl entry.
95771 96543
The isi_gather_info utility fails to run on clusters running in compliance mode. This version of OneFS does not work with Symantec Backup Exec. See article 3834 in the Isilon Knowledge Base, "Symantec Backup Exec does not work with OneFS 7.0."
96545
If you are using the Comvault Simpana data management application (DMA), you cannot browse the backup if the data set has file names with non-ASCII characters. As a result, you cannot select single files to restore. Full restoration of the dataset is unaffected. Visiting the Events Summary or Events History pages when a large number of events are present on a cluster can cause the web administration interface to run out of memory. Restarting the web administration interface from the command line resets the memory held by that instance of the web administration interface. Workaround: Use the isi event command to configure and view events and event notifications.
96812
97024
A Collect job or the Collect portion of a MultiScan job may ultimately be canceled because of group changes. The job is listed as System Cancelled, not
Failed. This issue can be further identified by job error log entries such as
28
OneFS 7.0.1.5
Release notes
ID -
Description Ending lin mark (error ECANCELED) that are followed by numerous ENOENT and EOPRESTART errors.
Workaround: Manually restart the canceled job.
97492
With SyncIQ, a mirror policy on a target fails in the resync_prep_restore stage with a
Failed to move <file>; from <path_to_file> to tmp working directory: "Operation not permitted" error.
This error can occur when SyncIQ translates operations on the source cluster, such as moving a file or a directory, into the same operation on the target cluster. Multiple quota domains cannot span SyncIQ target subtrees. If the source cluster is used for failback, the failback operation could fail if multiple quota domains span SyncIQ source subtrees. If the source cluster is not used for failback, multiple quota domains can exist on the source.
This error might occur if a quota scan job has not finished by the time synchronization jobs are running.
97496 / 97533 The isi nfs nlm locks list and isi nfs nlm sessions list commands return information only about clients that connected to the node on which the command is run. To obtain information about all the clients across the cluster, you must run the commands in conjunction with the isi_for_array command. Find all file locks held by clients in the cluster by running the isi_for_array 'isi
nfs nlm locks list command.
Identify all the client session information on a cluster by running the isi_for_array
'isi nfs nlm sessions list' command.
97536
SyncIQ policies with source restrictions on subpools containing a mix of nodes using Gigabit Ethernet (GigE) and non-GigE interfaces fail with the following error:
SyncIQ error connecting to daemon (bandwidth, throttle, pworker). Please verify all SyncIQ daemons are running. Unable to connect to throttle host for last <x> seconds.
Workaround: Disable the source restriction from the policy, or assign the nodes that use GigE interfaces to the same pool. 97655 97735 Performing a rolling upgrade while a SyncIQ job is running with the --diff_sync option enabled can potentially cause a process to crash, although the job does not fail. Adding an Isilon vendor provider might fail when you enable VASA support. Additionally, the VASA information that appears in vCenter might be incorrect. These issues can occur if you create a data store or virtual machine through the VMware vSphere PowerCLI. To resolve this issue, create data stores through either the VMware vCenter graphical user interface or the VMware ESXi command-line interface. The OneFS upgrade process incorrectly reports upgrades that fail because of a degraded boot drive mirror. To check for a degraded boot drive mirror, review the cluster events history for any
98072
Unhealthy boot disks (<disk_id>), mirror is degraded

29
Release notes
ID -
Description
messages. If the cluster contains a degraded boot drive, contact Isilon Technical Support for information about replacing the boot drive. Cluster jobs that are running before a OneFS upgrade might not automatically restart after the upgrade completes. Workaround: Cancel all running jobs before upgrading. If existing jobs do not automatically restart, you can manually start them after you upgrade OneFS.
98341
98452
The isi version osreldate command does not return the expected OneFS release date. In earlier versions of OneFS, the web administration interface included settings to add domain groups to local groups. With the current web administration interface, you cannot add a domain group to a local group. Workaround: Use the command-line interface to add domain groups to local groups.
98607
99211 99383
If you revert a snapshot that contains a SmartLock directory, the operation might fail, leaving the directory partially reverted. The SyncIQ scheduler service uses UTF-8 encoding even if the cluster is set with a different encoding. Impact: DomainMark and SnapRevert jobs, which use cluster encoding, can fail to run.
99693 99951 99983
While the system restores an NDMP backup, it assigns insecure permissions to the top-level directory until the restore is complete. Verbose listings of user and directory quotas incorrectly display the amount of spaced used. When upgrading from 6.5.5.x to 7.0.x, iSCSI mounts may be lost. Workaround: Following the upgrade, perform the command isi_for_array killall -HUP isi_iscsi_d on every node in the cluster to reload the iSCSI configuration.
100042 100045 100272 100332 100365
If a Collect job is in a paused state when a cluster is upgraded from 6.5 to 7.0, the job is not canceled. NFS exports with unresolvable client host names cannot be created or modified from the WebUI. During a node chassis replacement, the new node sometimes receives an incorrect SKU. After change permission is granted on an SMB share, users or groups are still unable to delete files. When isi_vol_copy is run twice, with different source paths but the same target path, the second run fails without migrating any files. When migrating FIFO files, the isi_vol_copy utility displays the message Save
100366
checkpoint error: Could not match file history.

100412 After an upgrade from 6.5 to 7.0.1.1, creating a snapshot of a directory can cause /ifs to become read only.
30
OneFS 7.0.1.5
Release notes
ID -
Description
Workaround: Create a snapshot on a directory that has already been captured in a snapshot. Nodes that are connected to a network that supports Appletalk write kernel logging to /var/log/messages excessively. When data is written to files that reference invalid diskpool IDs, the log messages indicate that files are written at 1x protection when the actual protection level is 2x. A rolling upgrade from OneFS 7.0.0 to 7.0.1.0-7.0.1.2 results in an incorrect diskpool database version, which means new nodes cannot be added to diskpools. When upgrading from OneFS 6.5 to 7.0, some configuration values related to the NFS server's request pool are not carried over. The isi_vol_copy utility terminates when it encounters an unreadable inode in the data stream. If a SyncIQ policy's root directory is moved or removed during a running job, the job runs without completing until the directory is restored. When upgrading from 7.0.1.x to 7.0.1.4, SMB change permissions do not update on existing shares.
100489
100659 100671 100997 101077
101113 101967
Upgrading OneFS
By upgrading to the latest version of OneFS, you can take advantage of new features and enhancements. Before upgrading OneFS, review the system requirements to verify that the cluster can be upgraded directly to the latest version.
Download the OneFS installation image

Before updating the OneFS software, you must download the installation image. Procedure 1. Download the OneFS installation image from the EMC Support website. https://support.emc.com/downloads/15209_Isilon-OneFS 2. To verify that the download operation was successful: a. From the command line, type the following: md5 <OneFS-install-file-name> b. Click Checksum under the download link on the EMC Support website. c. Compare the checksum of the downloaded image against the MD5 checksum. 3. Open a secure shell (SSH) connection to any node in the cluster and log in using the root account. 4. Copy the installation files to the /ifs/data directory on the cluster.
Run the upgrade compatibility checks

Before upgrading OneFS, it is recommended that you confirm that the cluster is compatible with the newer OneFS version. OneFS provides a series of compatibility checks that you can run independent of an upgrade to verify that the cluster is healthy
Upgrading OneFS
31
Release notes
and does not contain settings or configurations that are incompatible with the new OneFS version. Before you begin Before you can run the compatibility checks, you must download the installation files for the OneFS version that you want to check for compatibility. Procedure 1. Open a secure shell (SSH) connection to any node in the cluster. 2. Run the isi version on the cluster.
osrelease command to view the OneFS version that is running
3. Optional: If the cluster is running OneFS 6.5.5.9 or earlier, you must install a patch before running the upgrade compatibility checks. Options OneFS 6.5.5.0 6.5.5.9 Description a. Download patch 96454 from the Isilon FTP site at ftp:// ftp.isilon.com/outgoing/patches/patch-96454.tgz. b. To install the patch, complete the steps in the README file that is included with the patch. a. Download patch 96453 from the Isilon FTP site at ftp:// ftp.isilon.com/outgoing/patches/patch-96453.tgz. b. To install the patch, complete the steps in the README file that is included with the patch. Other OneFS versions Contact Isilon Technical Support for information about running the upgrade compatibility checks.
OneFS 6.5.4
4. Start the compatibility checks by running the following command: isi update --check-only The command returns a list of warnings or errors if present, and then displays the following prompt: Please specify the image to update:
Although the prompt indicates that the image will be updated, because the --checkonly option is specified the command will only perform the pre-upgrade checks. 5. At the prompt, specify the image by typing the absolute path or URL to the image location. After you finish If the command returns errors, you must resolve the errors before proceeding with the upgrade. Warnings are informational and do not prevent an upgrade.
Upgrade OneFS through the web administration interface

You can upgrade the OneFS version that is running on a cluster through the web administration interface. Procedure 1. Log in to the cluster through the Isilon web administration interface with the root account. 2. Navigate to the Operations Summary page.
32
OneFS 7.0.1.5
Release notes
l l
For OneFS 6.5 or earlier, click Cluster > Operations > Summary . For OneFS 7.0 or later, click Cluster Management > Operations .
3. In the Running Jobs table, check for jobs that are running. 4. Optional: If jobs are running, complete one of the following actions to resolve the jobs before proceeding with the upgrade.
It is recommended that you wait for FlexProtect and FlexProtectLin jobs to complete before proceeding with the upgrade. Options Description
To wait for the running jobs No action is necessary. The amount of time it takes for to complete the jobs to complete varies by cluster size and configuration. To cancel the running jobs In the Running Jobs table, click Cancel for each running job.
5. Navigate to the Upgrade OneFS page. l For OneFS 6.5 or earlier, click Cluster > Cluster Management > Upgrade Summary .
l
For OneFS 7.0 or later, click Help > About This Cluster , and then click Upgrade.
6. Browse to the location of the installation image that you want to install, and then click Submit. 7. In the Upgrade Mode area, select one of the following upgrade modes, and then click Continue. Options Simultaneous upgrade Rolling upgrade Description Upgrades and restarts all the nodes in the cluster at the same time. While the nodes are restarting, the cluster is unavailable for client connections. Upgrades and restarts each node in the cluster sequentially so that clients can access the cluster during the upgrade. Rolling upgrades are unavailable for some OneFS versions. Review the system requirements for a list of versions that support rolling upgrades. The cluster displays status updates and a prompt to continue the upgrade process. 8. Optional: For rolling upgrades, specify how to terminate TCP client connections before upgrading the node. Options To immediately terminate client connections To terminate client connections after a wait period Description Click Immediately terminate TCP connections. a. Click Wait for TCP connections to terminate. b. In the Wait time field, type an integer that represents how long to wait in seconds, minutes, hours, days, weeks, or months.
Upgrade OneFS through the web administration interface
33
Release notes
9. Optional: For rolling upgrades, specify whether you want to confirm restarting each node during the upgrade process. Options Description
To display a notification and a prompt before each Click Confirm before rebooting node is restarted nodes. To automatically restart each upgraded node without a prompt 10.Click yes to begin the upgrade process. The cluster might display several confirmation messages that are related to the upgrade. You must confirm each message to continue the upgrade process. Once the upgrade is complete, the cluster restarts, and then the web administration interface login page appears. If the login page does not appear, clear your web browser cache and reload the page. Results After an upgrade, a number of upgrade-related jobs will continue to run for some time. During this time, the cluster is accessible, but you might experience a decrease in cluster performance. After the jobs complete, performance will return to normal. Click Reboot nodes without confirmation.
Upgrade OneFS through the command-line interface

You can upgrade the OneFS version that is running on a cluster through the commandline interface. Procedure 1. Open a secure shell (SSH) connection on any node in the cluster and log in to the cluster with the root account. 2. Check for any running jobs by running the following command:
isi job status
3. Optional: If jobs are running, complete one of the following steps to resolve the jobs before proceeding with the upgrade.
It is recommended that you wait for FlexProtect and FlexProtectLin jobs to complete before proceeding with the upgrade. Options To wait for the running jobs to complete To cancel the running jobs Description No action is necessary. The amount of time it takes for the jobs to complete varies by cluster size and configuration. Run the following command for each running job:
isi job cancel <job>
Replace <job> with either a job name or a job instance ID. 4. Choose one of the following options for upgrading OneFS. Rolling upgrades are not available for some OneFS versions. Review the system requirements for a list of versions that support rolling upgrades.
34
OneFS 7.0.1.5
Release notes
Options Simultaneous upgrade
Description To perform a simultaneous upgrade and restart all of the nodes in the cluster at the same time, run the following command:
isi update
The cluster prompts you to specify the location of the OneFS installation image that you downloaded. Rolling upgrade To perform a rolling upgrade, which upgrades and restarts each node in the cluster sequentially, run the following command:
isi update
--rolling
To specify a timeout period before each node is restarted, include the --drain-time option. This option is useful to allow time for TCP clients to disconnect from the cluster before the upgrade process restarts the node. The default timeout is zero seconds. To display a confirmation prompt before each node restarts, include the --manual option. Results After the upgrade, a number of upgrade-related jobs will continue to run for some time. During this time, the cluster is accessible, but you might experience a decrease in cluster performance. After the jobs complete, performance will return to normal.
Verify the OneFS installation

After you install OneFS, verify that the installation was successful. Procedure 1. Confirm that the health of all the nodes in the cluster is OK. isi stat 2. Remove the installation files from the /ifs/data directory. rm /ifs/data/onefs_v<OneFS-version>_install.tar.gz Replace <OneFS-version> with the four-digit OneFS version number. 3. Collect information about the cluster and send the log file to Isilon. isi_gather_info
Upgrade compatibility checks

Before upgrading OneFS, the upgrade process performs a number of system health and configuration checks to verify that the cluster is compatible with the new OneFS version. Compatibility errors must be resolved before upgrading the cluster. Check Disk load
Description Checks the cluster usage level and returns a warning if the disk load is greater than 50 percent. A disk load that is greater than 50 percent might indicate that multiple clients are using the cluster or that important system jobs are running. It is recommended that you wait until
Verify the OneFS installation
35
Release notes
Check -
Description
the cluster is not being heavily used to proceed with the upgrade. Checks the free space and returns either a warning or an error if certain capacity thresholds are exceeded for the following cluster partitions or node pools:
u
Free space
/ Returns a warning if the root partition is more than 97 percent full. The check returns an error when the partition reaches 100 percent full. /var
Returns a warning if the/var partition is more than 90 percent full. The check returns an error when the partition reaches 100 percent full.
/ifs Returns a warning if the /ifs partition is more than 95 percent full. The check returns an error when the partition reaches 100 percent full. Node pools
Returns a warning if one or more node pools are more than 90 percent full. The check returns an error when all the node pools reach 90 percent full.
If the check reports an error, reduce the size of the partition or node pool so that it is below the threshold before proceeding with the upgrade. Drive stalls Checks the health of the drives in the cluster and returns a warning if the cluster contains stalled drives. Before you proceed with the upgrade, stalled drives must be smartfailed and replaced, or the stall must be resolved. See KB article 3594 for information about resolving drive stalls. Smartfail operation status Checks whether the smartfail operation is running on any drives or nodes in the cluster. If there is a smartfail operation running, the check returns an error. Wait for the smartfail operation to complete before proceeding with the upgrade. Integrity scan job status Checks whether the integrity scan job is running. Wait for the job to complete before proceeding with the upgrade.
36
OneFS 7.0.1.5
Release notes
Check Outstanding critical events
Description Checks for the presence of critical events on the cluster. If there are critical events, complete the steps listed in the event details help to resolve the issues before proceeding with the upgrade.
Unsupported SMB configuration
Checks for deprecated SMB settings. Through the OneFS web administration interface, remove the unsupported settings before proceeding with the upgrade.
Legacy LDAP support enabled
Checks whether legacy LDAP support is enabled. Legacy LDAP support has been deprecated. Reconfigure the cluster to use the standard LDAP implementation before proceeding with the upgrade.
Unsupported SmartPools configuration
Checks for the presence of a deprecated SmartPools configuration. If the cluster contains a deprecated SmartPools configuration, reconfigure SmartPools to a supported configuration before proceeding with the upgrade. See the OneFS Administration Guide for information about the supported configurations for SmartPools.
Where to go for support

You can contact Isilon Technical Support for any questions about Isilon products. Online support Telephone support https://support.emc.com/ United States: 800-782-4362 (1-800-SVC-4EMC) Canada: 800-543-4782 Worldwide: +1-508-497-7901 For local phone numbers in your country, see EMC Customer Support Centers. To contact Isilon Technical Support: 1. Call EMC Customer Support at one of the telephone numbers listed above. 2. From the main menu, select Option 2 - All Hardware Products and then select Option 1 - All Hardware Products except AX. Help with online Questions specific to EMC Online Support registration, access, or site support association: support@emc.com
Where to go for support
37
Release notes
Pre-OneFS 7.0 command mapping

This section maps pre-OneFS 7.0 commands to OneFS 7.0 commands. For detailed descriptions of new commands, refer to the OneFS 7.0 Command Reference.
New authentication commands

The following table maps the syntax of pre-OneFS 7.0 isi auth commands to the isi auth commands that are used in OneFS 7.0. Old Command isi auth ads status
New Command isi auth ads list --verbose isi auth ads view <provider> -verbose
Notes The isi auth ads list command may display more than one Active Directory (AD) domain.
isi auth ads status --domains
isi auth ads trusts list <provider> isi auth ads trusts view <provider> <domain>
isi auth ads status --refresh isi auth ads join isi auth ads join --keep-accounts
isi auth refresh isi auth ads create <domain-name>
Now requires root privileges.
n/a
There is no equivalent command for this feature.
isi auth ads leave isi auth ads leave -workgroup=<workgroup> isi auth ads users list
isi auth ads delete <domain-name> isi auth settings global modify --workgroup <workgroup> isi auth users list --provider ads:<provider> <domain> isi auth users view <username> ads:<provider> isi auth groups list --provider ads:<provider> --domain <domain> isi auth groups view <group-name> --provider ads:<provider> isi auth ads trusts list <provider> isi auth ads trusts view <provider> <domain> isi auth ads view <provider> -verbose
isi auth ads users list -name=<username> --verbose isi auth ads groups list
Can also list by --sid and --uid.
isi auth ads groups list -name=<group-name> --verbose isi auth ads accounts list
Can also list by --sid and --gid.
isi auth ads accounts list -domain=<domain>
The combination of the new commands is the equivalent of the old command.
38
OneFS 7.0.1.5
Release notes
Old Command isi auth ads search
New Command isi auth users list
Notes Search functionality is currently not supported.
or
isi auth groups list isi auth ads spn isi auth ads dc --domain=<domain> --list isi auth ads dc --domain=<domain> --set-dc=<domain> isi auth ads dc --domain=<domain> --reset-schannel isi auth ads dc --domain=<domain> --site=<site> isi auth ads dc --domain=<domain> --verbose isi auth ads time isi auth ads time --sync isi auth ads spn isi auth ads trusts controllers list <provider> --verbose isi auth ads modify <provider> -domain-controller <domain> isi auth ads modify <provider> -reset-schannel yes isi auth ads trusts view <provider> <domain> isi auth ads view <provider> -verbose isi auth ads view <provider>
Querying for sites is not supported.
n/a
There is no equivalent command for this feature. The following parameters have no equivalent: --user, --group, --uid, or --gid.
isi auth ads cache flush
isi auth users flush
or
isi auth groups flush isi auth local {users | groups} <action> isi auth local <action>
isi auth local now manages the local
providers. See isi auth users and isi

auth groups for user and group
management.
isi auth local users isi auth local users create <name> isi auth local users new <name> isi auth local users modify <persona> isi auth users modify {<name> | <persona>} isi auth users isi auth users create <name>
New users are created under the local provider for the current access zone. Some parameters were renamed. Name or persona parameters are resolved under the local provider for the current access zone. Some parameters were renamed. Name or persona parameters are resolved under the local provider for the current access zone.
isi auth local users delete <persona>
isi auth users delete {<name> | <persona>}
39
Release notes
Old Command isi auth local users list
New Command isi auth users list
Notes The list is only of the users within the local provider for the current access zone. Specify a provider to list users that are not within the local provider. Optionally, specify an access zone to list users under a provider outside of the current zone or specify a domain and a provider to list Active Directory users.
isi auth local users list -remote
isi auth users list --provider <provider>
isi auth local users list <persona> isi auth local users list <persona> --remote
isi auth users view <persona>
isi auth users view <persona> -provider <provider>
Specify a provider to view a user that is not within the local provider. Optionally, specify an access zone to view a user under a provider outside of the current zone or specify a domain and a provider to view an Active Directory user.
isi auth local groups isi auth local groups create <name> isi auth local groups new <name> isi auth local groups modify <persona> --remote
isi auth groups isi auth groups create <name>
New groups are created under the local provider for the current access zone. Some parameters were renamed. Name or persona parameters are resolved under the local provider for the current access zone. Some parameters were renamed. Name or persona parameters are resolved under the local provider for the current access zone. The list includes only the groups within the local provider for the current access zone. Specify a provider to list groups that are not within the local provider. Optionally, specify an access zone to list groups under a provider outside of the current zone or specify a domain and a provider to list Active Directory groups.
isi auth groups modify {<name> | <persona>}
isi auth local groups delete <persona>
isi auth groups delete {<name> | <persona>}
isi auth local groups list
isi auth groups list
isi auth local groups list -remote
isi auth groups list --provider <provider>
isi auth local groups list <persona> isi auth local groups list <persona> --remote
isi auth groups view <persona>
isi auth groups view <persona> -provider <provider>
Specify a provider to view a group that is not within the local provider. Optionally, specify an access zone to view a group under a provider outside of the current
40
OneFS 7.0.1.5
Release notes
Old Command -
New Command -
Notes
zone or specify a domain and a provider to view an Active Directory group.
isi auth status -provider=<provider> isi auth status --refresh isi auth mapping new isi auth mapping create isi auth mapping modify isi auth mapping set isi auth mapping delete isi auth mapping flush isi auth mapping list isi auth mapping token -name=<name> isi auth mapping idrange isi auth mapping dump isi auth mapping import isi auth mapping upgrade-db isi auth config
isi auth {ads | file | ldap | local | nis} view <provider> isi auth refresh isi auth mapping new
Now requires root privileges. Now requires root privileges.
isi auth mapping modify
isi auth mapping delete isi auth mapping flush isi auth mapping list isi auth mapping token {<name> | <persona>} isi auth mapping idrange isi auth mapping dump isi auth mapping import isi auth mapping upgrade-db isi auth settings
Now requires root privileges. Now requires root privileges. Now requires root privileges. Some parameters were removed.
Now requires root privileges. Now requires root privileges. Now requires root privileges. Now requires root privileges. Some sub-commands were moved or renamed. Output is now divided into global values and provider-specific values.
isi auth config list
isi auth settings global view isi auth {ads | file | ldap | local | nis} view <provider>
isi auth config modify
isi auth settings global modify isi auth {ads | file | ldap | local | nis} modify <provider>
Configuration parameters were split into global parameters and provider-specific parameters.
isi auth config rules --list isi auth config rules --readline=<string>
isi zone zones view <zone> isi zone zones modify <zone> -user-mapping-rules
User mapping rules are configured with list management parameters (add/ remove/clear).
isi auth config rules --revert
isi zone zones modify <zone> -clear-user-mapping-rules
41
Release notes
Old Command isi auth config rules --readfile=<string> isi auth config krb5 isi auth config ldap list isi auth config ldap modify isi auth error isi auth log-level
New Command n/a
Notes There is no equivalent command for this feature. Now requires root privileges.
isi auth krb5 isi auth ldap view <provider> isi auth ldap modify <provider> isi auth error isi auth log-level
Some parameters were renamed. Now requires root privileges. Now requires root privileges.
New NFS commands

The following table maps the syntax of pre-OneFS 7.0 isi nfs commands to isi nfs commands used in OneFS version 7.0. Old Command isi nfs exports list <id> -verbose isi nfs exports list --sitedefault --verbose isi nfs exports {checks | verify} isi nfs exports {create | new} isi nfs exports {modify |change} <id>
New Command isi nfs exports view <id>
Notes -
isi nfs settings export view
isi nfs exports check isi nfs exports create <paths> isi nfs exports modify <id>
Some parameters were renamed. Some parameters were renamed. All -default-* parameters were renamed and are now --revert-* parameters. Some parameters were renamed. All -default-* parameters were renamed and are now --revert-* parameters.
isi nfs exports {modify | change} --site-default
isi nfs settings export modify
isi nfs exports {delete | remove} <id> isi nfs exports {reload | refresh} isi nfs locks isi nfs locks list -client=<client> --file=<file> -lin=<lin> --age=<age> isi nfs locks waiters
isi nfs exports delete <id>
isi nfs exports reload
isi nfs nlm locks isi nfs nlm locks list --sort {client | path | lock_type | range | created} isi nfs nlm locks waiters
Parameters for filtering a list were replaced with parameters for sorting a list.
42
OneFS 7.0.1.5
Release notes
Old Command isi nfs clients isi nfs clients list isi nfs clients remove <client>
New Command isi nfs nlm sessions isi nfs nlm sessions list isi nfs nlm sessions disconnect <client> isi nfs settings global modify -lock-protection <int> isi nfs netgroup
Notes -
isi nfs flexprotect --set=<int>
isi nfs netgroup
New quota commands

The following table maps the syntax of pre-OneFS 7.0 isi quotas commands to isi
quotas commands used in OneFS version 7.0.
Old Command isi quota {create | new}
New Command isi quota quotas create <path> <type>
Notes --path <path> is now the first argument. The --directory parameter is now the directory option for the second argument. --specific-user=<user> is now user for the second argument, with a user persona parameter of user, uid, wellknown, or sid. --specific-group=<group> is now group for the second argument, with a group persona parameter of group, gid, or sid. Specify the <zone> parameter for the persona resolution. The --default-user parameter is now the default-user option for the second argument. The --default-group parameter is now the default-group option for the second argument. --snaps=<boolean> is now the --include-snapshots <boolean>. The --include-overhead parameter is now the -thresholds-include-overhead parameter set to yes. The --include-no-overhead parameter is now the -thresholds-include-overhead parameter set to no. The --enforcement parameter is now the --enforced parameter set to yes. The --accounting parameter is now the --enforced parameter set to no. The parameters <hard-threshold>, <advisory-threshold>, <soft-threshold>, <soft-grace>, and <container> are unchanged.
New quota commands
43
Release notes
Old Command -
New Command -
Notes
For quota notifications parameters, see isi quota quotas notifications create. All --notify-* parameters on isi quota create were replaced with isi quota quotas notifications create instead.
isi quota {create | new} -notify-for-{hard | soft | advisory}-threshold -notify-while-over=<schedule> --notify-whileexpired=<schedule> --notifywhile-over-notexpired=<schedule> --notifyon-threshold-exceeded-onceper=<duration> --notify-ondenied-write-onceper=<duration> --notifyalert --notify-email-toowner --notify-emailto=<email> isi quota modify
isi quota quotas notifications create <path> <type> <threshold> <condition>
isi quota quotas modify <path> <type>
--path <path> is now the first argument. The --directory parameter is now the directory option for the second argument. --specific-user=<user> is now user for the second argument, with a user persona parameter of user, uid, wellknown, or sid. --specific-group=<group> is now group for the second argument, with a group persona parameter of group, gid, or sid. Specify the <zone> parameter for the persona resolution. The --default-user parameter is now the default-user option for the second argument. The --default-group parameter is now the default-group option for the second argument. --snaps=<boolean> is now the --include-snapshots
<boolean>.
The --include-overhead parameter is now the -thresholds-include-overhead parameter set to yes. The --include-no-overhead parameter is now the -thresholds-include-overhead parameter set to no. The --enforcement parameter is now the --enforced parameter set to yes. The --accounting parameter is now the --enforced parameter set to no. The --unlink-from-default parameter is now the --linked parameter set to no. The --link-to-default parameter is now the --linked parameter set to yes.
44
OneFS 7.0.1.5
Release notes
Old Command -
New Command -
Notes
The parameters <hard-threshold>, <advisory-threshold>, <soft-threshold>, <soft-grace>, <container>, <clear-hardthreshold>, <clear-soft-threshold>, and <clear-advisorythreshold> are unchanged. For quota notifications parameters, see isi quota quotas notifications modify.
isi quota modify --notifyfor-{hard | soft | advisory}-threshold -notify-while-over=<schedule> --notify-whileexpired=<schedule> --notifywhile-over-notexpired=<schedule> --notifyon-threshold-exceeded-onceper=<duration> --notify-ondenied-write-onceper=<duration> --notifyalert --notify-email-toowner --notify-emailto=<email> isi quota modify --clearnotify-{hard | soft | advisory}-threshold
isi quota quotas notifications modify <path> <type> <threshold> <condition>
All --notify-* parameters on isi quota modify were replaced with isi quota quotas notifications modify.
isi quota quotas notifications delete <path> <type> <threshold> <condition> isi quota quotas notifications clear <path> <type> <threshold> <condition> isi quota quotas notifications disable <path> <type> <threshold> <condition> isi quota settings notifications create <threshold> <condition> <schedule> <holdoff> isi quota settings notifications modify <threshold> <condition> <schedule> <holdoff>
isi quota modify --restorenotify-to-global-defaults
isi quota modify --resetnotify-state
isi quota modify --globalnotify --notify-for-{hard | soft | advisory}-threshold --notify-whileover=<schedule> --notifywhile-expired=<schedule> -notify-while-over-notexpired=<schedule> --notifyon-threshold-exceeded-onceper=<duration> --notify-ondenied-write-onceper=<duration> --notifyalert --notify-email-to-
All global notification settings are now handled through isi quota settings notifications.
New quota commands
45
Release notes
Old Command owner --notify-emailto=<email> isi quota modify --globalnotify --clear-notify-{hard | soft | advisory}-threshold
New Command -
Notes
isi quota settings notifications clear isi quota settings notifications delete <threshold> <condition> isi quota quotas delete <path> --type <type>
All global notification settings are now handled through isi quota settings notifications.
isi quota {delete | remove}
--recurse-path-up=<path> is now --path <path> -recurse-path-parents. --recurse-path=<path> is now --path <path> --recursepath-children. --snaps=<boolean> is now --include-snapshots <boolean>. The --directory parameter is now --type directory. --specific-user=<user> is now --type <user>, with a user persona parameter of user, uid, wellknown, or sid. --specific-group=<group> is now --type group, with a group persona parameter of group, gid, or sid. Specify the <zone> parameter for persona resolution. The --default-user parameter is now --type default-user. The --default-group parameter is now --type defaultgroup. All other parameters were removed.
or
isi quota quotas delete -all
isi quota reporting isi quota reporting show
isi quota reports isi quota settings reports view isi quota settings reports modify
isi quota reporting set
Some parameters were renamed. --revert-*parameters were added to reset values back to factory defaults.
isi quota reporting stopreports isi quota reporting {makeon-demand | make-ad-hoc} isi quota import
isi quota settings reports modify --schedule never isi quota reports create
n/a
There are no equivalent commands for this feature.
46
OneFS 7.0.1.5
Release notes
New SMB commands

The following table maps the syntax of pre-OneFS 7.0 isi smb commands to isi smb commands used in OneFS version 7.0. Old Command isi smb share isi smb share list isi smb share list -sharename=<sharename>
New Command isi smb shares isi smb shares list isi smb shares list isi smb shares view <sharename> isi smb shares create <sharename> <path>
Notes -
The functionality of the isi smb config share list <sharename> parameter is supplied with these new commands. The --comment option was renamed to --description. The <sharename> parameters from the isi smb config share modify command were moved to the new command. The --comment option was renamed to --description. The <sharename> parameters from the isi smb config share modify command were moved to the new command.
isi smb share create -sharename=<sharename> -path=<path>
isi smb share modify -sharename=<sharename>
isi smb shares modify <sharename>
isi smb share delete -sharename=<sharename> isi smb permission isi smb permission list -sharename=<sharename>
isi smb shares delete <sharename> isi smb shares permission isi smb shares permission list <sharename>
The <zone> parameter was added to resolve personas. The command now requires the <sharename> parameter. The <account-name> and <account-type> parameters were removed in favor of the persona parameters <user>, <group>, <wellknown>, <uid>, and <gid>. The <zone> parameter was added to resolve personas. The <run-as-root> parameter is now a separate parameter from the <permission-type> parameter values. The <account-name> and <account-type> parameters were removed in favor of the persona parameters <user>, <group>, <wellknown>, <uid>, and <gid>. The <zone> parameter was added to resolve personas. The <run-as-root> parameter is now a separate parameter from the values for the <permission-type> parameter. The <account-name> and <account-type> parameters were removed in favor of the persona parameters <user>, <group>, <wellknown>, <uid>, and <gid>. The <zone> parameter was added to resolve personas. The <force> parameter enables you to delete files without confirmation and is now a separate parameter from the
isi smb permission create -sharename=<sharename>
isi smb shares permission create <sharename> <username | persona>
isi smb permission modify -sharename=<sharename>
isi smb shares permission modify <sharename> <username | persona>
isi smb permission delete -sharename=<sharename>
isi smb shares permission delete <sharename> <username | persona>
New SMB commands
47
Release notes
Old Command -
New Command -
Notes
values for the <permission-type> parameter. The following parameters were removed with no equivalent commands provided in OneFS 7.0: <permission-type>, <permission>, and <all>.
isi smb config isi smb config global isi smb config global list
isi smb settings isi smb settings global isi smb settings global view
All filtering parameters were removed, with no equivalent commands provided in OneFS 7.0. The <security-mode> parameter was removed. See isi
smb config global modify. The --revert-*
isi smb config global modify
isi smb settings global modify
parameters were added to supply isi smb config

global revert functionality. isi smb config global modify --security-mode=<mode> isi smb settings shares modify --impersonate-guest <enum> isi smb settings global modify [--revert-* parameters...] isi smb settings shares modify --revert-impersonateguest isi smb settings shares isi smb settings shares view
You may also have to enable the guest user under the local provider for a zone.
isi smb config global revert
isi smb config global revert --security-mode
You may also have to disable the guest user under the local provider for a zone. You can do this with the isi auth users modify command.
isi smb config share isi smb config share list
All filtering parameters were removed, with no equivalent commands provided in OneFS 7.0.
isi smb config share list -sharename=<sharename> isi smb config share modify
isi smb shares view <sharename> isi smb settings shares modify
The <mangle-map> and <host-acl> parameters have additional add, remove, and clear parameters. The -revert-* parameters were added to supply functionality for isi smb config share revert.
isi smb config share modify --sharename=<sharename> isi smb config share revert
isi smb shares modify <sharename> isi smb settings shares modify [--revert-* parameters...] isi smb shares modify <sharename> [--revert-* parameters...]
isi smb config share revert --sharename=<sharename>
48
OneFS 7.0.1.5
Release notes
Old Command isi smb session isi smb session list
New Command isi smb sessions isi smb sessions list
Notes The <computer-name> filtering parameter was removed, with no equivalent commands provided in OneFS 7.0. The <user-name> parameter was removed in favor of the user persona parameters <user>, <uid>, and <sid>.
isi smb session delete
isi smb sessions delete <computer-name> isi smb sessions delete-user <username | persona>
isi smb file isi smb file list
isi smb openfiles isi smb openfiles list
The <file-id> filtering parameter was removed, with no equivalent commands provided in OneFS 7.0. You can supply the <force> parameter to close a file without confirmation. Now requires root privileges.
isi smb file close --fileid=<file-id> isi smb log-level
isi smb file close <file-id>
isi smb log-level
New snapshot commands

The following table maps the syntax of pre-OneFS 7.0 isi snapshot commands to isi
snapshot commands used in OneFS version 7.0.
Old Command isi snapshot {create | add} <name> <path>
New Command isi snapshot snapshots create <name> <path>
Notes Some parameters were renamed. The <duration> parameter was replaced with the <expires> parameter and a timestamp. Some parameters were renamed. The <duration> parameter was replaced with the <expires> parameter and a timestamp.
isi snapshot {modify | change} <snapshot>
isi snapshot snapshots modify <snapshot>
isi snapshot {rename | move} <snapshot> <new-name>
isi snapshot snapshots modify <snapshot> --name <new-name> isi snapshot snapshots delete <snapshot> isi snapshot snapshots list
isi snapshot {delete | remove} <snapshot> isi snapshot list
The <showid>, <long>, <schedule>, <expiration> parameters were removed. The --format list parameter can be used to generate output in table (default), JavaScript Object Notation (JSON), comma-separated value (CSV), or list format.
isi snapshot usage
isi snapshot snapshots list --format table --verbose
isi snapshot alias <snapshot> <alias>
isi snapshot snapshots modify <snapshot> --alias <alias>
49
Release notes
Old Command isi snapshot schedule isi snapshot schedule list
New Command isi snapshot schedules isi snapshot schedules list
Notes The <schedule> (positional or specified as a parameter) and <long> parameters were removed. Some parameters were renamed. Some parameter values are of a different type. Positional arguments were rearranged. The <expiration> parameter was removed.
isi snapshot schedule {todo | pending} isi snapshot schedule {create | add} <name> <schedule> <pattern> <path> isi snapshot schedule {modify | change} <schedulename> isi snapshot schedule {delete | remove} <schedulename> isi snapshot schedule {rename | move} <schedulename> <new-name> isi snapshot lock isi snapshot lock list <snapshot> isi snapshot lock {create | add} <snapshot> isi snapshot lock {modify | change} <snapshot> <id> isi snapshot lock {delete | remove} <snapshot> <id> isi snapshot enable
isi snapshot schedules pending list isi snapshot schedules create <name> <path> <pattern> <schedule> isi snapshot schedules modify <schedule-name>
Some parameters were renamed. The <expiration> parameter was replaced with the <duration> parameter.
isi snapshot schedules delete <schedule-name>
Specify the --force option to delete the snapshot schedule without a confirmation prompt.
isi snapshot schedules modify <schedule-name> -name <new-name> isi snapshot locks isi snapshot locks list <snapshot> isi snapshot locks create <snapshot> isi snapshot locks modify <snapshot> <id> isi snapshot locks delete <snapshot> <id> isi snapshot settings modify --service on --autocreate on --autodelete on isi snapshot settings modify --service off --autocreate off --autodelete off isi snapshot settings isi snapshot settings isi snapshot settings
Some parameters have been renamed. <duration> parameter has been removed. Use <expires> instead. The <duration> parameter was replaced with the <expires> parameter. Specify the --force option to delete a snapshot lock without a confirmation prompt.
isi snapshot disable
isi snapshot autocreate isi snapshot autodelete isi snapshot reserve
50
OneFS 7.0.1.5
Release notes
Old Command isi snapshot settings list <name> isi snapshot settings set <name> <value>
New Command isi snapshot settings view
Notes The <name> parameter was removed.
isi snapshot settings modify
The <name> and <value> positional arguments were replaced with parameters for each item.
51
Release notes
Copyright 2001-2013 EMC Corporation. All rights reserved. Published in USA. Published April, 2013 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners. For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com). For documentation on EMC Data Domain products, go to the EMC Data Domain Support Portal (https://my.datadomain.com).
52
OneFS 7.0.1.5

OneFS 7.0.1.5 Release Notes

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

OneFS 7.0.1.5 Release Notes

Încărcat de

Drepturi de autor:

Formate disponibile

Isilon OneFS

Release number 7.0.1.5

New features and changes

New in OneFS 7.0.1.5

Support for Smart Modular boot drives

Support for Mars-K Plus ACO firmware

Support for Seagate Megalodon hard drive

Support for Western Digital boot drives

New in OneFS 7.0.1.4

New in OneFS 7.0.1.3

Disconnected battery detection

Support for Cobra-E drive firmware

Support for Seagate Manta Ray firmware

Antivirus scan enhancement

Bash shell upgrade

New in OneFS 7.0.1.2

Onsite Verification Test (OVT) Support

New in OneFS 7.0.1.1

New in OneFS 7.0.1

Microsoft Windows 8 support

New in OneFS 7.0

New in OneFS 7.0.1.1

Automatic provisioning and SmartPools

SyncIQ automated failover and failback

VMware API integration

OneFS command-line interface

OneFS web administration interface

Telnet_d support removed

New in OneFS 7.0

Environment and system requirements

Supported Isilon nodes

IQ 1920X IQ 3000X IQ 6000X EX 6000 IQ 9000X EX 9000 IQ 12000X

Version OneFS 7.0 OneFS 7.0.1

Simultaneous upgrade Yes Yes

Rolling upgrade Yes Yes

Resolved issues in OneFS 7.0.1.5

positional arguments for function call.

101292 101783 101905 101910 101938

102557 102583 102650 102657

102790 102794 102825 102912 102914 103000 103024

103137 103260 103262

Resolved issues in OneFS 7.0.1.5

Resolved issues in OneFS 7.0.1.4

100434 100559 100765

101117 101170 101206 101299 101300 101397 101430

Resolved issues in OneFS 7.0.1.4

Resolved issues in OneFS 7.0.1.3

97399 97817 98093

Resolved issues in OneFS 7.0.1.3

100248 100252 100267

many links when the source file had at

Resolved issues in OneFS 7.0.1.2

Resolved issues in OneFS 7.0.1.2

99758 99789 99790

Resolved issues in OneFS 7.0.1.1

Resolved issues in OneFS 7.0.1.1

Resolved issues in OneFS 7.0.1

98969 98987 99073

99132 99162 99186 99219

Resolved issues in OneFS 7.0

70943 72319 72339 / 92140 72410 72709 72871 75103 76009

77017 77917 78183

Resolved issues in OneFS 7.0

ID 79740 79809 80083 80860 81189