Quarterly Release Notes 

Qumulo Core 2.14.0 
October 30, 2019 
 
Welcome to the 2.14.0 Quarterly Release Notes! Below you’ll find a recap of all the features, 
improvements, and bug fixes we’ve included since version 2.13.0 of Qumulo Core, our exciting last 
quarterly release. Once you install this version, feel free to sit back and relax for the next three months 
(give or take) until our next quarterly release.  

Quarterly Release Highlights 

With our refreshed, head-turning Qumulo Core Web UI chock-full of new analytics and data, the 
much-requested and anticipated release of our new SMB 3.0 support and encryption, new RBAC 
Administrators role option, and our exciting new Snapshot Policy Replication feature that adds another 
layer to your backup strategy, this quarterly release is by far our best one yet!  
 
That’s just the beginning. We understand that speed matters around here, so we not only improved 
rebalance performance to make data re-allocation faster than ever, but we’ve also tweaked our 
upgrade system to handle background processes quicker so you don’t have to take extended breaks 
between multiple upgrades. You’ll also find SMB write leasing support, even more upgrade 
enhancements to ensure installing the latest release is just plain simple, and much, much, (we mean it) 
more.  
 
Read on to check out all the exciting improvements and enhancements we've made since the last 
quarterly release of Qumulo Core. 

NEW Revamped User Experience 

Talk about a makeover! Since our last quarterly release, we’ve been working ‘round the clock to 
improve your experience with the Qumulo Core Web UI by not only offering you more, but making sure 
we look good while we do it. From new colors and fonts to even more at data at your fingertips, here’s 
everything you can expect to find in this quarterly release of Qumulo Core. 
 
● We freed up our canvas (you’ll see why in a minute) by removing the Onboarding tasks section 
from the right-hand pane of the dashboard for new clusters. 

 
© 2019 Qumulo, Inc.  
Contact Us   
 
 
 

● You get a widget and y ​ ou​ get a widget! We’ve added a plethora of new widgets to our 
Dashboard that bring all the details you need and want front and center. Here’s the full list: 
○ The O ​ verview widget​ was added to the top of the Dashboard so that you don’t have to 
hunt for the answer to that age old question of “where did my space go?”. And while we 
were there, we made some changes to how the section resizes to ensure anyone 
viewing the UI on a smaller screen enjoys the same experience. 
○ The C ​ lient Connect Distribution widget​ in the Client Activity section provides a deep 
dive of the connections across your cluster displaying the NFS, SMB, and the total 
number of connections per node in both numerical and bar graph form.  
○ The M ​ ost Active Clients widget​ highlights the busiest clients according to throughput 
and IOPs and includes details for reads, writes, and the IP address of the client in the 
Client Activity section.  
○ The T ​ op Directory Changes widget​ in the Capacity Trends section of the Qumulo Core 
Dashboard outlines which directory on your cluster has had the biggest change 
(increase or decrease!) over the last 72 hours so that you can easily track and manage 
your storage at a granular level. Keep in mind that the data displayed in this widget 
begins populating once the cluster finishes upgrading and requires 72 hours to gather 
all the data it requires.  
○ The R ​ ead Throughput Distribution​ and W ​ rite Throughput Distribution widgets 
include your cluster’s throughput for the last 24 hours (at most!) as well as a “Current” 
line that indicates the throughput in real time.  
● Speaking of the Dashboard, we reworked the Cluster Overview section as well to provide a 
more complete picture of your cluster’s overall health at a glance. You’ll find all the same info 
from the old one (including some new arrivals), but bigger and in more detail! 
○ Cluster Usage​: Here you’ll find a color-coded pie chart and metrics on the consumption 
and availability of your storage—dark blue for Data, light blue for Metadata, green for 
Snapshots, and white for Available free space. 
○ Number of Nodes​: Displays the number of active nodes in your cluster. 
○ Protection Status​: Indicates drive failure protection.  
○ File and Directory Count​: Highlights the total file and directory count and displays the 
current change rate (increase or decrease) calculated every 5 seconds. 
● We renamed the ​Users and Groups​ page to L ​ ocal Users and Groups​. 
● We moved the​ Local Users and Groups​, R ​ ole Management​, ​Active Directory​, and L​ DAP​ from 
their old location under the S ​ haring​ menu to a new home under the C ​ luster​ menu.  
● We restyled the message display bar across the top of the Dashboard to better match the 
overall look-and-feel of our new and improved UI.  

 
© 2019 Qumulo, Inc.  
Contact Us   
 
 
 

● And we added some new messages to boot! You’ll now find a new ​Unconfigured Node 
message in the UI when new nodes are detected, the U ​ nable to connect to the cluster 
message in the event that your browser can’t connect to Qumulo Core, and the ​Cannot 
Upgrade​ message on the Software Upgrade page if an attempt fails.  
● We added support to dismiss Replication job errors from the Replication Relationship 
table—simply click ‘Dismiss error’ alongside the relationship in question. 
● We’ve changed the enable/disable radio button for ​Map Local User/Group IDs to Associated 
NFS IDs​ to a single ​Enabled​ checkbox on the Create and Edit Replication page. 
● We’ve added a link to the Relationship Details page on the A ​ ctions​ menu (found on the far 
right of the relationship listing) so it is always accessible rather than just during a Replication 
job. 
● We’ve updated the Relationship Details page to include information about any linked Snapshot 
policies enabled, including a table with the linked policies and any snapshots queued for 
replication. 
● And last but not least, we fine-tuned a few more UI elements that are small but still worth 
mentioning:  
● The error message displayed when users take an action they do not have permission for 
has been changed from “You must be an administrator to perform this action.” to “You 
do not have sufficient privileges to perform this action.” 
● The snapshot policy “Summary” column is now split into “Schedule” and “Delete Time” 
to better section the data. 
● The UI displayed via a node’s VGA output when using a kiosk (a.k.a., crash cart) will 
now close after 3 minutes if it is left idle instead of running persistently to conserve 
resources. To restart the UI, you can simply click the “Start the kiosk” button that is 
displayed. 
● Large numbers on the Replication page will be broken up via commas (e.g., ‘1,234,567’ 
instead of ‘1234567’) to not only improve readability, but ensure consistency with other 
pages.  
 
To see the fruits of our labors, head on over to Qumulo Care and check out the ​Qumulo Core 
Dashboard​ article. 

NEW SMB 3.0 Support and Encryption 

For those of you that have been patiently waiting for SMB 3.0 support with Qumulo, the time has 
come! Qumulo Core 2.14.0 is the first release that will use SMB 3.0 by default, no configuration 
required. Better yet, any clients that don’t support SMB 3.0 will automatically fall back to SMB 2.1, so 
all your bases are covered! 
 

 
© 2019 Qumulo, Inc.  
Contact Us   
 
 
 

While we were at it, we decided to add support for SMB 3.0 traffic encryption as well. SMB 3.0 
introduces encryption to the SMB protocol that can be enabled (disabled by default) at a cluster-wide 
level or at a per-share level—it’s your choice! Depending on your environment and workflow, you can 
configure per-share level encryption instead of the cluster-wide setting so that a client can use 
encryption against a single share that requires it and connect to a share that does not in the same 
session. While these settings can be controlled, SMB clients can still decide whether or not to encrypt 
even when encryption is not required.  

Want to hear more? Check out ​SMB3 Encryption with Qumulo Core​ in Qumulo Care!  

NEW RBAC Administrators Role 

We’ve heard your feedback loud and clear that having the option to assign admin privileges on your 
cluster would make managing storage with Qumulo that much easier. With the release of 2.14.0, you 
can now grant full cluster access to any users or groups (AD and local) of your choosing with the new 
administrators role option. Simply head on over to the ​Role Management​ page or use the new q ​ q
auth_assign_role​ command with the user or group credentials (UID, AD username, local username, 
group name, etc.) to grant admin rights and share the responsibility of cluster management. Keep in 
mind that a new administrator will need to re-log in or experience a session timeout for the change to 
take effect. 

To get the full scoop, head on over to Qumulo Care and check out the A
​ ssign Administrators Role to 
Users and Groups​ article for more info. 

NEW Snapshot Policy Replication 

We here at Qumulo take your data seriously and are always looking into new ways to keep it safe. 
That’s why we jumped on the opportunity to take our awesome Replication feature and gave it a 
hearty dose of Snapshot enhancement! The new Snapshot Policy Replication feature allows you to add 
an extra layer of backup to your disaster recovery scenario by ensuring that the data replicated to your 
backup cluster can be captured and stored in a snapshot. Talk about a winning combo!  
 
Snapshot Policy Replication allows you to link up to ten existing Snapshot policies to a Replication 
relationship. Once you establish the link, Replication will take care of the rest by replicating future 
snapshots taken by those policies to its target directory. Once each replication job completes, a new 
snapshot of the target directory is taken to ensure that the data is consistent on both the source and 
target clusters and that a snapshot history of the file changes exists. You can specify how long you 
wish to keep the snapshots, either manually or by setting it to use the same expiration as is configured 
in the Snapshot policy.  
 

 
© 2019 Qumulo, Inc.  
Contact Us   
 
 
 

NOTE:​ When a Snapshot policy is linked to a relationship, snapshots taken by those policies will be 
immediately locked for the Replication relationship and can only be removed by configuring their 
expiration accordingly or unlinking the policy from the Replication relationship. 
 
Thirsty for more details? We thought so! Head on over to our ​Replication: Snapshot Policy Replication 
article on Qumulo Care to find out more. 

Feature Enhancements 
Rebalance Performance Improvements  
Speed matters! We’ve increased the performance of rebalance planning so that any and all capacity 
expansions to your cluster can be accepted and utilized even sooner. Now when you add a new node 
or disk to your cluster, we will start reallocating data faster than we have in the past and the new total 
capacity will display quicker as a result. While clusters of all shapes and sizes will see a difference, 
those of you with larger clusters (​raw​ capacity, not used capacity) can expect the greatest impact from 
this change. 

SMB Write Leasing 

Most applications don’t bother thinking about how many bytes of data to write to disk and when to do 
so—they leave that up to the OS, which handles this in the background. While Qumulo Core has 
allowed client operating systems to cache r​ eads​ over SMB for quite some time, the 2.14.0 release 
allows clients to also cache ​writes​, so that the client OS can combine write requests and send them 
over the network in larger increments. This means greater efficiency when writing data over a network, 
which in turn means better performance for you! This new​ S ​ MB capability is enabled by default in 
Qumulo Core 2.14.0 and does not require any configuration on clients or your cluster. It requires 
Windows 7 and later—Mac OS and Linux support it to some degree, but Windows sees the largest 
performance improvement. 

SMB Enhancements 
Clients will get the maximum access allowed on a particular file at the time of opening a new handle 
with a CREATE or EDIT operation. What does this mean for you? You may see some reduced IOPS 
from clients since there is no need to query access attributes separately on your cluster. Note this will 
depend on your current workflow and environment and is not guaranteed. Additionally, we added 
added support for hard links over SMB so that you can now create, rename, unlink and query info on a 
file with multiple links. Note that replacing an existing hard link with a symlink and replacing an 
existing file/directory/symlink/hard link with a hard link are not supported at this time. 

 
© 2019 Qumulo, Inc.  
Contact Us   
 
 
 

In order to move closer to our full Unicode support for SMB (coming soon!), we needed to upgrade the 
on-disk representation of SMB shares. With this exciting step, it’s possible that previously unique 
share names could conflict with one another (e.g., Share name “share_ß”, id 6, and “share_ss”, id 5, 
don’t conflict in an ASCII case-insensitive manner but do in a strict case-insensitive manner) following 
this upgrade. In this scenario, one share would be placed into the new on-disk format (e.g., “share_ss”) 
as-is, and the other would be re-named to “:UPGRADE-CONFLICT_6:share_ß”. As you know, we 
share by default around here. We don’t expect any of you to hit this in the field with your clusters, but 
feel it’s important to keep you in the know of any potential event.  

NOTE: ​If you haven’t already, enable Cloud-Based Monitoring so that our team can notify you if an 
SMB share name conflict occurs on your cluster. For additional details on this proactive monitoring 
feature, check out the ​Qumulo’s Cloud-Based Monitoring​ article available on Qumulo Care. 

Replication Job Progress Enhancements 

If it seems like nearly every release brings some enhancement or improvement to our Replication 
feature, it’s not just your imagination! In 2.14.0, we’ve adjusted the formula used to calculate the 
Estimated Remaining Time to include the expected number of unchanged files. What does this mean 
for you? Improved accuracy for the calculation, especially when replicating a mix of both changed and 
unchanged files. That’s not the only Replication improvement you’ll find. 

To ensure you can easily track the progress of your Replication job, we’ve updated the Data section of 
the Replication Job Details page to include not only the files written, but the number of files deleted as 
well. Additionally, we’ve changed the scheduling of how often we report the number of files and bytes 
deleted during a replication job on your cluster. Instead of the prior behavior of refreshing the data only 
after the entire directory is deleted, you’ll now see the metrics update regularly so that you can better 
track the progress of your Replication jobs.  

Last, but certainly not least, we tweaked the timestamp on target replication snapshots so that it’s 
equal to the source snapshot that was successfully replicated instead of the time that replication 
completed and captured the target snapshot. Why the change? The snapshot on the target contains 
the data at the time the source snapshot was taken, so now this timestamp reflects the recovery point 
timestamp to use with failover and failback workflows.  

For details on our replication feature, head on over to Qumulo Care and check out the R ​ eplication: 
Continuous Replication with 2.11.2 and above​ and R ​ eplication: Failover and Failback with 2.12.0 and 
above​ articles to find out more. 

 
© 2019 Qumulo, Inc.  
Contact Us   
 
 
 

Snapshots Improvements  
If you regularly take advantage of Qumulo’s snapshot feature, take note! NFS exports can now be 
mounted with a sub-export path that includes the .snapshot directory. If the export /​ files​ exists on a 
cluster, you can now easily use ​files/.snapshot/42_my_snap​ to mount a snapshot of the NFS export’s 
root directory. If your export subdirectory path includes a symlink, you will not be able to mount the 
NFS export, since the symlink cannot traverse to a .snapshot directory. Keep in mind that creating an 
NFS export that directly exports a snapshot is still not supported at this time. 
 
While we’re on the topic of Snapshots, the directory path of an existing snapshot policy can no longer 
be changed using the API, CLI, or Web UI. Why? Due to the fact that a single directory and schedule 
are permanently linked in the Snapshot policy, it was clear that removing the ability to change the 
directory path was the right choice. If you do need to change the directory path, you’ll need to delete 
the existing policy and create a new policy for the new directory instead. Additionally, if you rename a 
directory that is currently associated with a snapshot policy, the policy will use the directory’s new 
name. 

For more info, check out the R​ ecommended NFS Mount Options​ and S
​ napshots: Per-Directory 
Snapshots​ articles available on Qumulo Care. 

Audit Log Error Enhancements 

When it comes to logs, you can never have too much info. That’s why we added s ​ hare_connect 
entries in the Audit Logs to outline the connection attempts to an SMB share. Note that the extra ID 
field will contain the share ID and the extra name field will contain the share name in the log. And 
that’s not the only Audit Log change you’ll find. Instead of displaying a generic n
​ tstatus_error​, we 
now provide the specific ​ntstatus​ code corresponding to the values shown on the public M ​ icrosoft 
Errors​ page for SMB users. That way you have you more visibility into the details about the ​ntstatus 
codes and reasoning behind it. Refer to our Q ​ umulo Core Audit Logging​ article on Qumulo Care for full 
details surrounding this great feature! 

FTP Improvements 
If you’ve been wishing you could configure FTP home directories for your Active Directory users, this is 
the release for you! Alongside the existing support for configuring local home directories, you’ll now be 
able to manage home directories for AD users as well via the new qq commands available in this 
release. Simply use the new q​ q identity_attributes_set [IDENTITY] --home-directory [HOME
DIRECTORY]​ to set the AD user’s home directory, and then verify the change with the new ​qq
identity_attributes_get [IDENTITY] ​command.  

 
© 2019 Qumulo, Inc.  
Contact Us   
 
 
 

And since we were already making changes, we added support for asynchronous FTP data channels in 
this release; e.g., users can send ​STAT​ and S
​ IZE​ commands while a ​STOR​ command is in progress and 
will receive responses with updated information.  

See our F
​ TP in Qumulo Core​ article on Qumulo Care for more details! 

Cluster Monitoring and Upgrade Enhancements 

Upgrade Enhancements 
When it comes to upgrades, we’ve made some big strides and changes to ensure that your cluster is 
prepped and ready to complete any upgrade successfully. With that in mind, we added another item to 
our pre-flight checklist to verify that all disks are recognized in your cluster before proceeding with a 
software upgrade. To be crystal clear, we did already have a check to confirm any disk failures and 
verify that all nodes were online before starting the upgrade process. But now, in addition to any disk 
failure or node offline event, a removed or missing disk scenario will also block an upgrade attempt to 
ensure the software installation goes smoothly. 

And that’s not all! We know system upgrades can be stressful, which is why we also tweaked our 
upgrade system to handle background processes significantly faster. This means less wait time 
between back-to-back upgrades, so you can get to the next upgrade in no time! 
 
To find out more about upgrading your cluster with Qumulo, reference the Q ​ umulo Core Upgrade 
Paths​ and ​Qumulo Core Upgrades via UI​ articles to get the info you need. 

Drive Monitoring Improvements 

We constantly keep a close eye on the health of your drives to ensure the security and safety of your 
data. So you can imagine that when it came time to find a way to improve the process of how we verify 
(a.k.a, scrub) the disks in your cluster, it was a no-brainer! With the release of 2.14.0, our disk scrubber 
will now check all the hard drives on your cluster in parallel. In other words, each disk will be read and 
checked in a shorter amount of time (without using more I/O) so that we can spot any potential issues 
before they start. That way if we do see any warning signs that a drive is about to fail (or other red 
flags), we can let you know sooner rather than later.  
 
Check out the ​Qumulo Care Proactive Monitoring​ article to discover how we track drive and overall 
cluster health so that you can get help when you need it the most. 

 
© 2019 Qumulo, Inc.  
Contact Us   
 
 
 

New Cluster Monitoring Alerts  

Who doesn’t like more when it comes to monitoring the health of your cluster? With this release of 
Qumulo Core, email subscribers to Qumulo Trends alerts will now be notified if the DIMM count is 
incorrect or if IPv6 duplicate address detection failed on any given node in the cluster. And to cover all 
of our bases, we made sure that our Qumulo Care team also receives a notification from any cluster 
with Cloud-Based Monitoring enabled in the case of either event. So whether the number of DIMMs 
doesn’t match the hardware specs or a duplicate address detection failed state occurs for one or more 
IPv6 addresses, you’ll be informed to proactively take steps to ensure your cluster is at peak 
performance.   

If you haven’t already, check out the ​Qumulo Care Proactive Monitoring​ and E
​ mail Alerting with 
Qumulo Trends​ articles on Qumulo Care to find out how you can be kept in the know when it comes to 
the current health status of your cluster.  

HPE Drive Replacement Updates  

Those of you that have HPE clusters, take note! Starting with Qumulo Core 2.14.0, HPE nodes will now 
verify the firmware on any and all spare drives following swaps for bad or failed drives. If a 
replacement HPE drive has the incorrect firmware version installed, the cluster will not accept the drive 
and a banner in the Web UI will display specifying which drive is at fault so you won’t be kept in the 
dark. The upgrade process automatically checks all drives present prior to performing the upgrade, and 
will stop if any invalid firmware is detected. In this event, reach out to your friendly ​Qumulo Care​ team 
so we can get a new HPE drive with the correct firmware sent your way. 

REST API and QQ CLI Enhancements 

Out with the old and in with the new! Here’s what’s changed with Qumulo’s REST API and qq 
commands in this release. 
 
NEW QQ CLI COMMANDS 
● Introduced the​ ​qq​ a
​ uth_expand_identity ​command to expand AD and LDAP users by name, 
and distinguish between equivalent identities and group membership. 
● Created the following new SMB qq commands: 
○ qq smb_modify_settings​: configure the SMB dialects that Qumulo will negotiate. 
○ qq smb_get_settings​: display the current SMB configuration 
○ New SMB encryption field: Encryption can be configured via q​ q smb_add_share
--require-encryption {true,false}​ and modified via​ ​qq smb_mod_share
--require-encryption {true,false}

 
© 2019 Qumulo, Inc.  
Contact Us   
 
 
 

● Added the following new Replication qq commands: 

○ replication_link_snapshot_policy​: link a snapshot policy to a relationship. 
○ replication_unlink_snapshot_policy​: unlink a snapshot policy from a relationship. 
○ replication_set_snapshot_policy_replication_mode​: change the replication 
mode of a policy-linked relationship. 
○ replication_list_queued_snapshots​: list the snapshot policy snapshots queued for 
replication. 
○ replication_release_queued_snapshot​: release a snapshot policy snapshot that is 
queued for replication. 
● Added q
​ q smb_modify_settings ​and​ qq smb_get_settings​ for SMB 3.0 encryption. 
● Added q​ q auth_assign_role​, q ​ q auth_unassign_role​, and q
​ q auth_list_roles​ to 
support RBAC. 
● Added the ​qq identity_attributes_{get,set}​ commands for FTP configuration. 
 
UPDATED QQ CLI COMMANDS 
● The ​fs_list_locks ​replaced the ​qq fs_list_locks_by_file​ and 
fs_list_locks_by_client​ commands. 
● The ​qq f ​ s_acl_explain_rights​ command now automatically expands equivalent identities 
and group membership if ​Active Directory Posix Extensions​ are enabled. 
● The ​--enable-continuous-replication​ flag is now - ​ -enable-replication ​for the ​qq
replication_create_source_relationship​ command. 
● The ​--enable-continuous-replication​ flag is now - ​ -enable-replication ​for the
replication_modify_source_relationship​ command. 
● Added the ​--require encryption {true,false}​ argument to the q ​ q qq smb_add_share 
and q​ q smb_mod_share​ commands. 
● The ​qq upgrade_status​ command now includes​ is_blocked​ and​ is_blocked_reason 
fields. 
 
DEPRECATED QQ CLI COMMANDS 
● Deprecated the q
​ q get_all_related_identities​ command and replaced it with ​qq
auth_expand_identity​. 
 
NEW REST API COMMANDS 
● Added the​ /v1/auth/identity/expand​ REST endpoint 
● All replication APIs have been versioned to the v2 module. The v1 module will be removed in a 
future release. Note that most APIs are versioned because the 
continuous_replication_enabled​ field is now r ​ eplication_enabled​. 
● Added the following new replication rest endpoints: 
○ PUT/PATCH /v2/replication/source-relationships/<id>​: modify a relationship’s 
linked snapshot policies. 

 
© 2019 Qumulo, Inc.  
Contact Us   
 
 
 

○ GET /v2/replication/source-relationships/<id>/queued-snapshots/​: return 

the queued snapshots. 
○ /v2/replication/source-relationships/<id>/queued-snapshots/<epoch>​: 
remove a queued snapshot from the queue via D ​ ELETE​. 
○ POST /v2/replication/{source,target}-relationships/<id>/dismiss-erro​r:​  
clear the relationship’s ​error_from_last_job​ string. 
● Added the following new SMB REST endpoints: 
○ GET/PUT/PATCH /v1/smb/settings​: modify the SMB dialects that Qumulo will 
negotiate. 
● Added​ ​GET|PUT|PATCH /v1/smb/settings​ ​for SMB 3.0 encryption with the 
require_encryption​ field. 
● Introduced G
​ ET|PUT /v1/auth/roles/​ ​for RBAC administrators role management. 
● Added the REST endpoint ​/v1/auth/identities/$id/attributes​.  
 
UPDATED REST API COMMANDS 
● None. 
 
DEPRECATED REST API COMMANDS 
● Deprecated the /
​ v1/smb/shares​ REST endpoint. 
● Deprecated the /​ v1/nfs/shares​ REST endpoint. 

Bug Fixes 
● Fixed an issue where attempting to copy a directory with alternate data streams over SMB 
using Robocopy or Windows Explorer would fail. 
● Fixed a bug for SMB behavior to properly use case-insensitivity for symlink resolution. 
Similarly, we now properly consider case-insensitivity for named stream opens and renames.  
● Fixed a bug where SSL certificates were not validated for proxied s3 object uploads. 
● Fixed a bug so that q
​ q capacity_history_get ​requests with timestamps greater than 
9223372036854775807 now return an HTTP 400 error. 
● Fixed a bug on the Add Nodes page so that node listings now float under the cursor during 
drag and drops. 
● Made an improvement to our read-ahead prefetch logic to read sequentially from the beginning 
after reading metadata at the end of a file. 
● Fixed a bug causing the backslash (‘\’) character in filenames to be translated incorrectly over 
SMB. 
● Fixed an issue with NIC memory tuning on P-series platforms that could cause out-of-memory 
errors. 
● Fixed an issue with SMB where rare write workloads could cause a cluster event. 

 
© 2019 Qumulo, Inc.  
Contact Us   
 
 
 

● Fixed a bug in the f ​ s_file_get_attr​ API so that it now returns directory hash version too. If 
it’s not a directory, that field will be null. 
● Fixed a bug for APPE and REST commands with FTP so that failed transfers can be resumed.  
● Fixed an issue where user-defined mappings that were case-sensitive would only take effect if 
the names’ casing in the user-defined mapping matched the casings present in Active Directory 
and LDAP server. As a result, user-defined mappings have been de-duplicated to remove 
entries which differ only by case. 
● Fixed an issue so that users who are logged in to the Web UI during an upgrade will see the 
cluster version as “Unknown” at the login page until a new login session is started. 
● Fixed an issue for files that could become temporarily unavailable over SMB under rare 
circumstances to ensure timely access is restored.  
● Fixed an issue to allow SMB locking requests to succeed when a file is simultaneously accessed 
by multiple clients. 
● Fixed an issue so that querying files for SMB FileCompressionInformation indicates that the file 
is not compressed (COMPRESSION_FORMAT_NONE) instead of returning an error message.  
● Fixed an issue by upgrading from Chrome 76 to Chrome 77 on our servers to address potential 
resource consumption issues. 
● Fixed an issue so that only system services for a specific SKU will start on system boot. 
Previously, [FAILED] messages would display while the node was still booting; these messages 
will no longer display. 
● Fixed a bug that prevented a SID from a domain that has not been seen before to be added to 
an ACL via the​ / ​ v2/files/{ref}/info/acl​ API. 
● Fixed a bug that caused a quorum event when opening a file with a trailing backslash (i.e., 
\foo\bar\file.txt\) over SMB. 
● Added support for querying for SMB File Alignment Information. Qumulo returns a 
FILE_BYTE_ALIGNMENT of 0, meaning that there are no alignment requirements for the 
underlying device. 
● Fixed a bug where Qumulo Core would incorrectly update the SMB atime value for transactions 
where no such update was requested. 
● Fixed a bug on HPE clusters that could prevent quorum formation when a node was booted or 
rebooted with a missing or failed drive. 

Known Issues as of 2.14.0 

● A known bug is currently impacting NFS clients in the Red Hat/CentOS 7.6 release. If a floating 
IP fails over to another Qumulo node, the NFS client will not register this behavior, causing the 
client to hang. For additional details on this bug and proposed solution, reference the full report 
on the ​Red Hat Customer Support Portal​. 

 
© 2019 Qumulo, Inc.  
Contact Us   
 
 
 

● When using Windows 10 version 1607 and Windows Server 2016, Windows Explorer will not 
automatically refresh to reflect changes connecting to Qumulo over SMB. To fix the problem, 
download and install this u​ pdate​ from Microsoft that addresses the issue.  
● If any node in your cluster currently has a defective DIMM, you may not be able to successfully 
install releases from Qumulo Core 2.11.4 onward. Prior to upgrading, please check your node’s 
memory status by following the steps detailed in our ​Check Node DIMM Status​ article or 
contact your CSM to ensure a successful upgrade. 

Upgrade Info 
As of Qumulo Core 2.13.0, all subsequent releases will be a quarterly upgrade source so that you can 
easily upgrade directly from any incremental version (2.13.X) to any later release, up to and including 
the next quarterly X.X.0 build. No matter what version past 2.13.0 your cluster is running, you will need 
to install every quarterly release before proceeding to upgrade to a later version of Qumulo Core. To 
find out more about upgrading your cluster with Qumulo, reference the Q ​ umulo Core Upgrade Paths 
and Q​ umulo Core Upgrades via UI​ articles to get the info you need. 
 
BACK TO BACK UPGRADES: ​Before attempting to install multiple releases of Qumulo Core in an 
extended maintenance window, reach out to the ​Qumulo Care​ team for guidance on your upgrade 
path. 

Performance Characterization 
Performance data for this release is available in Q
​ umulo’s Tableau Public Workbook​. Details on how these 
performance numbers are calculated can be found in the ​Qumulo Performance Benchmarks​ article available on 
Qumulo Care. 

API 
● Be sure to visit our ​GitHub​ page to see what folks are building with the Qumulo REST API.  
● Find the latest python wrapper for our REST API h ​ ere​.  
 

What’s Supported 
● Our supported browser is Google Chrome  
● Supported clients over SMB: 
○ Mac OS X 10.13, 10.12, 10.11, 10.10 and 10.9 
○ Windows 10, 8.1, 8, and 7 

 
© 2019 Qumulo, Inc.  
Contact Us   
 
 
 

● Supported clients over NFS: 

○ Mac OS X 10.13, 10.12, 10.11, 10.10 and 10.9 
○ Linux Kernel 2.6.x, 3.x and 4.x 
● Python v 2.7.5 or later in the Python 2 family is required for our command line tools (Python 3 is 
not supported) 
● Domain functional level 2008 R2 and above (Samba DCs are not supported) 
● Qumulo Core is up to date with all Ubuntu 16.04 security updates as of August 8, 2017 

Supported Switches 
Qumulo appliances will work against any switch that meets the following criteria: 
● Enterprise grade 
● Fully non-blocking 
● Managed 
● Supports IPv6 
 
No exceptions at this time. For information on the upgrade process, reference the ​Qumulo Core 
Upgrades via UI​ article for additional details. 

 
© 2019 Qumulo, Inc.  
Contact Us