Docu46725 OneFS Version 6.5.5.19 Release Notes

OneFS 6.5.5.x Release

ONEFS 6.5.5.19 RELEASE NOTES OneFS 6.5.5.x Release

2 OneFS 6.5.5.19 Release Notes

Published April 3, 2013

Copyright © 2013 EMC Corporation. All Rights Reserved.

EMC believes the information in this publication is accurate 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.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.



Table of Contents

OneFS 6.5.5.19 release notes ................................................................................................................ 4

Download location .................................................................................................................................................. 4

OneFS 6.5.5.19 enhancements ............................................................................................................................... 4

OneFS 6.5.5.19 resolved issues .............................................................................................................................. 4

OneFS 6.5.5.19 known issues ................................................................................................................................. 5

Previous OneFS 6.5.5.x release enhancements and resolutions .............................................................. 6

Previous release enhancements.............................................................................................................................. 6

Previously resolved issues .................................................................................................................................... 13

Upgrading OneFS ................................................................................................................................ 37

Upgrade prerequisites .......................................................................................................................................... 37

Downloading the OneFS image file ........................................................................................................................ 38

Upgrade using the OneFS web administration interface ........................................................................................ 39

Upgrade using the command-line interface ........................................................................................................... 40

Rolling upgrade ..................................................................................................................................................... 40

Simultaneous upgrade .......................................................................................................................................... 40

Upgrade Verification ............................................................................................................................................. 41

Contact Support .................................................................................................................................................... 42



OneFS 6.5.5.19 release notes

OneFS 6.5.5.19 Release Notes describe enhancements, resolved issues, and known issues for this maintenance release. They also supplement the OneFS 6.5.5 Release Notes, which you should review before installing OneFS 6.5.5.19.

Download location

To download the OneFS 6.5.5.19 installation file, refer to the Upgrading OneFS section of this document.

OneFS 6.5.5.19 enhancements

Bug ID Description Release

99757 Adds support for 8GB boot flash drives. 6.5.5.19

101460 Adds support for Mars-K Plus AC0 firmware. 6.5.5.19

99748 Adds support for the Seagate Megalodon 4TB hard drive. 6.5.5.19

102144 Adds the ability to mount snapshot aliases in OneFS. 6.5.5.19

100176 Adds the isi_set_ram_hightemp tool for changing BIOS settings in order to manage DIMM

operations in high-temperature scenarios.

6.5.5.19

OneFS 6.5.5.19 resolved issues

This section describes the issues resolved in this OneFS 6.5.5 release.


101310 The vsftpd daemon looped infinitely until it eventually exited, disrupting client FTP

transfers.

6.5.5.19

101679 Identity mapping operations failed after encountering two SIDs hashed to the same ID

value.

6.5.5.19

93851 In the event of a power supply failure, the output of the isi_hw_status command did not

indicate which power supply failed.

6.5.5.19

101675 If several SMB clients connected to a single node opened a single file more than 32767

times without eventually closing them, the node in use would panic.

6.5.5.19

101963 SMB sessions remained open for a period of time after clients disconnected, resulting in the

server becoming unavailable after the open sessions accumulated.

6.5.5.19

102131 The lwiod SMB service doubled the count of open client sessions, draining resources and

eventually causing the service to become unavailable.

6.5.5.19




101601 OVT reported failures when run on nodes with motherboards containing an updated serial

number format.

6.5.5.19

101357 While working on a wide directory, SyncIQ returned the error <systemoutput>Failed to

delete user attribute</systemoutput>.

6.5.5.19

101803 The lwiod SMB service became unavailable and generated a core file when a zero-copy

write unsuccessfully executed.

6.5.5.19

101199 The Infiniband subsystem would time out, causing node panic. 6.5.5.19

91930 SNMP traps were not sent for specific alerts, including SSD drive usage, drive status, and

bootdisk failures.

6.5.5.19

99922 When a OneFS cluster was renamed from the OneFS web administration interface, the

built-in administrator user remained associated with the old name.

6.5.5.19

102461 The wait time associated with identity mapping calls to an authentication source could not

be lowered to a value of 0.

6.5.5.19

102686 The lsass daemon lost connectivity to Active Directory servers, resulting in authentication

failure.

6.5.5.19

100819 Conflicting filesystem locks due to high-frequency snapshot schedules may have resulted in

node panic.

6.5.5.19

101291 The Flexprotect drive scan phase performed unnecessary writes, resulting in longer

runtimes for Flexprotect jobs.

6.5.5.19

OneFS 6.5.5.19 known issues

This section details the known issues in this OneFS 6.5.5 release.

Bug ID Description

100493 SSD drives on OneFS 6.5.5.11 clusters fill to capacity after a system outage.

101765 Deleting a LIN within a SyncIQ domain may also delete the domain.

99653 The lwiod SMB service does not correctly handle different UNIX path character encodings.

102620 The isi_vol_copy utility may remove ACL from files during migration.



Previous OneFS 6.5.5.x release enhancements and resolutions

This section discusses enhancements and resolved issues in previous releases of OneFS 6.5.5.x.

Previous release enhancements

ID Description Release

95419 OneFS now performs three sequential battery readings to ensure a correct status before

entering read-only mode.

6.5.5.18

101248 Enhances OneFS compliance with Infiniband switch specification. 6.5.5.18

100433 Enhances NDMP Direct Access Restore (DAR) throughput performance, particularly for large

files, by eliminating extraneous read requests.

6.5.5.18

95421 Adds a new battery test scheduling process. Upon startup, OneFS schedules a test

immediately if the most recently battery test failed.

6.5.5.17

99891 Adds path information to the Apache error message "Could not open the lock database,"

identifying the affected file.

6.5.5.16

99821 Adds a new battery status. If the battery is disconnected by ship mode, the OneFS isi

batterystatus command will return output similar to the following:

battery 1: Battery disconnected by Ship Mode

6.5.5.16

99657 Adds expiration time option for cached Active Directory user and group information through

the OneFS isi auth config modify --param=cache-entry-expiry command.

6.5.5.16

97123 Adds the max-password-age argument option for the OneFS isi auth config list

command.

6.5.5.16

98289 Adds OVT support for firmware added in Isilon Firmware Package 8.2. 6.5.5.16

99746 Adds support for Seagate Manta Ray 3TB drive firmware version 0006. 6.5.5.15

99745 Adds support for Cobra-E drive firmware version A350. 6.6.5.15

98665 Improves logging of failed SMB logins to help debug authentication issues. 6.6.5.15

97952 Reduces excessive log entries when a DNS resolver is not configured. 6.5.5.14

98937 Changes logging of routine Iwiod errors to debug level to reduce log file size and improve

troubleshooting.

6.5.5.14

97767 Improves hardware-related event alerts to eliminate a generic hardware error – I2C bus

hang has occurred alert.

6.5.5.12




97501 Stops automatically collecting information about SmartPools and SetProtectPlus policies.

Although you can re-enable the setting, collecting the data can take a long time and slow

down other jobs. To re-enable the setting, run the following command:

isi job config jobs.sp.usage_accounting=True

6.5.5.12

97125 Improves network monitoring to reduce the number of nodes that OneFS separates, or

splits, from a cluster when an InfiniBand problem occurs.

6.5.5.12

96666 Improves debugging of certain rare node restarts caused by file-locking conflicts. 6.5.5.12

96494 Adds support for Hitachi Mars-KP 4 TB, 3 TB, and 2 TB 512n hard drives. 6.5.5.12

77762 Improves CPU efficiency of OneFS event handling. 6.5.5.12

96305 Improves support for more removable USB drives. 6.5.5.11

95760 Enhances the vsftpd service: When error_on_empty_dir=YES is specified in the file

vsftpd.conf, the service returns 550 - LIST failed on attempting to list an empty

directory.

6.5.5.11

94061 Improves diagnostics of Active Directory server timeouts from the cluster. 6.5.5.11

95507 Isilon for vCenter 1.2 (Beta) introduces scheduled virtual machine backups. 6.5.5.11

95505 Improves the algorithm for OneFS drive smartfail criteria. OneFS now smartfails a drive when

it has been stalled for 3 cumulative hours in the past 30 days.

6.5.5.10

95465 Enhances the isi_vol_copy command with statistical reporting, a feature which was

removed from this command after OneFS 6.5.4.x.

6.5.5.10

95455 Adds username expansion support to share names in the form of \\clustername\<Active

Directory user name>.

To use this feature you should create a special share (for instance, with the name “%U”) and

can specify a path, such as /ifs/home/%U, although any path to that share is acceptable.

For example, when a user named userjoe executes the command

net use \\cluster\userjoe, an Isilon server first attempts to connect to the share

\userjoe. If that fails, OneFS tries to find the special share %U. If it exists, OneFS then

compares the username and the share name. If they match, the path from the special share

is used to map to the share. In this example, OneFS would map to /ifs/home/userjoe.

6.5.5.10

95105 Enhances troubleshooting and diagnosis of a rarely encountered system lockup. 6.5.5.10

94197

95079

Changes multiplexed SMB connection counting to match Microsoft's implementation and

allows configuration of the maximum multiplexed connections per client.

6.5.5.10

94984 Improves memory management for file system analytics. This now prevents issues when a

job is set to “High Impact.”

6.5.5.10




94923 Adds alert instance IDs to the Isilon Management Information Base (MIB) object IDs. You can

now correlate a trap with an alert and clear the alert through the command-line interface or

through the OneFS web administration interface.

6.5.5.10

94231 Adds capacity to the isi update command so that you can more easily check for potential

issues before you upgrade.

6.5.5.10

94164 Adds support for Netlist bootflash drives. 6.5.5.10

94018 Adds support for A50 firmware for Hitachi Ultrastar A7K2000 (Mars-K) 2 TB HDD (model

0F12455).

6.5.5.8

94016 Adds support for A50 firmware for Hitachi Ultrastar A7K3000 (Mars-K) 3 TB SATA HDD

(model HUA723030ALA640).

6.5.5.8

93853 Adds support for Hitachi Ralston Peak 25nm "B" fw A110 (100/200/400 GB) solid state drives

(SSD).

6.5.5.8

93240 Adds support for Netlist 8 GB boot drives. 6.5.5.8

92504 Adds support for the following:

Seagate Constellation ES (Muskie Plus) 2 TB SATA HDD (model ST2000NM0011);

Seagate Constellation ES (Muskie Plus) 1 TB SATA HDD (model ST1000NM0011);

Seagate Constellation ES (Muskie Plus) 500 GB SATA HDD (model ST500NM0011).

6.5.5.8

90774 Enhances OVT testing of SAS and SATA drives. 6.5.5.8

92722 Adds support for Hitachi Cobra-E A2D0 hard drive firmware. 6.5.5.8

92520 Resets the following OneFS operational parameters to improve cluster interoperability with

clients running Microsoft Windows Vista:

GlobalCreditLimit increased from 25,000 to 250,000;

ClientCreditLimit doubled from 1024 to 2048;

ClientCreditMinimum increased from 4 to 5.

6.5.5.7

92506 Adds support for Hitachi MarsK Plus 4 TB emulated drives. 6.5.5.7

92232 Adds support for Hitachi 200 GB and 400 GB SSD drives. 6.5.5.7

91996 Reduces memory consumed by the input-output process (lwiod). 6.5.5.7




91137 Adds an optional parameter (use_snmp_trap=true) to the command

isi_gconfig celog.celog_settings.

In OneFS 6.5.5.6 or earlier, OneFS sent SNMPv2 “InformRequest” messages by default,

irrespective of what version of SNMP was installed, with the result that SNMPv1 monitors

could not properly interpret the messages.

To configure a cluster to send SNMP traps instead of SNMP inform requests and then verify

the reconfiguration, do the following:

1. (Set the parameter): isi_gconfig celog.celog_settings.use_snmp_trap=true

2. (Query the settings): isi_gconfig celog.celog_settings.use_snmp_trap

(Expected query result): celog.celog_settings.use_snmp_trap (bool) = true

6.5.5.7

89114 Adds support for Seagate Compass 900 GB hard drive. 6.5.5.7

91447 Adds support for MD5 authentication to the isi_vol_copy command. 6.5.5.6

91148 Implements improvements to increase the performance of FlexProtect, AutoBalance, and

IntegrityScan.

FlexProtect and AutoBalance run faster on clusters that have a copy of all metadata on SSD

nodes. Adding a drive to a node will no longer cancel IntegrityScan. If the most recent job

completed was a FlexProtect job, Multiscan will not start a group change unless the change

adds a device to the cluster. If Multiscan is disabled, the behavior described above applies to

Autobalance and Collect.

6.5.5.6

90832 Hardware configuration information is now backed up to non-volatile memory. 6.5.5.6

90647 Upgrades Aspera to version 2.7.4. For more information about this patch, see the release

notes on the Aspera website.

6.5.5.6

90152 Improves HDFS to decrease CPU usage. 6.5.5.6

89898 OneFS now issues an alert if a flash-based boot disk loses its disk mirror. 6.5.5.6

89158 Increases the default number of HDFS threads to improve HDFS performance. 6.5.5.6

87732 Improves HDFS write performance. 6.5.5.6

87316 Adds the ability to control whether OneFS sends a notification for an informational job

engine failure.

You can manage the setting in the OneFS web administration interface by navigating to

Status >> Events> > Notification Rules>> Add Rule, and then selecting the check box in the

Software events >> Information column for the Job {job_type} has failed event.

6.5.5.6

84389 Upgrades OpenSSL to version 0.9.8x. For more information about this release, see the

release notes on the OpenSSL.org web site.

6.5.5.6




88857 Adds support for the following hardware:

Hitachi Ralston Peak 25nm 100 GB SSD drive;

Hitachi Ralston Peak 25nm 200 GB SSD drive;

Hitachi Ralston Peak 25nm 400 GB SSD drive.

6.5.5.6


Hitachi Cobra-E 300 GB SAS HDD drive;

Hitachi Cobra-E 600 GB SAS HDD drive;

Hitachi Cobra-E 900 GB SAS HDD drive.

6.5.5.5

88059 InsightIQ supported LOW (key length less than 128-bit) encryption ciphers. InsightIQ now

supports only MEDIUM (128-bit key length) and HIGH (greater than 128-bit key length)

ciphers when encrypting communications between the server and clients.

6.5.5.5

88569 Adds an option to the isi nfs export command to reload the NFS exports configuration after

changes are made to DNS or NIS.

To refresh the NFS exports configuration, run the following command:

isi nfs exports reload

6.5.5.5

88562 Improves performance by decreasing the impact on the system when the Anti-Virus > On

Access Scans > Scan files when they are opened option is selected.

6.5.5.5

89244 Adds a sysctl that, when set to true, allows the showmount –e command to list netgroup

names instead of host names.

To enable the showmount –e’ command to display netgroup names, run the following

command:

sysctl vfs.nfs.mountd_ngs_in_showmount_e=1

For information about making sysctl settings persistent, go to support.emc.com and search

for “Configuring sysctls and making sysctl changes persist through node and cluster reboots

and upgrades.”

6.5.5.5

72871 Adds the ability to force file names for new files created over SMB to use lower case

characters only. For more information, see KB 3543 “How to use the SMB - - manglemap

option to replicate Samba ‘preserve case = no’ in OneFS 6.5.5.6 and later” in the Isilon

Knowledge Base.

6.5.5.5

78487 Updates the OneFS event processor to decrease the number of un-actionable events

Starting with OneFS version 6.5.5.4, the “Active Directory Offline” event has been disabled.

This event was generated whenever a node was unable to get a response from an Active

Directory (AD) server on the network. In most cases, this was an AD server or network

problem and was un-actionable.

The “Active Directory Offline” event can be re-enabled by running the following command

on any node in the cluster:

isi auth config modify --domain-offline-alerts=yes

6.5.5.5

79153 Adds a new IB GUID range for Belknap NVRAM/IB cards. 6.5.5.4




78480 The –ignoreconflicts option is added to the isi nfs exports [create | modify]

command to suppress conflicts when creating and modifying exports.

6.5.5.4

78126 The isi set command is updated to include the -L <lin> parameter. 6.5.5.4

78109 Adds the FSA use-snapshot configuration to the settings modifiable through the platform

API to support InsightIQ config.

6.5.5.4

78108 Changes default FSA behavior to run FSAnalyze jobs without a snapshot. 6.5.5.4

70392 Adds a man page for the isi smb commands. 6.5.5.4

85676

86571

86805

86813

86815

86819

86821

86929

86947

87020

87137

87302

Improves write algorithms for flash boot disks as well as logging mechanisms to track writes

to flash regions for measurement purposes, improving the lifespan of the flash devices.

6.5.5.4

86370 The NDMP server now generates a core dump file that provides more diagnostic and

troubleshooting information.

6.5.5.3

86376 Introduces the following changes to improve NDMP performance:

During backup, OneFS no longer collects file protection information not used during

a restoration;

When opening files for backup, OneFS does not perform directory entry searching.

6.5.5.3

86018 Adds support for applications such as HBase and Hive that require the append() call. 6.5.5.3

85239 Adds support for applications such as Apache HDFS 0.20.205 that utilize the 7-param create()

call.

6.5.5.3

87336 Adds support for Hitachi Mars-K drives that have updated firmware. 6.5.5.3

86835 Backup and restore now report file size statistics to the Data Management Application

(DMA).

6.5.5.3

82110

85342

85343

85594

Adds several enhancements to the isi_gather_info utility. It now gathers:

• a more verbose snapshot list;

• the contents of the /ifs/.ifsvar/db/node_info_cache directory;

•the contents of /ifs/.ifsvar/aspera/etc/;

• more information about new hardware platforms.

6.5.5.3





Hitachi 500 GB SATA HDD (Ultrastar A7K2000) (Jupiter U);

Hitachi 1 TB SATA HDD (Ultrastar A7K2000) (Jupiter U);

Hitachi 2 TB SATA HDD (Ultrastar A7K2000) (Jupiter K).

6.5.5.2

85556 Firmware updates are applied properly to all candidate firmware. 6.5.5.2

85541 The operating system issues an event notification when the power supply is unseated from

an X200 or S200 node.

6.5.5.2

85108 Modifies the restoration process to more closely mirror the behavior of the backup process.

Before this release, a list of the files that were backed up, as well as some statistical

information such as file types and sizes, was issued after a successful backup, but the same

information was not issued after a successful restore.

6.5.5.2

76038 Adds support for field upgrade of Western Digital and Hitachi disk firmware. 6.5.5.2

76520 Adds configuration information describing which drive types and firmware are qualified for

this family of OneFS.

6.5.5.2

75772

76376

76383

Adds support for S200 node configured with 6 x 1GigE ports 6.5.5.2

76293 Updates BIOS to add OVT support for new hardware revisions. 6.5.5.2

74650 Adds a new permissions policies option that allows a user to remove an existing ACL and

create an ACL equivalent to the UNIX permission for all users/groups referenced in the old

ACL.

6.5.5.2

67650 Changes the isi_hw_stats command to display the amount of installed RAM. 6.5.5.2



Previously resolved issues

This section describes resolved issues for earlier releases of OneFS 6.5.5.


100638 A memory leak issue with the srvsvc daemon was caused by listing a large number of SMB

shares.

6.5.5.18

86660 Local guest account modification sometimes failed when the assume-default-domain

command was set to TRUE.

6.5.5.18

89701 When an NFS client failed to mount a directory on the cluster, no alert was generated

because of an invalid SNMP configuration.

6.5.5.18

93851 In the event of a power supply failure, the output of the OneFS command-line interface

isi_hw_status command did not indicate which power supply failed.

6.5.5.18

99361 Running the Microsoft psfile command-line utility from an SMB client caused the OneFS SMB

server to restart and did not return the expected output.

6.5.5.18

100072 A write operation sometimes wrote less data than requested, but correctly returns the

amount of data written. In some circumstances, this may have caused a node to kernel

panic.

6.5.5.18

87066 Outdated data in the L1 cache triggered Isilon Data Integrity alerts. 6.5.5.18

92454 The OneFS authentication service crashed when associating a user with an Active Directory

domain.

6.5.5.18

100864 An error caused export refreshes to fail during a large export refresh. Impact: NFS export

processing never completed.

6.5.5.18

101193 If a CTO node was reimaged with a USB device, the node was unable to boot because of a

missing system configuration number.

6.5.5.18

71951 Creating a snapshot of a directory or file with the NTFSOG attribute set caused an assertion

during initialization of the new snapshot.

6.5.5.18

101056 During migration of NetApp data, the isi_vol_copy utility displayed the error message

"cannot find directory inode" and aborted the process.

6.5.5.18

85329 The lsassd daemon would crash during user lookup on the OneFS web administration

interface.

6.5.5.18

101199 The Infinband subsystem incorrectly determined commands as timed out, causing node

panic when the system time was changed.

6.5.5.18

99361 Running the Microsoft psfile command-line utility from an SMB client caused the OneFS SMB

server to restart and not return expected output.

6.5.5.18



99922 When a OneFS cluster was renamed from the OneFS web administration interface, the built-

in Administrator user remained associated with the old cluster name.

6.5.5.18

98846 A missing space in the OneF S command-line interface isi smb permission list command

caused the output to be difficult to read.

6.5.5.18

86334 The opensm daemon would write an identical version of the /var/log/opensm-1.topo file

every ten seconds when an IP loopback cable was installed.

6.5.5.18

101238 QuotaScan incorrectly re-retrieved domain instance IDs before marking them as ready. 6.5.5.18

101168 Random characters appeared in the folder names of NetApp user shares that were migrated

to an Isilon cluster.

6.5.5.18

91920 Flexprotectlin leaked a small amount of memory when starting or resuming processes. 6.5.5.18

101072 The replicated NFS client data on the cluster became inconsistent, causing a lockd thread to

cease processing.

6.5.5.18

100813 Multiple NFS 3 clients simultaneously mounting the same node using Kerberos

authentication could have caused the node to panic.

6.5.5.17

99974 The lsassd daemon core dumped when performing a guest account lookup if the /ifs

directory was not mounted.

6.5.5.16

99710 The safe.short.memspeed test failed during OVT in systems configured for 48 GB memory. 6.5.5.16

99115 Running the isi status -n command resulted in a traceback with the error message "TypeError: can’t multiply sequence by non-int of type ‘float.’"

6.5.5.16

97292 If the /ifs directory became unavailable during a backup, the reader process would fail while

the writer process would continue indefinitely.

6.5.5.16

99331 Files with a user ID number higher than 65535 would be assigned incorrect file permissions

when copied through the isi_vol_copy utility.

6.5.5.16

86199 OneFS failed to detect node deadlock.

Impact: Potential cluster outage due to deadlock.

6.5.5.16

100140 When an NFS export was configured to map incoming users, users that were unable to be

mapped were given root access privileges.

6.5.5.16

99655 OneFS did not correctly display time-zone revisions made between March 2, 2010 and March

24, 2012.

6.5.5.16

100244 The FSAnalyze job ran indefinitely and without producing results when interrupted during

the merge phase.

6.5.5.16

99942 If a hard link existed for a source file, and the matching destination file was a soft link

directed to an external file system, SyncIQ occasionally failed with the error message "Too

many links.”

6.5.5.16



99737 During a field chassis replacement, a node’s EEPROM data was copied to the files in the

/etc/isilon directory during startup before any checks were performed on the data. This

resulted in the new node being misidentified as an empty chassis.

6.5.5.16

96036 A SyncIQ policy failed when a file with the immutable bit set was included in the policy. The

immutable bit prevents the file from being modified.

6.5.5.16

100358 Nodes panicked when file operations exceeded AVscan daemon processing limitations. 6.5.5.16

100392 An NFS file owner could successfully override restricted write permissions for a file, but was

denied access when attempting to set an updated size attribute.

6.5.5.16

95493 If the SMB --host-acl option was set on hidden shares, the option was honored, but could not

be viewed.

6.5.5.16

81543 The OneFS isi auth local users modify command did not issue a password prompt

when run with the --password argument.

6.5.5.16

100044 SyncIQ error messages displayed an incorrect directory path if an error occurred during file

transfer.

6.5.5.16

99586 A backup created by OneFS may not contain all directory files if the directory name was

changed. This issue has been resolved in this release.

6.6.5.15

99585 NDMP hardlinks containing non-ASCII characters and symlinks linking to a file name

containing non-ASCII characters would fail to be restored. This issue has been resolved in this

release.

6.6.5.15

99520 An SMB search pattern that included a forward-slash character would not return results. This

issue has been resolved in this release.

6.6.5.15

99447 A memory leak in the isi_vc_d daemon would cause the process to become unavailable for a

short amount of time. This issue has been resolved in this release.

6.6.5.15

99446 Backup and restore tasks would stay in QUEUED status for an excessively long time before

they began to process. This issue has been resolved in this release.

6.6.5.15

99445 The Isilon for VCenter web interface would become unavailable for a long period of time due

to a file locking issue. This issue has been resolved in this release.

6.6.5.15

99444 Excessive error messages were stored in the /var/log/messages directory. This issue has

been resolved in this release.

6.6.5.15

99342 The value for the --sharename option for the isi smb create command did not allow spaces

between words. This issue has been resolved in this release.

6.6.5.15

99212 An NDMP backup job would not respond when a tape device returned a write error. This

issue has been resolved in this release.

6.6.5.15

99174 A SyncIQ policy that was canceled and rerun was failing to report all phases of the

subsequent canceled job. This issue has been resolved in this release.

6.6.5.15

99125 SyncIQ sometimes failed to update a synchronized file if new data was written at an offset of

4 GB. This issue has been resolved in this release.

6.6.5.15

99043 HDFS jobs could fail due to a timeout if a compute node did not recognize the closed socket

state of a work thread. This issue has been resolved in this release.

6.6.5.15



98571 Windows 8 and Windows 2012 clients were unable to initiate more than one session with a

cluster. This issue has been resolved in this release.

6.6.5.15

98194 An NFS client, when defined in a NIS netgroup, could be assigned the wrong permissions

when the client was specified as both a rootclient and a client on an export. This issue has

been resolved in this release.

6.6.5.15

98022 Node panics would occur due to an accounting error in the NFS lock subsystem. This issue

has been resolved in this release.

6.6.5.15

97000 When a LIN reached its storage limit, an 8k extension block was created at equivalent

protection levels. Because no automated process was employed to maintain the storage

limit unless a user modified the file, the extension blocks could fill the disk pool to capacity.

This issue has been resolved in this release.

6.6.5.15

96966 Upgrading from OneFS 6.0.x a later version could fail to preserve the coalescer preference

attribute for iSCSI LUNs. The default value would be applied instead. This issue has been

resolved in this release.

6.6.5.15

96385 The Events page in the OneFS web administration interface was not counting all of the

events correctly when creating or editing a notification rule. This issue has been resolved in

this release.

6.6.5.15

96094 A risk of local privilege escalation attack threatened various operating systems running on an

Intel processor, including OneFS, as identified in CVE-2012-0217. This issue has been

resolved in this release.

6.6.5.15

98568 SMB processes could fail with the following log entry: “too many open files.” 6.5.5.13

98523 A single node restart could cause multiple node restarts. 6.5.5.12

97468 Two processes could simultaneously write to the temporary file snapshot_schedule.xml. 6.5.5.12

97157 Contention for buffer resources could cause a node to restart when a large number of blocks

were written to disk.

6.5.5.12

96800 SmartConnect did not correctly assign IP addresses to aggregate interfaces when the

interfaces were associated with VLANs.

6.5.5.12

82727 NFS readdir operations were allowed for non-directory objects.

Non-directory objects no longer accept NFS read directory operations. The operations

triggered multiple IDI failure detection alerts on the mounted node.

6.5.5.12

86502 A node could restart upon startup if ECC errors were found on the drive containing the

mounted root file system.

6.5.5.12

92735 An event alert such as “Cluster needs to be restriped but FlexProtect is not running” was

generated while the isi_job_status command showed the FlexProtectLin process running.

6.5.5.12

96942 Rarely, a Hitachi Mars-K drive reset caused a failure that prevented the system from adding a

replacement drive.

6.5.5.12

95174 A node’s 10GigE network interface card could become unresponsive to network traffic until

the node is restarted.

6.5.5.12

98303 Occasionally, the Isassd process in an LDAP environment consumed too much memory and

failed.

6.5.5.12



98134 Some mountd processes failed during export reload requests because of unnecessary error

checking.

6.5.5.12

97959 A memory leak in mountd could occur if the process received frequent HUP signals. The

memory leak could eventually cause the service to fail and temporarily prevent clients from

mounting drives.

6.5.5.12

97599 Incremental backups might not have completed due to memory leakage when the

FH_REPORT_FULL_DIRENTS parameter was enabled.

6.5.5.12

97502 An NFS client could overload a node by closing the TCP connection in the middle of a very

large read-dominant request stream.

6.5.5.12

97241 In OneFS releases 6.5.5.5 through 6.5.5.11, NFSv3 and NFSv4 clients generated an incorrect

exit code when performing an ’exclusive create’ operation on an existing file.

6.5.5.12

97225 Network Status Monitor (NSM) timed out while waiting to resolve a host name in the file

rpc.statd, resulting in unreliable file locking for clients that had unresolved host names.

6.5.5.12

97031 SMB 2.0 connections could fail with system error 64 when SMB 1.0 packet signing was

enabled on server and client.

6.5.5.12

91827 Excessive SMB logging of trivial events. 6.5.5.12

98801 NVRAM in a node became unresponsive and eventually the node restarts. 6.5.5.12

98205 NFS-related advanced settings for SnapshotIQ were ignored following a node restart. 6.5.5.12

98004 Multiple email notifications were sent out for the same alert. 6.5.5.12

97979 Occasionally, new drives were not added to a provisioned diskpool when a smartfail

operation occurred.

6.5.5.12

97100 A memory leak in SyncIQ worker processes occurred during diff_sync operations. 6.5.5.12

96534 Rolling upgrades coud fail if all nodes are not in all SmartConnect pools. 6.5.5.12

94819 Versions earlier than Rsync 3.0.5 had errors when copying more than 4 GB of sparse data

using the -- sparse(-S) option, rendering the affected files unreadable.

6.5.5.12

84944 SmartConnect did not correctly assign IP addresses to aggregate interfaces when the

interfaces are added or removed from a SmartPool. Applicable patch: 97154

6.5.5.12

96414 A CTO (Configure to Order) node could lose its CTO configuration after upgrading to 6.5.5.8

or 6.5.5.10 if the CTO configuration was not updated as described in the EMC Knowledge

Base article “After upgrading to OneFS 6.5.5.8 or 6.5.5.10 some S200 and X400 nodes reboot

with the error: LNI not found on this node!” Without this configuration, the node could not

rejoin the cluster. Customers running OneFS 6.5.5.8 or 6.5.5.10 with this issue should call

Isilon Technical Support.

6.5.5.11

94934 An overcharged battery could take longer to discharge than the timeout allowed by the

command isi_checkjournal, leading to false reports that the battery failed the discharge

testing.

6.5.5.11

94190 The isi_drive daemon records an incorrect number of empty bays. For instance, looking in

/var/log/isi_drive.log, a customer might see a message similar to the following:

2012-09-19T18:39:45-05:00 <3.3> eh-RX-655-1(id1) isi_drive_d[3797]: Drive

ratio is wrong: exp_ssd 2, exp_hdd 10, act_ssd 3, act_hdd 7, empty bays 0

6.5.5.11



94358 A healthy node could go into read-only mode because of a failed I2C bus read. 6.5.5.11

96410 The command isi devices -a add -d <node>:<bay> did not add a replacement drive

until the node is restarted.

6.5.5.11

89412 The shadow volume of an iSCSI LUN could not be cloned because the shadow mask was not

properly captured.

6.5.5.11

95314 The Likewise I/O daemon (lwiod) failed to respond correctly to SMB2 signed packets. 6.5.5.11

95602 Users and groups utilizing the approximate [owner | group] mode using only the ACE with

the [owner | group] ID permission might not have interacted correctly with the Access

Control List (ACL).

6.5.5.11

96425

96426

Increasing the size of a thickly-provisioned iSCSI LUN destroyed the contents of the LUN. 6.5.5.11

96142 The iSCSI process failed when iSCSI ordered commands were received out of order. 6.5.5.11

95933 The SMB 1.0 NT Trans request NT CREATE incorrectly failed upon encountering an empty file

name.

6..5.11

89920 After FlexNet updated a subnet mask, all NFS clients were disconnected. 6.5.5.11

91934 Some events did not generate an SNMP trap and logged the error message Unable to send

trap to XXXXX: code 1 msg ISILON-TRAP-MIB:: measuredValue: Bad value name

(92.25).

6.5.5.11

94886 In a rare situation, two drives in a node being replaced simultaneously resulted in the

physical drives in a node being assigned the same logical drive number.

6.5.5.11

95856 The command isi lun modify used with the - - protection argument failed to change

the protection level of the LUN.

6.5.5.11

95891 Under certain circumstances the isi_job_d process crashed repeatedly until MediaScan was

disabled.

6.5.5.11

95985 A rare network error caused nodes to restart. Subsequent examination of the stack tracing

finds "sosend" in the trace.

6.5.5.11

96105 The Local Administrators group security identifier (SID) was mapped to a user ID (UID),

resulting in permission errors, such as when applying ACLs to directories.

6.5.5.11

96166 OneFS 6.5 – 6.5.5.10 did not properly calculate the initial credits of SMB 2.0 clients. 6.5.5.11

96549 The AV Scan process consumed too much memory and caused node panics. 6.5.5.11

96742 In the OneFS web administration interface the LDAP administrator’s password was displayed

in plain text while configuring LDAP authentication.

6.5.5.11

94438

94439

Alerts were not being properly generated for electrical power current events. . 6.5.5.11



96027 Since late 2011, Intel network interface cards (NIC) have included with a new Organizational

Unique Identifier (OUI), which compose the initial 6 hex digits of the MAC address: 68:05:ca

(but possibly others). Nodes that use Intel NICs with this new OUI scheme might not have

accepted configuration of the default outbound gateway through FlexNet.

For more information, go to support.emc.com and search for “Unable to configure the

default outbound gateway using FlexNet on nodes that contain NICs that use a new OUI

scheme” in the Isilon Knowledge Base.

This issue may affect OneFS 5.5 – 6.5.5.9.

6.5.5.10

94440 The Onsite Verification Test (OVT) test incorrectly passed nodes that failed local testing. 6.5.5.10

94315 The Onsite Verification Test (OVT) failed to find errors on a SAS PHY. 6.5.5.10

93591 If an NFS client was holding a lock on a file and disconnected unexpectedly, the cluster did

not properly release the lock.

6.5.5.10

92582 The Onsite Verification Test (OVT) could falsely report failure of the fan control board on a

node.

6.5.5.10

95431 A memory leak in SMB 1.0 caused the lwiod process to crash. 6.5.5.10

95408 Some iSCSI threads could be orphaned or stranded, and clients unable to connect to a LUN. 6.5.5.10

95392 SMB 1.0 packets could be truncated and connections lost due to the frame being flagged as a

malformed packet.

6.5.5.10

95309 Clients failed when attempting to connect to more than four iSCSI LUNs. 6.5.5.10

94708 Users mounted via NFSv4 and using a non-Active Directory Kerberos server were not being

recognized in the form of user@realm.

6.5.5.10

94662 SMB clients who were moving files and creating hard links could not change or execute files

in directories to which they did not have write permission.

6.5.5.10

94619 NFSv4 kernel crashes. 6.5.5.10

93979 Multi-homed clients could request a file lock which was then granted to an incorrect IP

address.

6.5.5.10

93674 NDMP was unnecessarily backing up hardlinks for ADS alternative data stream) files. 6.5.5.10

93645 Modifying entries on Microsoft NTFS Alternate Data Streams (ADS) did not trigger an

incremental backup. Incremental backups, however, were being performed for files with

ADS. The files were not backed up properly only if the entries were modified instead of the

data.

6.5.5.10

93591 When an NFS client locked a file and then disconnected unexpectedly, the cluster did not

properly release the file lock. When the client remounted, it could not open the locked file

6.5.5.10

93141 The default domain was handled incorrectly when using the assume-default-domain setting. 6.5.5.10

93056 Incremental jobs run by the Isi_vol_copy command failed in phase IV and the following

message was logged: bad entry: not marked REMOVED.

For more information, go to support.emc.com and search for “Patch to resolve an issue

where an isi_vol_copy incremental job fails in phase IV for OneFS 6.5.5.2 - 6.5.5.6.”

6.5.5.10



93032 If SMB 2.0 security signing was enabled on the cluster but not required, some clients using

SMB 1.0 were denied access to files.

6.5.5.10

93257 The isi smb file list command did not display multi-byte file names. Multi-byte

character sets include Chinese, Japanese, and Hebrew.

6.5.5.10

92813 In an extremely rare condition, NFS connections over UDP could cause a node restart. 6.5.5.10

92700 By default, client-side SMB writes waited 30 seconds for an Oplock break response. If no

response was received within that time, the client timed out.

6.5.5.10

88432 Some backup application programs might have failed when processing the node based file

history information sent by the NDMP daemon during an incremental backup session.

6.5.5.10

94990 Under certain circumstances, such as deleting the Snapshot Delete job in order to allow the

TreeDelete process to finish, the job coordinator disconnected from multiple nodes.

6.5.5.10

94949 Formatting a sysctl caused rare node restarts. 6.5.5.10

94919 The job engine runs only one worker on a running job. 6.5.5.10

94732 Under rare circumstances nodes restarted during mwdl restripe transactions. 6.5.5.10

94408 Selecting a date range for AVScan records would show no results and log a stack trace. 6.5.5.10

95743 The isi_avscan daemon (isi_avscan_d) crashes when processing files, ADS (Alternative Data

Streams) or directories containing embedded characters that matched ‘printf’ format

specifiers.

6.5.5.10

91863 A rare failure of the lsassd process lead to temporary interruptions of Active Directory

authentication. Affects OneFS 6.5.5 – 6.5.5.8.

6.5.5.9

92746 As delivered, alerts for high input voltage were set at 250 VAC (Warning) and 255 VAC

(Critical). Acceptable voltage fluctuations in European energy environments might vary from

that, causing spurious alerts. Affects OneFS 6.5.5 – 6.5.5.8.

6.5.5.9

93856 Exclusive create operations could fail under both NFSv3 and NFSv4 when IP addresses were

being moved from node to node by the SmartConnect service (IP failover).

6.5.5.9

93681 The Onsite Verification Test (OVT) reported a false failure on the BIOS configuration check of

S200 and X200 nodes.

6.5.5.8

93249 The Power Management interface requested an IP address through DHCP, which violates site

security guidelines at many sites.

6.5.5.8

93177 A rare node restart caused by the USB stack could occur. 6.5.5.8

91839 The OneFS web administration interface incorrectly displayed the status of 2 port

aggregations when four 1 GB Ethernet ports were present on a node.

Affected OneFS 6.5.4 through OneFS 6.5.5.7.

6.5.5.8

93407 OneFS would not allow a single path to be exported over NFS using multiple authentication

methods.

6.5.5.8

93096 An infrequent problem with the lwiod process in environments using SMB 2.0 could cause it

to restart, dropping client connections.

6.5.5.8

92751 Clients were unable to open files with names of more than 34 characters on SMB shares. File

creation operations failed with an error message: An unexpected error is keeping you

from creating the file, referencing Error Ox800700EA.

6.5.5.8



92646 The NTP (Network Time Protocol) daemon, running at real-time priority, could cause nodes

to momentarily split from the cluster.

6.5.5.8

93696

91861

92297

HDFS clients could not list directories with file names containing colons, as might occur in a

directory shared between HDFS and NFS.

6.5.5.8

92952 HDFS clients could not process or manipulate files with non-UTF8 names. 6.5.5.8

93163 Malformed password or group entries caused the lsassd process to fail. 6.5.5.8

93818 Users pressing TAB to auto-complete the isi network modify subnet command fragment

with either - - add-dsr-addrs or - -remove-dsr-addrs does not work as expected.

6.5.5.8

93611 During an upgrade, if the user specified a path to the installation image that contained an

embedded space, the upgrade would fail.

6.5.5.8

93316 The OneFS alert and notification mechanism failed to send alerts in a timely fashion if node 1

of the cluster lost external connectivity.

6.5.5.8

92876 Alerts about failed boot drives were being sent at "Warn" importance rather than the correct

"Critical" level.

6.5.5.8

91907 Battery voltage readings included incorrect values injected by software. 6.5.5.7

92642 In rare cases, if a node restarted while an NFS client was holding file locks on it, the

outstanding file locks could be left in a non-removable state.

6.5.5.7

92284 Changing ownership of a file or directory with a NULL discretionary access control list (DACL)

caused a node restart.

6.5.5.7

91907 Battery voltage readings included incorrect values injected by software. 6.5.5.7

92409 An invalid NDMP user name for authentication might have caused the NDMP server to crash. 6.5.5.7

91131 DMA might have detected an incorrect mover record count during an NDMP tape copy and

then failed the operation. In addition, during an NDMP tape copy or a 3-way restoration,

insufficient bytes might have been moved to target.

6.5.5.7

91081 NDMP backups could quit unexpectedly if a tape seek failed. 6.5.5.7

90570 Data might not have been restored when the original path in the nlist was NULL. 6.5.5.7

91177 Flexnet incorrectly applied static routes to the parent interface instead of a VLAN interface.

Routes in the affected VLAN then were inaccessible until manually added to the correct

interface.

6.5.5.7

90467 Precedence of share permissions allowed a root client to have write access even when the

NFS export is exported as read-only. Affects OneFS 6.5.5 – 6.5.5.6.

6.5.5.7

81239 Under certain circumstances, nodes would continuously update their SmartConnect

configuration and the cluster could not maintain client NFS connections.

6.5.5.7

92646 Behavior by the NTP daemon running at real-time priority could cause a cluster to enter a

split state.

6.5.5.7

92389 Chown operations from HPUX clients over NFSv3 could fail. 6.5.5.7



92175 The lwiod process (associated with SMB/CIFS services for UNIX-based clients) locked up

when trying to create a directory or file if the client did not specify a file type. The node

stopped accepting further SMB client connections.

6.5.5.7

91911 SMB file creation with a Mandatory Integrity Control access control entry (ACE) failed due to

unknown ACE type.

6.5.5.7

89861 During authentication with Active Directory, if the cluster’s clock was ahead of the client’s

clock, clients could have received STATUS_LOGON_FAILURE and could have been

erroneously denied access to an SMB share.

6.5.5.7

91974 Under some unusual circumstances, moving a file or saving it in a text editor could overwrite

a WORM-committed file.

6.5.5.7

91923 The job FlexprotectLin leaked memory when starting or resuming. 6.5.5.7

92026 Interactive queries to the OneFS event and alert messaging process could be slow or could

time out when a large number of events were processed. When the event coalescer fails, the

processing of events from cluster nodes could be delayed while the coalescer was restarted.

Under high load, the isi_celog_coalescer process can crash after running out of memory.

6.5.5.7

91449 An isi_vol_copy job could hang during phase IV of an incremental backup. This occurred

when processing a directory containing millions of files that were being updated while the

directory was being processed.

6.5.5.6

90716 A race condition in the NDMP process could cause files in directories to contained only zero-

byte files – such as hardlinks, sub-directories, and softlinks – to be backed up twice.

6.5.5.6

90581 In OneFS 6.5.5.3 – 6.5.5.5 token-based incremental backups were improperly processed and

a level 0 backup was performed instead.

6.5.5.6

90090 The Onsite Verification Test (OVT) disk speed test incorrectly failed healthy drives 6.5.5.6

90170 When a SCSI controller performed a SCSI device probe while an expander was under heavy

I/O load, the controller might have lost track of some drives. The isi dev command then

erroneously reported that drive bays in the node were EMPTY.

6.5.5.6

90578 A firmware update failed, returning the following error:

LsiMpsFirmware._update: update failed: error=256 output: isi_mpsutil:

driver gave status 0003

6.5.5.6

90617

90619

Depending on the node model, disk drive resets were handled improperly. This prevented

some drives in some nodes from being smartfailed and caused other drives in other nodes to

be smartfailed unnecessarily.

6.5.5.6

90815 Updating the bootflash firmware on an 8 GB Sandisk drive failed. 6.5.5.6

88577 The ForceGen1 feature was enabled by default on some Hitachi SATA drives, reducing the

drive link rate between the drive and the expander from 3 Gbps or 6 Gbps — depending on

the drive model — to 1.5 Gbps.

For more information, go to support.emc.com and search for “Node access is sluggish and

logs report link rates are lower than expected.”

6.5.5.6

91172 In OneFS 6.5 – 6.5.5.5, if the isi set command was run at the same time as a job that

included a restripe operation, and then a drive failed, some files were improperly protected.

For more information, see KB 3578 in the Isilon Knowledge Base.

6.5.5.6



90498 When snapshot creation failed by design to avoid a potential deadlock, in most cases the

snapshot was retried immediately and was successfully created but the following error was

repeatedly logged: Failed to create snapshot.

6.5.5.6

90456 Under some circumstances, a restriping job that was preempted by a job with a higher

priority could leave a file’s metadata unprotected. For more information, see KB 3578 in the

Isilon Knowledge Base.

6.5.5.6

84921 HDFS read connections were not distributed evenly across nodes in the cluster. 6.5.5.6

86795 HDFS processing hung when the lsassd service was under heavy load. 6.5.5.6

87473 The isi_hdfs_d daemon started to send data to a client but closed the connection before all

the data was sent. Clients reported errors containing text similar to the following:

Status FAILED java.io.IOException: All datanodes 10.7.185.91:8021 are bad.

Aborting...

6.5.5.6

87732 Unresponsive nodes were blacklisted for a longer period of time than necessary, affecting

performance.

6.5.5.6

88160 The isi_hdfs_d service crashed during group changes. 6.5.5.6

88969 Authentication occasionally failed when a high number of connections were initiated at the

same time.

6.5.5.6

90329 If hdfs-root was set to a directory with an enforcement quota with a hard threshold enabled,

HDFS did not honor the quota.

6.5.5.6

87041 All job failure alerts were set to Critical regardless of the job. 6.5.5.6

89778 Jobs were handled at a slower rate than expected. This was most noticeable when deleting

snapshot data from 'deleted' or expired snapshots.

6.5.5.6

89819 A group change, for example adding a drive or node to the cluster, caused the integrity scan

to fail.

6.5.5.6

90691 Flexprotect failed if it encountered a file that had no valid inodes, preventing the re-

protection of other data.

6.5.5.6

90410 On Solaris Sparc systems that required support for the format_unit command, the

command would fail with an error similar to the following:

isi_iscsi_d: Unsupported SCSI command: 0x4 len 0x0

6.5.5.6

89219 Clients were unable to maintain connections to iSCSI LUNs from Solaris Sparc clients. 6.5.5.6

87145 The isi_iscsi_d process failed when an iSCSI LUN was written to at the same time that a large

number of read operations were taking place.

6.5.5.6

91808 Kerberos servers using Heimdal rather than MIT Kerberos sign packets incorrectly. 6.5.5.6

91490 Files cannot be created on SMB clients when using a Group Policy Object (GPO) to create the

files; the following error is returned: STATUS_INVALID_ACL (0xc0000077).

6.5.5.6

91009 A memory leak in the lsassd process causes it to crash in workflows that include the use of

home directories.

6.5.5.6



90881 When connected to an isilon SMB share, Mac OS X 10.7 clients experienced one of the

following problems:

The Finder does not display color labels or other metadata created by the current

user or by other users.

The Finder displayed a newly-created color label or other metadata for a split second

and then the label or metadata disappeared.

6.5.5.6

90539 When a node is shut down or restarted and the NFS server does not wait until all

outstanding requests have received their responses before disconnecting from the client,

unexpected errors occurred. For example, a file create operation might return an EEXIST

error because the operation succeeded on the node that was shut down but no response

was returned to the client.

6.5.5.6

90058 The lwiod process uses 100% of the CPU on a node when accessing a file whose name

contains a date stamp with the following pattern:

@GMT-YYYY.MM.DD-HH.II.SS'

For example, “[email protected]”.

6.5.5.6

89856 A memory leak in the lsassd process might cause the lsassd process to run out of memory

and eventually crash in workflows that include high numbers of machine accounts.

6.5.5.6

89714 The following NFS-related settings that were added to the syctl.conf file are not correctly

migrated during an upgrade from OneFS 6.0.x or earlier to OneFS 6.5.0 through 6.5.5.5:

vfs.nfsrv.async

vfs.nfsrv.do_32bit_fileid

vfs.nfsrv.do_readdirplus

vfs.nfsrv.macos_maxfsize

vfs.nfsrv.readdirplus_prefetch

vfs.nfsrv.sync_response

6.5.5.6

87135 The upgrade process fails to add the NFS site-default rule entries to the file

/ifs/.ifsvar/modules/nfs/nfs_default.xml. Exports cannot be viewed, edited, or added using

the OneFS web administration interface and the default site rules cannot be viewed or

edited from the OneFS command line interface.

Affects upgrades from OneFS 6.0.x and earlier to OneFS 6.5.5.0 through 6.5.5.4.

6.5.5.6

86283 A locking issue can occur when a large number—60 or more—of Red Hat Enterprise Linux

(RHEL) 6.1 clients access the same file.

6.5.5.6

86434 Under some circumstances an NFS export doesn’t honor client restrictions if the sole client

or netgroup name does not resolve.

6.5.5.6

85853 Node under heavy NFS load panics due to NFS lock management errors. 6.5.5.6

87145 Under rare circumstances, the isi_iscsi_d process fails when an iSCSI LUN is written to at the

same time that a large number of read operations are taking place.

6.5.5.6

86591 After joining an S200, X200, or 108NL node to a cluster consisting of mixed node types, the

node's LCD panel was unresponsive.

6.5.5.6

89153 Configuration changes that were applied to an SMB share from the command line interface

were overwritten with default values when the share was accessed from the OneFS web

administration interface.

6.5.5.6



89705 The wrong options were configured in the Permissions Policies section when the Balanced

or Windows only Environment settings were selected in the OneFS web administration

interface. For more information, go to support.emc.com and search for “Selecting Balanced

or Windows only Environment settings in the Isilon web administration interface, doesn't

configure the settings as expected in OneFS 6.5.2 and later.”

6.5.5.6

90471 The OneFS alert and messaging service incorrectly expired events that have been

acknowledged or ended, therefore the job engine history reports may become inaccurate.

6.5.5.6

89402 A node restart during a group change caused a BUF_TIMELOCK: Waited more than 300

seconds for lock error to be logged.

6.5.5.6

87978 LUNs larger than 8 TB in size could not be created. 6.5.5.5

88682 Closed iSCSI sessions continued to pass data, causing the iSCSI process to crash and

disconnecting clients from iSCSI LUNs.

6.5.5.5

87941 The Onsite Verification Test (OVT) failed on nodes with an LSI2008SAS2-24 controller that

was also updated to Isilon firmware package 7.1.

6.5.5.5

87663 The ATA driver truncated drive serial numbers to 8 digits, negatively impacting drive

identification and troubleshooting.

6.5.5.5

86557 Under rare circumstances, when the isi set concurrent command was used, some files

might have been improperly protected. Files were reprotected when the next restriping job

was run.

6.5.5.5

88380 The statistics displayed for coalesced random writes in InsightIQ (or returned from the

isi statistics command) were inaccurate.

6.5.5.5

88619 In rare cases, when a quota with hard enforcements was violated, snapshots could not be

taken for an extended period of time, even though the system was not under significant

load, causing snapshot failure and node panics.

For more information, go to support.emc.com and search for “In rare cases, snapshots fail

when the hard threshold of an enforcement quota is exceeded.”

6.5.5.5

88402 A race condition occurring between the backup reader and backup writer when handling a 0

byte file caused the backup to fail.

6.5.5.5

88403 If an NDMP job was aborted, the NDMP process restarted unexpectedly or had to be

manually restarted.

6.5.5.5

88422 The NDMP process ran out of memory and then wrote core files or issued an error stating

that it failed to allocate memory.

6.5.5.5

88424 An NDMP backup or restore job could fail for no obvious reason if the isi_archive process ran

out of memory. No error message would be logged.

6.5.5.5

88430 Due to memory corruption, NDMP server crashed when NDMP_CONFIG_GET_SCSI_INFO or

NDMP_CONFIG_GET_TAPE_INFO NDMP messages are processed.

6.5.5.5

88431 After a file was restored, the UF_DOS_NOINDEX file attribute flag was not restored and the

file might then be indexed.

6.5.5.5

88432 Some backup applications failed to process the node-based file history information sent by

the NDMP daemon during an incremental backup session.

6.5.5.5



88088 The Owner attribute of a shared file or directory is not returned if NTFS ACL support is

disabled on the share, causing Windows Explorer to crash when the Customize tab was

selected in the Properties window of the shared file or folder.

6.5.5.5

88118 Simultaneously copying many files to the cluster over SMB 2.0 fails from Windows Vista or

Windows 2008r1 clients.

6.5.5.5

88319 A valid directory search over SMB that uses a pattern that contains multiple wildcards

doesn’t return any files or returns fewer files than it should.

6.5.5.5

88496 A memory leak occurs in user and group handling code, causing node restarts. 6.5.5.5

88671 Network shares cannot be mounted if the domain user name is entered following the form

“[email protected]”.

6.5.5.5

89064 The lwiod process writes core files and restarts due to a bug in notify error handling that is

encountered when process resources are exhausted, causing clients to be disconnected.

6.5.5.5

87966 When using the OneFS web administration interface to query for users on a trusted domain,

the operation fails if the domain name is entered in either lower or mixed case. In addition,

The webui_webware.log file might contain the following error:

Unable to get Kerberos ticket for administrator.

6.5.5.5

88004 When Cygwin is used to create a hard link to a file, the target file is replaced by the hard link. 6.5.5.5

87154 NFS export processing never completes during large export refresh operations. 6.5.5.5

87171 The offline files and folders feature does not work on Windows 7 and Windows Vista clients

connected over SMB 2.0. The issue is restricted to shares that contain a group or user that

has permissions set to None.

6.5.5.5

87565 On busy systems with a large number of SMB connections per node, the lwiod process might

deadlock.

6.5.5.5

87647 Under some circumstances a file name operation that relies on a relative file path can cause

the lwiod process to crash, disconnecting clients from the cluster.

6.5.5.5

87958 A memory leak in the lsassd process causes the process to exit abnormally. 6.5.5.5

86303 When a subdirectory within a directory assigned to a SyncIQ policy was moved out of the

parent directory after the initial sync, and then changes were made to the subdirectory,

subsequent attempts to run the policy failed.

For more information, go to support.emc.com and search for “SyncIQ: Operation failed while

trying to detect all directory entry changes.”

6.5.5.5

87388 SyncIQ policies that exclude or include several cluster directories did not run. 6.5.5.5

87981 Setting the max_reports per policy option to 0 configured OneFS to retain an unlimited

number of reports until the reports expired, which is 365 days by default.

6.5.5.5

88755 The statistical gathering process isi_stats_d incorrectly monitored external interfaces. 6.5.5.5

86672 A memory leak in the 10GigE driver caused node restarts. 6.5.5.5

87532 When you configured DNS for Active Directory through the OneFS web administration

interface or the command-line interface, a domain name was rejected when the name

contained a digit after the last decimal point.

6.5.5.5



87045 Nodes might have restarted when policies that force drive selection are combined with a

directory that is smaller than the WDL (width device list) and that has global namespace

acceleration (GNA) enabled, which caused nodes to restart following a software watchdog

induced restart.

6.5.5.4

79435 In rare instances, automatically taking a disk out of service because of failures could cause a

node to restart.

6.5.5.4

78580 Corrected data checksum calculations.

Although generally self-correcting, the incorrectly calculated checksums produced symptoms

identical to filesystem corruption, and extensive investigation was required to ensure that

filesystem integrity was maintained.

6.5.5.4

79791 In very rare cases, specific files could not be repaired by a FlexProtect job due to silent

failures in a previous FlexProtect job that was triggered by rebalancing work items between

nodes. While this problem was extremely uncommon, it could result in unreadable files. The

change in this release ensured that FlexProtect successfully reprotected all blocks in a file.

6.5.5.4

79225

78889

79398

Node reports data mismatch failures. 6.5.5.4

79732 Choosing Merge the new permissions with the existing ACL setting on the Advanced >> ACL

Policies page resulted in a new ACE being added to files with existing ACLs on every chmod

change. This had the potential for causing an ACL to expand to an unmanageable size.

6.5.5.4

78666 In rare cases, the umount process triggered a race condition on a node. 6.5.5.4

78794 In a very specific workflow, small contiguous writes within the same protection group could

have potentially resulted in a corrupt snapshot.

6.5.5.4

79513

79576

79631

Under certain conditions, while writing data on a snapshot version of a file, the data CRC was

not written.

6.5.5.4

79577 Snapshot reports could falsely reduce the reported size of snapshots over 32 TB. 6.5.5.4

41548 SMB clients could traverse directories when the ACL did not specifically grant the user

traverse permission.

6.5.5.4

77401 In rare circumstances, an SSD would not immediately be recognized as an SSD for layout

purposes.

6.5.5.4

79474 Restoration of files runs without errors, but the timestamps of the restored files are

incorrect. The restored files have the time stamp of when the restore was run.

6.5.5.4

78683 Node reports the following error when attempting to connect to the lsassd process after a

group change: Couldn't open connection to lsass: ERROR_FILE_NOT_FOUND.

6.5.5.4

79068 In certain SMB workflows, Windows Explorer on Windows 7 and Windows 2008 clients crash

when attempting to view a file owner that has an unmappable SID.

6.5.5.4

78976 When attempting to restore files greater than 68 GB, the restore fails with the following

error: Fatal Error reading archive: Unrecognized archive format.

6.5.5.4

77825 DAR file restorations via NDMP report missing files due to mishandling how files with hard

links are reported.

6.5.5.4



77799 In certain cases, restoring a backup to a new location results in nlink failures due to hard

links to non-regular files being treated as copies of the file during recovery.

6.5.5.4

78609 In certain workflows, a node panics and restarts if multiple NFS connections are idle for an

extended amount of time.

6.5.5.4

79087 NFS server failed to send an EOF on READ response. 6.5.5.4

79206 In a specific case, after upgrading to OneFS 6.5.3, 64-bit file IDs are sent to NFS clients that

expected 32-bit file IDs. This is due to the order in which the upgrade script processed

certain tasks.

6.5.5.4

79579 When creating a file over NFS in workflows with inheritable ACLs, OneFS ignores the passed

in mode.

6.5.5.4

78813 When the cluster has a system lock on a file during a credentials check, it blocks other access

to the file while waiting for the credential server to return. If the lock is on an NFS export

directory, this can cause the cluster to appear unresponsive.

6.5.5.4

79085 In certain cases, Mac OSX clients receive an error similar to the following when attempting a

mount request on the cluster via NFSv4:

mount_nfs -o vers=4,rw 10.53.180.91:/ifs /Volumes/myvol mount_nfs: can't

mount /ifs from 10.53.180.91 onto /Volumes/myvol: Unknown error: 10014.

6.5.5.4

79410 NFSv4 clients that have read file permissions are unable to access read-only files on an NFSv4

export.

6.5.5.4

78861 As a result of a memory leak in the lwiod process when performing frequent read/write

operations on small files, the Microsoft IIS Media Center returns HTTP 500 errors to clients

OneFS is used as the IIS document root.

6.5.5.4

79659 Windows XP and Vista clients are unable to see all available snapshots. 6.5.5.4

78313 Cannot map alternate ftp root for LDAP/NIS users. 6.5.5.4

77698 Upgrade of the vsftpd process from version 2.2.2 to version 2.3.4 addresses an issue where

File eXchange Protocol (FXP) fails in OneFS version 6.5.3.

6.5.5.4

78980 NDMP backup job fails and retries after reaching 9TB of a backup. In some cases, the backup

fails with an unexpected NDMP error message.

6.5.5.4

75988 NDMP does not return an error message if DAR is used and the nlist for a restore contains

file paths longer than 1024 characters.

6.5.5.4

78096 In a rare situation, a security scan on a node caused the isi_iscsi_d process to write core files. 6.5.5.4

77954 In a rare case, NFS export definition results in a hash collision and continuous node restarts. 6.5.5.4

77910 Potential for deadlock when writing the NFS exports file. 6.5.5.4

76479 In certain workflows, the isi nfs exports command took more than 20 minutes to

process an NFS export.

6.5.5.4

77753 NFSv3 writes failed for files greater than 5.5 GB. 6.5.5.4

78210 In some cases, NFS connections appear unresponsive. 6.5.5.4

79027 The isi nfs export modify command fails and writes core files when adding a client. 6.5.5.4



78001

78386

78496

SMB client connections are closed when duplicate multiplex IDs (MID) are encountered. 6.5.5.4

78285 When attempting to save a file via Avid Media Composer, the export dialog will repeatedly

prompt the user to choose an export location.

6.5.5.4

78322 The Run As Root share permission does not allow use of the COPYALL option in Robocopy. 6.5.5.4

78144 The Previous Versions tab doesn't display previous file version in Windows 7 or Windows XP

(64-bit).

6.5.5.4

78761 SMB clients cannot rename folders without read access to the root file system of a share. 6.5.5.4

80119 iSCSI targets are only visible on a maximum of six subnets. 6.5.5.4

78377 In some cases, if the --skip_bb_hash option is enabled on the source, the target was unable

to connect and the sync job failed.

6.5.5.4

79496 The isi_evaluate_provision_drive process consumed 100% CPU. 6.5.5.4

78641 In certain configurations, a node could incorrectly generate an “External network link down”

alert.

6.5.5.4

78201 Under certain conditions, the isi_vol_copy tool can fail when it encounters a symbolic link

with a long path name.

6.5.5.4

79340 The isi_quota_report_d process hangs without notification. 6.5.5.4

79279 Under certain conditions, after running for several days, the FSA job could fail on a constraint

error.

6.5.5.4

78367 Variables entered into the subject portion of a quota email template remained in place,

rather than being replaced.

6.5.5.4

59195 The isi_vol_copy process could fail when migrating a dataset that contained more than 15

million files.

6.5.5.4

80096 The isi_vol_copy process could fail when encountering a directory with the same inode of a

previously deleted file.

6.5.5.4

78068 In certain workflows, nodes with 10GigE NICs set at 1500 MTU experienced decreased

throughput.

6.5.5.4

79560 Drive stall events could cause the MultiScan job to start. 6.5.5.4

64976 The isi tape rescan command halted, forcing a restart of the accelerator. 6.5.5.4

85906 A deadlock could occur when two processes that were contending for a lock restarted at the

same time.

6.5.5.3

56310 Nodes were not placed in safe read-only mode before you upgraded the firmware on the

IB/NVRAM card.

6.5.5.3

73785 The WORM information that was returned by the isi worm info command did not reflect an

override retention date set on the WORM root directory.

6.5.5.3

74098 The WORM retention date on a file was not always the same as the time returned by the

file's atime value.

6.5.5.3

74320 Running the isi worm info command on the /ifs directory resulted in a traceback. 6.5.5.3



85906 A deadlock could occur when two processes that were contending for a lock restarted at the

same time.

6.5.5.3

56310 Nodes were not placed in safe read-only mode before you upgraded the firmware on the

IB/NVRAM card.

6.5.5.3

73785 The WORM information that was returned by the isi worm info command did not reflect an

override retention date set on the WORM root directory.

6.5.5.3

74098 The WORM retention date on a file was not always the same as the time returned by the

file's atime value.

6.5.5.3

74320 Running the isi worm info command on the /ifs directory resulted in a traceback. 6.5.5.3

82318 Jobs that were deleted and then re-created with the same file name failed. 6.5.5.3

83477 The isi_hdfs_d process did not detect that the IP address pool had changed. 6.5.5.3

85705 Some jobs failed unless task trackers were configured to run with more memory than

required by native Java HDFS servers.

6.5.5.3

86097 Jobs failed if communication with the node being written to was lost. 6.5.5.3

86802 Concurrent jobs sometimes failed with the error LeaseExpiredException: No valid

lease….

6.5.5.3

86811 In some cases, when a boot disk I/O operation timed out, no error was returned. 6.5.5.3

86415 Nodes with10GigE interfaces that are also in an IPv6 pool intermittently restarted. 6.5.5.3

86860 A node might boot off the last known good root partition if the boot disks were incorrectly

cabled.

6.5.5.3

87048 Firmware updates could not be applied if boot drives were connected to the onboard SATA

controller.

6.5.5.3

87166 Accelerator nodes failed the OneFS Onsite Verification Test (OVT) disk speed test. 6.5.5.3

74047 Changing the link aggregation mode while VLAN tagging was enabled could cause a node to

restart, although the affected node would retain the correct setting after restarting.

6.5.5.3

74220 At times the system might not have issued a sensor update over the internal monitoring bus

due to an internal resource contention. In those instances, multiple SES-busy error messages

might have been logged.

6.5.5.3

86218 Backups to Netapp VTL failed to complete because the tape driver wrote two file marks.

Although Netapp VTL is not supported, this change improved compatibility but did not

guarantee that Netapp VTL will work.

6.5.5.3

86401 NDMP Trace log data might have been lost. 6.5.5.3

86541 Files with the setuid or setgid bit set had the bit reset upon restoration. This caused the files

to adopt the invoking user’s uid or gid.

6.5.5.3

69854 NFSv4 clients may be unable to access certain files on the node which have invalid utf-8

filenames. Lookup requests will display an error such as: cannot access XXXX: invalid

argument where XXXX is the filename and may display unprintable characters.

6.5.5.3



71335 Fibre Channel tape and media change devices connected to a backup accelerator are

returned by NDMP daemons running on all nodes in response to NDMP tape and SCSI query

requests.

6.5.5.3

72679 Unsupported SMB share configuration on the /ifs share may not correctly raise errors on

upgrade.

6.5.5.3

73073 NFSv4 clients do not mount when different security parameters are used for exports. 6.5.5.3

74133 Upgrade fails to migrate local users from OneFS 5.5.2.

Local users and groups are now retained when upgrading from OneFS 5.5.2.

6.5.5.3

76737 User mapper incorrectly matched users. A wildcard (*) in a User Mapper Rule will match not

only UNIX users but also Active Directory users. This may cause rules using only the wildcard

to be skipped. In particular, the rule "* &= DOMAIN\*" would have no effect on users within

DOMAIN. All other rules are unaffected by this issue.

6.5.5.3

76190 During the first incremental upgrade sync following an upgrade to 6.5/SyncIQ 3.0, SyncIQ

incorrectly double-counted some files as skipped, resulting in an inaccurate report.

6.5.5.3

71989 When adding a new user, the OneFS web administration interface allowed invalid characters

in new usernames.

6.5.5.3

73112 The Message display on the Recent Job History page reports user-cancelled jobs as being

cancelled by the system.

6.5.5.3

73969 Cloning a shadow LUN to a normal LUN from the OneFS web administration interface results

in an error.

6.5.5.3

74119 The OneFS web administration interface did not display the Filesystem drop-down menu

when accessed with the Internet Explorer 7 browser.

6.5.5.3

67358 Drives were marked as “replace” before a FlexProtect job completed. 6.5.5.3

74598 Email notification for NIS users were sent to <username>@<first search domain> regardless

of the domain mapping rules configured on the SmartQuotas >> Email Notification Mapping

page.

6.5.5.3

75107 Running isi_promptsupport with no options, and then confirming ‘yes’ to enable

SupportIQ, removed the primary contact information.

6.5.5.3

75424 The OneFS pre-upgrade configuration check did not account for the OneFS case insensitive

lookup parameter.

6.5.5.3

75379 The local user Guest could not be enabled or disabled using the OneFS web administration

interface.

6.5.5.3

69703 Very rare hardware problems could cause mis-registration of data used for alerts, resulting in

false alerts for properly functioning hardware.

6.5.5.3

71781 The isi_iscsi_d process might have failed when the cluster went into read only mode. 6.5.5.3

72334 The message “param_text_add buffer to smallmessage” occasionally appeared in the file

/var/log/messages.

6.5.5.3

72507 In the brief period before a node join is complete, an event might have been generated

reporting that the node is offline.

6.5.5.3

73283 Adding a drive would cancel long running integrity scan jobs. 6.5.5.3



73884 iSCSI reservation unlocks could result in failure of the isi_iscsi_d process. 6.5.5.3

85162 No event notification was sent when the SAS controller encountered a problem. 6.5.5.2

85399 Onsite Verification Test (OVT) recorded a false error testing memory on X400 and NL400

platforms.

6.5.5.2

75354

76130

In random cases, the front panel on X200/S200 node was recognized but the temperature

sensor returned no data.

6.5.5.2

84728 The isi_vol_copy utility failed when it encountered a hardlink that pointed to a softlink. 6.5.5.2

85546 The isi_vol_copy utility occasionally stopped responding during migration of a very large

dataset, for example one containing thousands of sub-directories.

6.5.5.2

85697 The maximum number of file handles (sysctl kern.maxfiles) in OneFS 6.5.5.0 and 6.5.5.1 was

miscalculated, resulting in an unreasonably low number (16424).

6.5.5.2

75566 Quotas could become corrupted when the user or group status for a cached SID was

unknown.

6.5.5.2

66550 The isi_flush process took more time to complete on nodes with large amounts of RAM. 6.5.5.2

75196

75715

In rare cases, a lock contention resulted in a node restart. 6.5.5.2

75229 In certain workflows, a cluster became unresponsive to client requests after you ran the

isi snapshot alias command.

6.5.5.2

73672 Nodes hung on restarting while waiting for the umount process. 6.5.5.2

84153 If a customer used ESX 4 with iSCSI datastores and upgrades to ESX5, the iSCSI datastores

could not be mounted.

6.5.5.2

84626 During a DAR (Direct Access Restore), if a proper header was not found in the backup

stream, the restore would fail.

6.5.5.2

84627 During a 3-way DAR (Direct Access Restore), restorations were started but never completed. 6.5.5.2

84628 Backup code did not properly handle broken connections to the remote mover in a 3-way

backup, resulting in a failed restoration.

6.5.5.2

84708 A renamed directory might have been backed up during an incremental backup even if no

files were changed.

6.5.5.2

84874 Three-way NDMP backups failed because the NDMP software was not ignoring loopback

interfaces, therefore sending unusable IP addresses to the backup device, causing backups to

fail.

6.5.5.2

85098 The Direct Access Restore (DAR) code did not restore some files if the name field was

specified.

6.5.5.2

85100 The restoration of a special file (a file containing metadata for a block device) could fail. 6.5.5.2

85101 When restore failed to recover file metadata, an uninformative error was logged. 6.5.5.2

85104 NDMP failed to properly restore socket file attributes. 6.5.5.2

85105 ADS files associated with changed files were not properly backed up during an incremental

backup.

6.5.5.2



85106 An incremental backup of a root directory that has been renamed might have only backed up

changed files within the directory instead of the entire directory.

6.5.5.2

85107 A backup that is aborted would not close a session and new backup jobs were not prevented

from starting.

6.5.5.2

85194 Statistics reported for backups did not correctly account for hard linked files, counting the

first instance of the file as a hard link rather than a file.

6.5.5.2

85261 During a Direct Access Restore (DAR), the tape offsets for hard links to special files were not

restored.

6.5.5.2

85583 Upon restarting a Backup Accelerator, the file /var/log/messages was filled with

cam_periph_error TIMEOUT messages.

6.5.5.2

70851 Unable to mount SMB share as guest user from OS X. 6.5.5.2

75348 In previous OneFS releases, attempts to set a NULL value with the isi auth config

modify command would result in a traceback.

6.5.5.2

75533 Unable to login with anonymous user via ftp. 6.5.5.2

75550 On upgrade, lsassd isn’t listed for netgroups in the nsswitch.conf file. 6.5.5.2

76391 Listing users from large LDAP directory slow under load. 6.5.5.2

76748 Listing users from large LDAP directory cause certain LDAP servers to crash. 6.5.5.2

76951 When viewing users in an LDAP tree the lsassd service will restart. 6.5.5.2

73171 Old Winbind mappings are re-imported to the cluster on node add. This causes issues with

existing SID to UID/GID mappings.

6.5.5.2

73862 Authentication mappings cannot access groups by name or principal. The isi auth mapping

command did not accept groups by name.

6.5.5.2

75970 A permissions issue related to lsassd. 6.5.5.2

74569 Attempts to restore a tape backup via NDMP fail if the backup contained hard links. 6.5.5.2

74858 Backup via NDMP fail when it encounters a filename with a max length of 255 chars. 6.5.5.2

75029 Backups via NDMP fail if files with timestamps older than 1/1/1970 are encountered. 6.5.5.2

75054 Backup of a hard link to a file larger than 20 MB failed. 6.5.5.2

75259 Wrong file size being reported in NDMP history causes DMA catalogs to display incorrect file

sizes.

6.5.5.2

76006 In certain workflows, the default RPC idle connection timeout of 360 seconds results in NFS

client connections being reset unexpectedly.

6.5.5.2

74004 A transient condition occurs when enumerating a large number of open files locally on a

node using isi smb file list command causing the enumeration to stop early with the

message ERROR_NETNAME_DELETED.

6.5.5.2

74209 Incorrect responses to change notifications cancellations over SMB2 can cause IIS to stop

responding when trying to read/write the web.config file.

6.5.5.2

75112 Wildcard matching for files via SMB is inconsistent. 6.5.5.2



75267 Attaching files with alternate data streams (ADS) to a Microsoft Outlook email returned an

operation failed message.

6.5.5.2

75416 Unable to access the Properties dialog box in the File System Explorer. 6.5.5.2

75426 SMB shares with “ImpersonateGuest = never” allow Guest access even when the Guest user

is enabled.

6.5.5.2

75435 When trying to join an AD domain, the join fails and the following message is returned:

ERROR: Domain join timed out. Please retry.

6.5.5.2

76596 In rare circumstances, a client disconnecting during SMB negotiation could cause the server

to become unresponsive.

6.5.5.2

76864 On Windows XP and Windows 2003 SP2 clients using Shadow Copy Emulation, snapshots do

not display properly in the Previous Versions tab.

6.5.5.2

76865 Using NTLM in OS X 10.5 resulted in an incomplete access token. 6.5.5.2

76968 Mac OS X 10.5.8 clients may have stalled and failed when attempting to access large shares. 6.5.5.2

73549 Occasionally there would be more entries in the Previous Versions tab when using SMB to

display snapshots from a Windows client.

6.5.5.2

74318 In a specific case, an lsassd core file was found after upgrading to OneFS v6.5.0.1. 6.5.5.2

76313 A memory leak in lsassd could lead to a node panic. 6.5.5.2

75269 The process 'make kernel' from NFSv3 mount on node returning 'Operation not supported'

has been resolved.

6.5.5.2

74418 SMB client that gets disconnected may have been unable to reconnect. 6.5.5.2

74286 After a group change, lwrestart.py may have become stuck in shutdown and unable to

restart.

6.5.5.2

83837 SyncIQ would write core dump files when diff_sync was enabled on the SyncIQ policy and

the process encountered extended attributes on a file or directory.

6.5.5.2

84963 SyncIQ jobs failed and the isi_migr_sworker process failed, leaving core dump files on the

target cluster. In addition, a message similar to the following appeared in the

/var/log/messages file on the target:

isi_migr_sworker: *** FAILED ASSERTION dlin != 0 @

/usr/src/isilon/bin/isi_migrate/sworker/stf_transfer.c:1002: Missing update

dlin for slin.

6.5.5.2

72890 File throttling with SyncIQ could burst above the promised limit for short periods of time. 6.5.5.2

75560 A 500 Error page might have resulted when changing a password.. 6.5.5.2

76044 Provisioning rules could not be configured for the ext-5/ext-6 interfaces. 6.5.5.2

76172 SmartConnect responded incorrectly to IPv6 DNS queries. 6.5.5.2

75619 Network provisioning rules did not allow provisioning by 10GigE nodes if there were X, S, or

NL-Series nodes already in the cluster.

6.5.5.2

75198 A high number of node_offline events were generated, causing memory errors. 6.5.5.2



76651 Smartfailing an accelerator node that was previously the master node resulted in an invalid

array.xml file.

6.5.5.2

72794 Isilon for vCenter jobs might have run slowly when several were running simultaneously. 6.5.5.2

75421 Debugging information appeared in the logs when running isi job start. 6.5.5.2

76060 Jobs run manually using the isi job start command failed with the message: Resource

temporarily unavailable.

6.5.5.2

75794 Upgrade process halted while waiting for a halted system process. 6.5.5.2

76997 The front panel display did not clear the “Which cluster to join” message during the join

process.

6.5.5.2

72779 Disk drive display update was not refreshed when switching between nodes. 6.5.5.2

76575 The isi_lcd_d process failed during node boot. 6.5.5.2

76036 The isi_stats_d process failed on an S200 node with a 6 GigE interfaces. 6.5.5.2

11834 Cluster becomes non-responsive when NIS server is unavailable. 6.5.5.1

69140 Network authorization/authentication lookup statistics are now available. 6.5.5.1

69502 Degradation in the performance of NFSv3 namespace operations in the NFS server has been

resolved.

6.5.5.1

69616 LDAP netgroups were not supported in NFS exports. NFS exports can now include netgroups

found in LDAP.

6.5.5.1

70162 Non-export NFS options such as sysctl and non-standard external config files were not

retained when upgrading. This issue has been resolved.

6.5.5.1

72597 SMB service could crash when there were spurious client disconnects. This issue has been

resolved.

6.5.5.1

72757 UID and GID ranges could not be modified via the command line. 6.5.5.1

73055 Periodic machine password changes can cause brief authentication outages. 6.5.5.1

73117 Servers configured for Kerberos crashed when a client connected with krb5p authentication. 6.5.5.1

73413 A race condition occured over SMB that caused files to be held open internally for a brief

period after it had been reported closed, leading to unexpected sharing violations when the

client tries to quickly reopen the file.

6.5.5.1

74217 When Microsoft IIS was configured to use virtual directories backed by an Isilon cluster over

SMB, web.config could not be read from or written to, returning HTTP Error 500.19.

6.5.5.1

71736 Excessive CPU utilization was reported incorrectly when running SyncIQ on certain nodes. 6.5.5.1

71872 SyncIQ generated an excessive number of failed policy events from each node. 6.5.5.1

72048 The OneFS web administration interface allowed invalid characters for group and password

file names.

6.5.5.1

72434 Clicking a bar within the Client Connections graph may have taken displayed the wrong

Node Status page.

6.5.5.1



73659 The Bandwidth chart under SyncIQ Performance showed incorrect Y-axis values. 6.5.5.1

74210 Switching SMB security mode from Anonymous to User did not switch the impersonate-

guest parameter to match.

6.5.5.1

47548 The OneFS web administration interface showed failover and rebalance policies for statically

allocated addresses.

6.5.5.1

66332 When upgrading the OneFS operating system, override protection settings on individual files

were reset to their default values.

6.5.5.1

69621 Some statistics queries erroneously failed with a "remote query" error. 6.5.5.1

72524 Events were being coalesced by unrelated events. 6.5.5.1

72777 iSCSI could become unresponsive and eventually fail due to logical unit resets. 6.5.5.1

72910 Alerts generated on nodes without SMTP connectivity failed to send email notifications. 6.5.5.1

73432 Due to allocation patterns on a heavily loaded system, the statistics database

(persistence.db) could become excessively fragmented. This issue has been resolved in the

release shown, however, the resolution does not apply to older databases.

6.5.5.1

73705 The Latency standard deviation column was missing in output from the isi statistics

command.

6.5.5.1

74200 A running SmartPools job occasionally failed while scanning a directory that belonged to a

snapshot that was being deleted.

6.5.5.1



Upgrading OneFS

This section discusses upgrading from an earlier version of OneFS to the current version.

Upgrade prerequisites

Upgrading to the current version of OneFS 6.5.5 is supported from OneFS 5.5 or later. Upgrading from a version of OneFS earlier than 5.5 can result in data loss. If you are running a version of OneFS earlier than 5.5, contact Isilon Technical Support. Before you upgrade, do the following:

Verify that you are running a version of OneFS that can be upgraded to this release. Verify that you are running Isilon hardware that is compatible with this release. For a list of

compatible hardware, see the OneFS 6.5.5 Release Notes.

Isilon highly recommends that if you are upgrading a cluster running any version of OneFS older than 6.5, you run a pre-upgrade check.

Isilon also highly recommends that before an upgrade, you run a pre-installation script to verify that you are not using unsupported SMB parameters. This script verifies that the SMB configurations in your installation are compatible with this version of OneFS. Only supported SMB configurations are permitted to upgrade. A patch that contains the script is available from the Isilon Technical Support.

When the pre-installation script finds an unsupported configuration, the process stops and displays instructions on troubleshooting the issue. Running the script that is included in the patch before you start an upgrade helps avoid an interruption because of incompatible SMB configurations.

Determine whether you want to perform a rolling upgrade or a simultaneous upgrade. Rolling upgrades are supported from the following OneFS versions:

OneFS 6.5.1

OneFS 6.5.2

OneFS 6.5.3

OneFS 6.5.4

OneFS 6.5.5

Important: In OneFS 6.5.4.0 through OneFS 6.5.4.12 and OneFS 6.5.5.1, under some conditions, the

cluster might attempt to write data to a node that is in read-only mode. This behavior can cause data loss

when you perform a rolling upgrade from a cluster that is running an affected OneFS version. For more

information, go to support.emc.com and search for “Write failures after a node transitions to read-only

mode and risk of data loss during a controlled shutdown.”

Simultaneous upgrades are supported from OneFS 5.5 or later.

For additional details about rolling and simultaneous upgrades, see the OneFS 6.5.5 Release Notes.



When determining the best time to perform an upgrade, if you are upgrading from OneFS 5.5, the upgrade job is performed as a background process. This upgrade job might cause long delays when it creates or removes files in directories that contain 1,000,000 entries or more–the larger the directory, the greater the delay. If your cluster’s directories contain 1,000,000 entries or more, consider scheduling the upgrade during off hours.

Depending on the amount of data on the cluster, the upgrade process can take several hours. If the process fails, contact Isilon Technical Support at 1-866-276-0723 or [email protected].

Downloading the OneFS image file

Information about the most recent and recommended release of OneFS can be found here.

1. Download the OneFS 6.5.5.x installation image from the EMC Support website: https://support.emc.com/downloads/15209_Isilon-OneFS

2. To confirm the download was successful: a. From the command line run the command md5 <filename> where <filename> is the full name

of the installation image you downloaded. b. Compare the results to the Checksum link below the download link.

3. Open a secure shell (SSH) connection to the node and log on with the root account. 4. Copy the downloaded installation image to the /ifs/data directory. 5. Upgrade using the OneFS web administration interface. For details, see Upgrade using the OneFS

web administration interface below. - OR - Upgrade from the CLI (command-line interface). For details, see Upgrade using the command-line interface below.

6. Verify the installation. For details, see Upgrade Verification below. 7. From the command line, run the isi stat command. 8. Verify that all nodes report OK.

mailto:[email protected]

https://support.emc.com/emc14001799_OneFS-Current-Release-Versions.sol

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



Upgrade using the OneFS web administration interface

1. Log in to the cluster from the OneFS web administration interface.

2. On the Cluster menu, point to Cluster Management, and then click Upgrade OneFS.

3. Browse to the location of the installation image to install and then click Submit. The cluster

checks the cluster and displays the upgrade options.

Note: You must specify the fully qualified path, including the file name, of the .gz installation file. Failure to specify a fully qualified path will result in an error message indicating that the image failed to load.

4. In the Upgrade Mode section, click one of the following upgrade modes:

Rolling upgrade: Upgrades and restarts each node in the cluster individually to continue to allow client access to the cluster during the upgrade process. Rolling upgrades are not available for all OneFS versions. Simultaneous upgrade: Upgrades and restarts all nodes in the cluster at the same time. When the nodes are restarting, the cluster will be unavailable to client connections.

5. For rolling upgrades, specify how client TCP connections to the nodes will be terminated during

the rolling upgrade process:

a. To immediately terminate all client connections to the nodes before the nodes are upgraded, click Immediately terminate TCP connections.

b. To allow all client connections to complete their workflows, click Wait for TCP connections to terminate, and then, in the Wait time box, type an integer that represents how long to wait in seconds, minutes, hours, days, weeks, or months. If a TCP connection does not terminate on its own after the specified amount of time has elapsed, the system terminates the connection.

6. For rolling upgrades, specify whether you want to manually confirm each node restart during the

rolling upgrade process:

a. To display a notification and a restart prompt when each upgraded node is ready to be restarted, click Confirm before rebooting nodes. During the upgrade process, individual notification messages will prompt you to restart each node.

b. To automatically restart each upgraded node with no prompt, click Reboot nodes without confirmation.



7. Click Yes to begin the upgrade process. The system might display several confirmation messages

related to operating-system version upgrades; you must confirm these messages in order to

continue the upgrade process.

8. The upgrade process completes, the cluster restarts, and then the OneFS web administration interface login page appears.

Upgrade using the command-line interface

You can upgrade OneFS through the command-line interface. Note that rolling upgrades are not available for all versions of OneFS.

Rolling upgrade

A rolling upgrade upgrades and then restarts each node in the cluster individually.

1. Open a secure shell (SSH) connection to the node and log on with the root account. 2. From a command line, run isi update --rolling. 3. To specify a timeout period before restarting the node, use the --drain-time=<time> flag.

This option gives TCP clients time to disconnect before the node restarts.

The default timeout is zero seconds. To specify a time unit other than seconds, append one of the following letters to the timeout value:

m: minutes

h: hours

d: days

w: weeks

4. To optionally display a notification prompt before each node restarts, use the --manual flag. The default value is no prompt.

Simultaneous upgrade

A simultaneous upgrade restarts all the nodes in the cluster at the same time.

1. Run the command isi update, and then press ENTER.

2. Type the fully qualified path, including the file name, to the installation image:

/ifs/data/OneFS_v<version>_Install.tar.gz, where <version> is the number of the OneFS version you

are installing. Then press ENTER.

3. When the installer prompts you to continue the upgrade process, type yes and then press ENTER.

The upgrade process begins, and the cluster displays the status of the upgrade process.



4. When prompted, type yes and the press ENTER.

The upgrade process completes, and the cluster restarts.

Upgrade Verification

1. Run the command isi stat.

2. Verify that all nodes report OK.

Note: If you are upgrading from OneFS 5.5, an upgrade restripe process starts after several

minutes. You can monitor the upgrade restripe process with the command isi stat or by

viewing status information in the OneFS web administration interface. If the process fails, contact

EMC Technical Support .

3. Remove or delete the file /ifs/data/OneFS_v<version>_Install.tar.gz, where <version> is the number

of the OneFS version you’re installing.

4. Run the isi_gather_info command and then upload the returned log file to the Isilon FTP

server.



Contact Support

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

Telephone Support: United States: 800-782-4362 (800-SVC-4EMC) Canada: 800-543-4782 Worldwide: +1-508-497-7901 Additional worldwide access numbers

EMC Isilon Telephone Support:

From the main menu, select Option 2 (All Hardware Products); then Option 1 (All Hardware Products except AX).

Help with Online Support Tools:

For questions specific to EMC Online Support registration, access, or site association: [email protected]

https://support.emc.com/

http://www.emc.com/collateral/contact-us/h4165-csc-phonelist-ho.pdf

mailto:[email protected]

Documents

Docu46725 OneFS Version 6.5.5.19 Release Notes