OneFS 7.0.1.5 Release Notes

7/22/2019 OneFS 7.0.1.5 Release Notes

1/52

Isilon

OneFSRelease number 7.0.1.5

Release notes

April, 2013

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


2/52

New features and changesThis 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, andchanges 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.

u Support for Mars-K Plus ACO firmware Adds support for Mars-K Plus ACO disk firmware.

u Support for Seagate Megalodon hard drive Adds support for Seagate Megalodon 4 TB drive firmware.

u 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 theprevious release of OneFS.


This version of Isilon OneFS includes the following new features and enhancements, andchanges to functionality that was present in earlier versions of OneFS.

u Disconnected battery detection

Node batteries that disconnect during shipping are detected.

u Support for Cobra-E drive firmware Adds support for version A350 of the Cobra-E drive firmware.

u Support for Seagate Manta Ray firmware Adds support for Seagate Manta Ray 3 TB drive firmware.

u Antivirus scan enhancement Antivirus policy scans open files with less impact to the system.

u Bash shell upgrade The bash shell is upgraded from version 3.3.39 to version 4.1.

New in OneFS 7.0.1.2This version of Isilon OneFS includes the following new features and enhancements, andchanges to functionality that was present in earlier versions of OneFS.

u Onsite Verification Test (OVT) Support Adds OVT support for firmware included in Isilon Firmware Package 8.2.

Release notes

2 OneFS7.0.1.5


3/52


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

New in OneFS 7.0.1


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

u Microsoft Windows 8 support Reintroduces support for clients running Microsoft Windows 8.

u 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.

u 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 non-

root 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 webadministration 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.

u 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

New in OneFS 7.0.1.1 3


4/52

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.

u 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.

u 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.

u Fast upgrade Major OneFS upgrades and reboots finish in significantly less time than in earlier versions,

regardless of cluster size and composition.

u 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.

u 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.

u 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.

u 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.

u 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.

u 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 runningisi_classic commands. For example, the

following command is valid in OneFS 7.0:

isi_classic snapshot create newSnap /ifs/data/media

Release notes

4 OneFS7.0.1.5


5/52

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.

u 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.

u SMB 2.1 OneFS delivers improved SMB performance and reliability through its support for client oplocks

and leases, and large (1 MB) MTU sizes.

u NFS OneFS provides single-node lookup for streamlined initial verification and mounting, improved

netgroup performance, and enhanced handling of stale exports.

u 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.

u 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.

u 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 spaceassociated with a shadow store. The SnapRevert job replaces the contents of a directory with

the data stored in a snapshot.

u 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.

u 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.

u 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.

Release notes

New in OneFS 7.0 5


6/52

SmartPools changes

The design of SmartPools is different from earlier versions and may require changes tothe 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.

u Simplify the configuration, management, monitoring, and performance optimizationof the cluster.

u Increase performance for network-based I/O for data files in the single largecontainer.

As a result, the following changes were made to SmartPools in this version of OneFS:

u This version of OneFS includes two new types of logical storage pools: node poolsand 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 usedas 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 nodetypes, see "OneFS 7.0 Node Provisioning Equivalences" in the Isilon Supportabilityand Compatibility Guide.

u Disk pools can no longer be viewed or targeted directly through the webadministration interface or the command-line interface; disk pools are managedexclusively by the system through autoprovisioning. Autoprovisioning is the processthrough which the system automatically assigns nodes to node pools and drives todisk pools, replacing manual disk pool creation and management. For moreinformation, see the OneFS Administration Guide.

u To avoid overloading node pools with SSDs, certain thresholds must be satisfied for

global namespace acceleration to be enabled. Global namespace acceleration can beenabled 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 least2.0% of the total cluster storage is SSD-based before enabling global namespaceacceleration.

Environment and system requirementsBefore installing OneFS, verify that your cluster and operating environment meet theminimum system requirements.

Supported Isilon nodes

OneFS runs only on supported Isilon hardware platforms.

This version of OneFS supports the following hardware platforms:

u IQ 1920X

u IQ 3000X

u IQ 6000X

u EX 6000

u IQ 9000X

u EX 9000

u

IQ 12000X

Release notes

6 OneFS7.0.1.5


7/52

u EX 12000

u IQ 10000X-SSD

u IQ 32000X-SSD

u IQ 36000X

u

IQ 5400Su IQ 5000S-SSD

u IQ 72000X

u IQ 108000X

u IQ 36NL

u IQ 72NL

u IQ 108NL

u Backup Accelerator

u IQ Accelerator

u IQ Accelerator-X

u X200

u S200

u X400

u NL400

Upgrade compatibility

Upgrades are available only between supported OneFS versions. If the cluster is notrunning a supported version of OneFS, contact Isilon Technical Support before attempting

an upgrade.Upgrades are supported for the following OneFS versions.

Version Simultaneous upgrade Rolling upgrade

- - -OneFS 6.0 Yes No

OneFS 6.0.1 Yes No

OneFS 6.0.2 Yes No

OneFS 6.0.3 Yes No

OneFS 6.0.4 Yes No

OneFS 6.0.5 Yes No

OneFS 6.5.0 Yes No

OneFS 6.5.1 Yes No

OneFS 6.5.2 Yes No

OneFS 6.5.3 Yes No

OneFS 6.5.4 Yes No

OneFS 6.5.5 Yes No

Release notes

Upgrade compatibility 7


8/52

Version Simultaneous upgrade Rolling upgrade

- - -OneFS 7.0 Yes Yes

OneFS 7.0.1 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 Version

- -Microsoft Internet Explorer 8 and 9

Mozilla Firefox Latest stable version

Google Chrome Latest stable version

Apple Safari 5.1.x and 6 on Mac OS X

Resolved issuesThis 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 Description

- -98041 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.

100489 Nodes connected to a network that supported Appletalk wrote kernel logging

to /var/log/message every forty seconds.

101203 The isi hdfs commands failed to read the encoded configuration file, which

resulted in a Corrupted configuration error.

101292 The Flexprotect drive scan phase performed more write operations than wereneeded, which resulted in longer job runtime.

101783 Onsite Verification Test (OVT) failed if a motherboard had a twelve-digit serial

number.

101905 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.

101910 The SMB service became unavailable and generated a core file when a zero-

copy write operation unsuccessfully executed.

101938 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.

Release notes

8 OneFS7.0.1.5


9/52

ID Description- -102018

102020

SMB workflows that relied on a large number of SMB change notifications

experienced client disconnections and service restarts.

102139 The timeout value for disk drives was equal to the lock timeout used for multi-

node operations, which resulted in a multi-node reboot event when a drivebecame unresponsive on a single node.

102309 Could not add decimal values for quotas through the web interface.

102467 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.

102479 When attempting to view Smartpools, the web interface crashed during

license verification.

102482 NFS configuration options that were available only in the CLI displayed

inaccurately in the web interface and resulted in inconsistent handling of

unresolvable clients.

102557 When attempting to view Smartpools, the web interface failed to load after

referencing a target pool policy that did not exist.

102583 The isi_vol_copy utility applied incorrect ACLs to migrated alternate data

streams.

102650 The output of the isi status command displayed an inaccurate Virtual

HotSpare (VHS) size due to calculation errors.

102657 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.

102790 All NFS connections were considered root clients and were given root

privileges.

102794 The SMB auditing function did not log delete operations.

102825 Following an upgrade from OneFS 6.5.5 to 7.0, SMB configuration contained

incompatible values related to client credit allocation.

102912 OneFS disabled a SyncIQ policy after several failed attempts to run the policy.

102914 After a cluster was added to the list of trusted sites in Internet Explorer, error

messages continued to appear.

103000 Memory consumed by the SMB server service increased over several days and

resulted in a node reboot due to memory exhaustion.

103024 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.

103137 HDFS 2 clients could not connect to the cluster.

103260 If a FlexProtectLin job was running for a smartfailed drive when a second drive

failed, data on the second drive was not repaired.

103262 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.

Release notes

Resolved issues in OneFS 7.0.1.5 9


10/52

ID Description- -103372 Memory consumed by the SMB server service increased over several days and

resulted in a restart of the service due to memory exhaustion.



ID Description

- -97669 If a quota is added while the QuotaScan job is

running, the new quota is prematurely marked

as ready.

99153 Clusters in compliance mode only allowed the

Onsite Verification Test (OVT) to run with the --

local option.

99382 If the cluster filesystem encoding was set to a

value other than UTF8, the DomainMark and

SnapRevert jobs failed.

100328 Following a failed battery test and node restart,

batteries were not immediately tested.

100332 Changing permissions on an SMB share did not

grant the user or group permissions for delete

or rename.

100399 Incorrect lock request responses from the

OneFS iSCSI service led to unexpected behaviorin connections from ESX clients.

100434 Support IQ did not deliver a weekly status

update.

100559 Quotas were unable to be associated with

custom email templates from the CLI.

100765 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.

100860 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.

100944 From the web interface, the LDAP configuration

page incorrectly specified that an LDAP server

must be entered as an IP or hostname.

100964 The LWIO daemon crashed and wrote a core file

during node shutdown.

Release notes

10 OneFS7.0.1.5


11/52

ID Description

- -101032 You could not clone the most recent version of

a file.

101053 When searching for open files with psfile tools,

the LWIO daemon restartsed and caused anerror.

101055 The NetBIOS Name Service (NBNS) did not start

after being enabled.

101077 The isi_vol_copy utility terminated after

encountering an unreadable inode in the data

stream.

101117 A user account was unable to log in with SSH if

the account was mapped to a different UID.

101170 The isi_vol_copy utility did not support themigration of special character files.

101206 A node was placed in a read-only state after a

single failed battery test.

101299 Running DomainMark on an invalid path

produced an unhandled error.

101300 DomainMark and SnapRevert did not run

without a SyncIQ license activated.

101397 A node panic occurred after a drive failed

during the MediaScan job.

101430 A high SMB1 connection load caused the SMB

service to write a core file when generating a

session response code.

101546 When working on a wide directory, SyncIQ

returned the errorFailed to delete

user attribute.

101566 A timing error allowed SMB locks to be taken

out of order, which resulted in a node becoming

unresponsive.

101588 Users were unable to log in with SSH when aprocess held an exclusive lock on /ifs.

101783 The Onsite Verification Test (OVT) did not

support a 12-digit serial number on new

motherboards.

Release notes



12/52



ID Description

- -86647 NDMP restore failed if the requested file list

contained an empty path. Empty paths occur

when a restore of an entire backup is needed.

87699 During an incremental backup, directories

leading to backed up files were not backed up.

89123 Email addresses were not pulled from Active

Directory domains by lsass NIS providers, which

resulted in incorrect email addresses populated

in quota notifications.

92272 Invalid NDMP user names for authenticationcaused the NDMP server to crash.

92491 NDMP backups included a copy of an ADS file

for the associated file and any hard links to that

file.

94132 If a root user typed the su command to mimic a

local user, that local user retained the

permission level of the root user.

94396 Backed up WORM data created duplicate calls

to rebuild header information, which consumed

additional tape space and CPU cycles.

94838 Incremental NDMP backups backed up a file as

a hardlink if hardlinks pointed to the file.

96111 If a file with the immutable bit set was included

in a SyncIQ policy, the policy failed because the

file could not be modified.

97399 SMB I/O file operations updated the "last

modified" timestamp.

97817 Partial adds of a netgroup timed out.

98093 An NFS client released all of its locksapproximately 45 seconds before a node-

caused group change, which resulted in failures

ofnfs.lockd to respond to requests.

99154 A cluster in compliance mode could not install

firmware or userspace patches.

99247 NDMP restore failed if the directory path was

longer than 1024 characters.

Release notes

12 OneFS7.0.1.5


13/52


14/52

ID Description

- -100158 When Node 1 of a source cluster was not

reachable by all nodes through the external

interface, SyncIQ jobs failed.

100240 SMB share ACL entries added from thecommand line were placed above the last entry,

instead of becoming the last entry.

100248 The host-acl option for SMB shares did not

support subnets for the allow and deny options.

100252 The SMB server allowed multiple clients to

modify a file simultaneously.

100267 Before an upgrade, there was no confirmation

that the disk pool policy was set correctly on /

ifs/.ifsvar.

100353 SyncIQ failed with the error message Too

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.

100413 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.

100427 A node 10 GigE network interface was

unresponsive until the node was restarted.

100438 Email alerts failed when clients did not send a

quit command before closing the connection

to the mail server.

100445 An SMB file created with a Mandatory IntegrityControl ACE failed due to an unknown ACE type.

100557 The AVScan job failed to keep pace with real-

time scanning, which resulted in a large work

queue and, in rare cases, a node panic.

100561 Quota email message templates formatted in

HTML were sent as plain text.

100585 OneFS failed to look up the email address

attribute of an LDAP user account.

Release notes

14 OneFS7.0.1.5


15/52

ID Description

- -100605 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.

100631 When the recovery shell was entered, the

following error appeared: File "/usr/

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.

100721 Request to open srvsvc pipe failed.

100722 SyncIQ backup files were removed when an

error occurred during an upgrade to OneFS

7.0.1.

100735 Users were repeatedly disconnected from anSMB share.

100798 If the SMB --host-acl option was set on hidden

shares, the option was honored, but could not

be viewed.

100848 When more than one NFS v3 clients mounted

the same node using Kerberos authentication,

the node panicked.

100899 SMB file operations were not logged as

expected when audit logging was enabled.



ID Description

- -86878 SSH connections with public key authentication

were not authenticated with role-based access

control.

Release notes



16/52

ID Description

- -97131 NDMP hardlinks containing non-ASCII

characters and symlinks linking to file names

containing non-ASCII characters failed to be

restored.

97505 The number of events for each event category

was not summarized correctly on the

Notification Rules page in the OneFS web

administration interface.

98176 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.

98299 An NFS client, when defined in an NIS netgroup,

was assigned the wrong permissions when the

client was specified as both a rootclient and aclient on an export.

98458 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.

98549 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.

98593 HDFS jobs failed due to a timeout when acompute node did not recognize the closed

socket state of a work thread.

99051 The file provider configuration value to

normalize user lookups was not carried over

when upgrading from OneFS 6.5.5 to 7.0.1.

99233 SyncIQ failed to update a synchronized file

when new data was written at an offset of 4 GB.

99382 SyncIQ job directories that were created or

moved with encoding other than UTF-8 caused

the DomainMark and SnapRevert jobs to notstart.

99596 An SMB search pattern that included a forward-

slash character did not return results.

99660 A user could not connect to a Windows home-

directory share if the user's name was the share

name.

99666 When logged in to the OneFS web interface as

an administrator, an Active Directory (AD)

Release notes

16 OneFS7.0.1.5


17/52

ID Description

- -search query that contained wildcard

characters did not return results.

99758 LSI2008 firmware contained in Firmware

Package 8.2 was not supported.

99789 Excessive error messages were stored in

the /var/log/messages directory.

99790 Backup and restore tasks stayed in QUEUED

status for an excessively long time before they

began to process.

99827 Group memberships based on the GSID did not

register, and produced incorrect permissions.

99832 Running the pw -a command resulted in looped

output.

99837 OneFS could not look up users in OpenLDAP

servers because the base search scope for the

user was incorrect.

99878 OneFS 7.0 requires clusters running Global

Namespace Acceleration (GNA) to meet an SSD-

to-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.

99975 An NDMP backup job did not respond when a

tape device returned a write error. The job

became unresponsive until it was manually

cancelled.

99988 OneFS 7.0.1.0 was not compatible with a rolling

upgrade to OneFS 7.0.1.1.

100009 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.


The following issue is resolved in OneFS 7.0.1.1.

ID Description

- -99721 Copying files with the SMB protocol and access

control lists caused the kernel to leak memory.

Release notes



18/52

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 Description

- -96581 Field upgrades of disks or RAM were not supported.

97743 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.

97400 32000X-SSD nodes were not supported.

98008 Under stress, NFS lock information leaked, leading to Fatal trap 12 node

panics in lkfi_client_remove .

98018 SnapshotIQ setting changes appeared to take effect, but advanced settings were

not preserved after the node was restarted.

98128 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 When a group change, such as a drive stall, occurred during a FlexProtect job,

another FlexProtect job was queued even if it was unnecessary.

98566 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.

98969 Aspera for Isilon was not supported.

98987 SupportIQ did not honor proxy configuration settings.

99073 In compliance mode, running the sudo isi auth users modify --

user=root command re-enabled the root account.

99132 After an upgrade, the failback action ran continuously without transferring any

files.

99162 In the OneFS web administration interface, the SmartPools page did not display

large, non-sequential group statements correctly.

99186 Windows 8 clients were not supported.

99219 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.

Release notes

18 OneFS7.0.1.5


19/52

ID Description

- -99285 InsightIQ did not collect performance data from clusters that were configured

with advanced time-zone settings, including all localized European and Asian

time zones.

99618 When a write failed due to an exceeded disk quota or a full cluster, the nodebecame unresponsive.

Resolved issues in OneFS 7.0

The following issues are resolved in OneFS 7.0.

ID Description

- -18467 /

65272

Automatic creation of a home directory upon initial SMB login was not

supported.

68670 A third-party component of SupportIQ consumed high levels of node CPU time.

N/A 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.

70097 After a rolling upgrade, the isi pkg info command returned a list of previously

installed patches.

70943 A firmware update of SanDisk boot drives did not succeed.

72319 Importing an iSCSI LUN from a snapshot returned a read-only error.

72339 /92140

When editing export options in the OneFS web administration interface, if youselected and then cleared a grayed-out option, it appeared to be a default

option.

72410 When contacting domain controllers over a secure channel, leaked sockets

occasionally occurred.

72709 The NFS Export page in the OneFS web administration interface displayed

incorrect security options after reverting to default settings.

72871 Case normalization over SMB was not supported.

75103 If a master node lost external network connectivity, it took up to 24 hours for the

cluster to send an event notification.

76009 In certain workflows, the ntp.drift file filled up the root partition, triggering

critical alerts.

76500 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.

77017 Windows 7 clients were unable to use Offline Folders over SMB 2.

77917 Updated events lost quiet and end status.

78183 Under heavy NFS load, some locks were ignored, resulting in a node panic.

Release notes

Resolved issues in OneFS 7.0 19


20/52


21/52

ID Description

- -85851 Quota email message templates that were formatted in HTML were sent as plain

text.

85974 A kernel panic occurred when an export update operation was running.

86163 In certain situations with large numbers of Kerberos clients per node, a node

crashed with a stack trace in svc_rpc_gss_forget_client.

86181 The cluster failed to handle the OTHER error code that was returned from the

Centrify LDAP server.

86281 A rare deadlock was triggered by SyncIQ.

86469 When running NDMP restores, the user sticky bit was not set on the restored file.

86533 In X200 and S200 nodes, the LCD panel did not display anything.

86639 Statistic counters for file sizes larger than 1 MB were incorrect.

86640 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.

86729 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.

87477 When restoring backed-up files, the DOS_NOINDEX bit was ignored and all files

were capable of being indexed.

87601 Due to memory corruption, NDMP processes crashed when multiple

NDMP_CONFIG_GET_SCSI_INFO orNDMP_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 Running the isi sync pol delete all command did not delete all policies.

91739 Rolling upgrades failed if each node was not in each SmartConnect pool.

93606 The OneFS web administration interface and the isi sync target ls

command displayed incorrect SyncIQ source-cluster information.

95866 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.

97110 By default, the SmartPools and SetProtectPlus jobs no longer automatically

reported space used in association with various policies.

Known issues and limitationsThe following issues and limitations are known to be present in OneFS.

Release notes

Known issues and limitations 21


22/52

ID Description

- -18901 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: Enter0.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.

54120 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.

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.

55576 The netstat -rs command reports inaccurate information. There is no known

workaround at this time.

57880 If an IPv6 subnet includes two or more NICs, one NIC might become unresponsive

over IPv6. There is no known workaround at this time.

60142 Isolated external networks on a single cluster can cause SyncIQ policies to fail. There

is no known workaround at this time.

62736 While a cluster processes a heavy I/O load, graphs in the web administration

interface might display an Unreliable Datamessage.

Workaround: Wait until the cluster is less heavily loaded to view graphs or run the

isi statistics command.

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 command-

line interface or the web administration interface.

Release notes

22 OneFS7.0.1.5


23/52

ID Description

- -Workaround: Edit the /ifs/.ifsvar/modules/flexnet/flx_config.xml

file to add an element that contains the target domain to .

64854 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.

67932 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.

68559 Monitoring with SNMP, InsightIQ, or the isi statistics command can fail when a

cluster is heavily loaded.

68602 Quota imports that are issued from the web administration interface might fail.

Workaround: Run the isi quota import command.

68656In the web administration interface, theJob Historysummary page does not displayend 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 A newly created cluster might not appear to unconfigured nodes for up to three

minutes.

69816 Writing files past the quota limit over NFSv4 generates an input-output error. There is

no known workaround at this time.

69917 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 xis 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.

Release notes



24/52

ID Description

- -Workaround: On NFS clients that encounter this issue, unmount and then remount

the directory.

70448 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.

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 atthis time.

71840 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.

71919 When you create a new target after you move iSCSI shadow clone LUNs, the web

administration interface can lock up.

72109 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.

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.

72337 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.

Release notes

24 OneFS7.0.1.5


25/52

ID Description

- -Workaround: You can remove the extra ACE by running the isi smb permissions

command.

72652 In VLAN configurations, the nmbd process generates excessive log entries

in /var/log/nmbd.log that say, WARNING: no network interfaces

found. The entries may occur when there are interfaces without IP addresses. There

is no known workaround at this time.

72864 Following a node panic and reboot, a node can become unresponsive after running

disk discovery. There is no known workaround at this time.

73038 The iSCSI Summarypage in the web administration interface may load slowly.

73050 An internal sensor monitoring lock-up may not be detected and will not generate an

alert.

73090 After a node restarts, the mountd process starts before authentication, leading to

failed user lookups. Immediately after the node restarts, users might experiencepermission 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.

73276 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.

73333 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, theActive Directorypage 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 If SmartConnect detects that it is in an inconsistent state, it will restart.

73790 Attempting to create a hard link to a file in a WORM directory returns the wrong error

message.

74090 A quieted event might appear in the wrong pane on the Events Summarypage of the

web administration interface.

Workaround: Look for quieted events underEnded 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.

Release notes



26/52

ID Description

- -Workaround: Determine WORM domains by running the isi worm command.

74251 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 When a cluster's capacity reaches 99 percent, there is insufficient space for

configuration changes. As a result, the cluster might stop working.

74303 VSS 32-bit installation succeeds on a Windows initiator, but the provider doesn't

appear in the list of installed providers.

75345 Exceeding SmartQuotas thresholds while the file system is under a heavy load might

affect the cluster's performance.

75917 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 cancelcommand,

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.

77470 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

Severitycolumn, and then clickView details.

Alternatively, run the isi events list --nodes 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 The isi statistics command displays incorrect NFS protocol latency information.

79341 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 Although SNMP requests can reference multiple object IDs, the OneFS subtree

responds only to the first object ID.

81598 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:

Release notes

26 OneFS7.0.1.5


27/52

ID Description

- -Error #1: Failed to modify user : The

authentication request could not be handled

or

Error #1: Failed to modify group : 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 The web administration interface does not prevent multiple rolling upgrades from

starting simultaneously.

84457 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.

86328 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.

87092 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.

87117 The isi smb shares permission create command fails if--permission and --

permission-type are not included. The arguments are not optional.

89086 The isi events notifications modify --email=

command fails to add the specified email ID and overwrites the existing email

addresses.

91640 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 SyncIQ may reduce to a single worker thread in the last 1% of a sync, which delays

the completion of a job.

93061 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.

93603 The SnapRevert job uses a maximum of 40 spawned job threads, regardless of the

job engine policies. No workaround is available at this time.

93663 Users who mount through NFSv4 and use a non-Active Directory Kerberos server are

not recognized in the form ofuser@realm.

Release notes



28/52

ID Description

- -Impact: users are authenticated as nobody.

93753 The isi_gather_info utility treats sparse files as regular files when creating the

compressed tar archive, which consumes more space than necessary.

94026 The default SSL port (8080) for the web administration interface cannot be modified.

94168 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.

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 targetcluster 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.

94797 The quota configuration import-export functionality is missing from the command-line

interface.

Workaround: Use the web administration interface.

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 The isi_gather_info utility fails to run on clusters running in compliance mode.

96543 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.

96812 Visiting the Events SummaryorEvents Historypages 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.

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

Release notes

28 OneFS7.0.1.5


29/52

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 ; from 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 timesynchronization 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 seconds.

Workaround: Disable the source restriction from the policy, or assign the nodes that

use GigE interfaces to the same pool.

97655 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.

97735 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.

98072 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

Unhealthy boot disks (), mirror is degraded

Release notes



30/52

ID Description

- -messages. If the cluster contains a degraded boot drive, contact Isilon Technical

Support for information about replacing the boot drive.

98341 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.

98452 The isi version osreldate command does not return the expected OneFS release

date.

98607 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.

99211 If you revert a snapshot that contains a SmartLock directory, the operation might fail,leaving the directory partially reverted.

99383 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 While the system restores an NDMP backup, it assigns insecure permissions to the

top-level directory until the restore is complete.

99951 Verbose listings of user and directory quotas incorrectly display the amount of

spaced used.

99983 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 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.

100045 NFS exports with unresolvable client host names cannot be created or modified from

the WebUI.

100272 During a node chassis replacement, the new node sometimes receives an incorrect

SKU.

100332 After change permission is granted on an SMB share, users or groups are still unable

to delete files.

100365 When isi_vol_copy is run twice, with different source paths but the same target

path, the second run fails without migrating any files.

100366 When migrating FIFO files, the isi_vol_copy utility displays the message Save

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.

Release notes

30 OneFS7.0.1.5


31/52

ID Description

- -Workaround: Create a snapshot on a directory that has already been captured in a

snapshot.

100489 Nodes that are connected to a network that supports Appletalk write kernel logging

to /var/log/messages excessively.

100659 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.

100671 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.

100997 When upgrading from OneFS 6.5 to 7.0, some configuration values related to the NFS

server's request pool are not carried over.

101077 The isi_vol_copy utility terminates when it encounters an unreadable inode in the

data stream.

101113 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.

101967 When upgrading from 7.0.1.x to 7.0.1.4, SMB change permissions do not update on

existing shares.

Upgrading OneFSBy upgrading to the latest version of OneFS, you can take advantage of new features andenhancements.

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.

Procedure1. 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

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 theroot 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 iscompatible with the newer OneFS version. OneFS provides a series of compatibilitychecks that you can run independent of an upgrade to verify that the cluster is healthy

Release notes

Upgrading OneFS 31
https://support.emc.com/downloads/15209_Isilon-OneFS


32/52

and does not contain settings or configurations that are incompatible with the new OneFSversion.

Before you begin

Before you can run the compatibility checks, you must download the installation files forthe OneFS version that you want to check for compatibility.

Procedure1. Open a secure shell (SSH) connection to any node in the cluster.

2. Run the isi version osrelease command to view the OneFS version that is running

on the cluster.

3. Optional: If the cluster is running OneFS 6.5.5.9 or earlier, you must install a patchbefore running the upgrade compatibility checks.

Options DescriptionOneFS6.5.5.06.5.5.9

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.

OneFS 6.5.4 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 OneFSversions Contact Isilon Technical Support for information about running theupgrade compatibility checks.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 thefollowing prompt:

Please specify the image to update:

Although the prompt indicates that the image will be updated, because the --check-only 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 imagelocation.

After you finishIf the command returns errors, you must resolve the errors before proceeding with theupgrade. 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 webadministration interface.

Procedure1. Log in to the cluster through the Isilon web administration interface with the root

account.

2. Navigate to the Operations Summarypage.

Release notes

32 OneFS7.0.1.5
ftp://ftp.isilon.com/outgoing/patches/patch-96453.tgzftp://ftp.isilon.com/outgoing/patches/patch-96453.tgzftp://ftp.isilon.com/outgoing/patches/patch-96454.tgzftp://ftp.isilon.com/outgoing/patches/patch-96454.tgz


33/52

l For OneFS 6.5 or earlier, click Cluster> Operations> Summary.

l 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 completebefore proceeding with the upgrade.

Options DescriptionTo wait for the running jobsto complete No action is necessary. The amount of time it takes forthe jobs to complete varies by cluster size and

configuration.

To cancel the running jobs In the Running Jobs table, click Cancel for each runningjob.

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 clickSubmit.

7. In the Upgrade Mode area, select one of the following upgrade modes, and then click

Continue.

Options DescriptionSimultaneousupgrade Upgrades and restarts all the nodes in the cluster at the sametime. While the nodes are restarting, the cluster is unavailablefor client connections.

Rolling upgrade Upgrades and restarts each node in the cluster sequentially sothat 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 thatsupport 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 beforeupgrading the node.

Options DescriptionTo immediately terminateclient connections Click Immediately terminate TCP connections.

To terminate clientconnections after a waitperioda. 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.

Release notes

Upgrade OneFS through the web administration interface 33


34/52

9. Optional: For rolling upgrades, specify whether you want to confirm restarting eachnode during the upgrade process.

Options DescriptionTo display a notification and a prompt before eachnode is restarted

Click Confirm before rebooting

nodes.

To automatically restart each upgraded nodewithout a prompt Click Reboot nodes withoutconfirmation.10.Clickyes to begin the upgrade process.

The cluster might display several confirmation messages that are related to theupgrade. You must confirm each message to continue the upgrade process.

Once the upgrade is complete, the cluster restarts, and then the web administrationinterface login page appears. If the login page does not appear, clear your webbrowser cache and reload the page.

ResultsAfter 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 clusterperformance. After the jobs complete, performance will return to normal.

Upgrade OneFS through the command-line interface

You can upgrade the OneFS version that is running on a cluster through the command-line interface.

Procedure1. 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 jobsbefore proceeding with the upgrade.

It is recommended that you wait for FlexProtect and FlexProtectLin jobs to completebefore proceeding with the upgrade.

Options DescriptionTo wait for the runningjobs to complete No action is necessary. The amount of time it takes for thejobs to complete varies by cluster size and configuration.To cancel the runningjobs Run the following command for each running job:isi job cancel

Replace 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 systemrequirements for a list of versions that support rolling upgrades.

Release notes

34 OneFS7.0.1.5


35/52

Options DescriptionSimultaneousupgrade To perform a simultaneous upgrade and restart all of the nodes inthe cluster at the same time, run the following command:

isi update

The cluster prompts you to specify the location of the OneFSinstallation image that you downloaded.

Rolling upgrade To perform a rolling upgrade, which upgrades and restarts eachnode in the cluster sequentially, run the following command:

isi update --rolling

To specify a timeout period before each node is restarted, includethe --drain-time option. This option is useful to allow time for TCPclients to disconnect from the cluster before the upgrade processrestarts the node. The default timeout is zero seconds.

To display a confirmation prompt before each node restarts,include the --manual option.

ResultsAfter 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 clusterperformance. After the jobs complete, performance will return to normal.

Verify the OneFS installation

After you install OneFS, verify that the installation was successful.

Procedure1. Confirm that the health of all the nodes in the cluster isOK.

isi stat

2. Remove the installation files from the /ifs/data directory.

rm /ifs/data/onefs_v_install.tar.gz

Replace 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 Description

- -Disk load 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

Release notes

Verify the OneFS installation 35


36/52

Check Description

- -the cluster is not being heavily used to proceed

with the upgrade.

Free space Checks the free space and returns either a

warning or an error if certain capacitythresholds are exceeded for the following

cluster partitions or node pools:

u /

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.

u /var

Returns a warning if the/var partition is


returns an error when the partitionreaches 100 percent full.

u /ifs

Returns a warning if the /ifs partition is


returns an error when the partition

reaches 100 percent full.

u 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.

Release notes

36 OneFS7.0.1.5


37/52

Check Description

- -Outstanding critical events 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 theissues 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 withthe 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 Guidefor information about the

supported configurations for SmartPools.

Where to go for supportYou can contact Isilon Technical Support for any questions about Isilon products.

Online support https://support.emc.com/

Telephonesupport

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 SupportCenters.

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 andthen select Option 1 - All Hardware Products except AX.

Help with onlinesupport

Questions specific to EMC Online Support registration, access, or siteassociation: [email protected]

Release notes

Where to go for support 37
mailto:[email protected]://www.emc.com/collateral/contact-us/h4165-csc-phonelist-ho.pdf?cc=http://www.emc.com/collateral/contact-us/h4165-csc-phonelist-ho.pdf?cc=https://support.emc.com/


38/52

Pre-OneFS 7.0 command mappingThis 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 New Command Notes

- - -isi auth ads status isi auth ads list --verbose

isi auth ads view --

verbose

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

isi auth ads trusts view

isi auth ads status --refresh isi auth refresh Now requires root privileges.

isi auth ads join isi auth ads create

isi auth ads join --keep-accounts n/a There is no equivalent command for this

feature.

isi auth ads leave isi auth ads delete

isi auth ads leave --

workgroup=

isi auth settings global modify

--workgroup

isi auth ads users list isi auth users list --provider

ads:

isi auth ads users list --

name=--verbose

isi auth users view

ads:

Can also list by --sid and --uid.

isi auth ads groups list isi auth groups list --provider

ads:--domain

isi auth ads groups list --

name=--verbose

isi auth groups view

--provider ads:

Can also list by --sid and --gid.

isi auth ads accounts list isi auth ads trusts list

isi auth ads accounts list --

domain=



verbose

The combination of the new commands is

the equivalent of the old command.

Release notes

38 OneFS7.0.1.5


39/52

Old Command New Command Notes

- - -isi auth ads search isi auth users list

or

isi auth groups list

Search functionality is currently not

supported.

isi auth ads spn isi auth ads spn Now requires root privileges.

isi auth ads dc --domain=

--list

isi auth ads trusts controllers

list --verbose


--set-dc=

isi auth ads modify --

domain-controller


--reset-schannel

isi auth ads modify --

reset-schannel yes


--site=


Querying for sites is not supported.


--verbose


verbose

isi auth ads time isi auth ads view

isi auth ads time --sync n/a There is no equivalent command for this

feature.

isi auth ads cache flush isi auth users flush

or

isi auth groups flush

The following parameters have no

equivalent: --user, --group, --uid, or --gid.

isi auth local {users | groups}

isi auth local 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 users

isi auth local users create

isi auth local users new

isi auth users create New users are created under the local

Documents

OneFS 7.0.1.5 Release Notes