Nutanix Files Storage Container

  • 29 April 2019
  • 5 replies

Why Files Storage container is system managed? What all different purposes this container is used for?

Best answer by proyoung 29 April 2019, 13:45

View original

This topic has been closed for comments

5 replies

Userlevel 3
Badge +1
Nutanix Files creates a container for every file server instance you create. A file server must have its own dedicated container. Since this is dedicated to a single File Server instance, it is marked as system managed which means you will not be able to modify the settings.

´╗┐Some other useful information :-
  1. Once a Nutanix Files cluster is deleted, the container can be deleted from Prism UI. This is applicable from AOS 5.10.1 onward.
  2. A Nutanix Files storage container should not be used to store Non-Nutanix Files data.
  3. Enabling de-duplication on a Nutanix Files storage container does not yield results. Hence, it should not be enabled on a Nutanix Files cluster storage in use, unless it is recommended by Nutanix. Nutanix has introduced a new NCC health check ( NCC 3.7.1) file_server_container_check to flag this. It verifies if On-Disk Dedup is enabled on the container used by Nutanix Files.
  4. On a Nutanix storage container, compression is enabled by default.
I hope this information is useful.
Badge +1
I cannot delete the container after deleting the File Server, still says it is system managed. What am i missing?
Userlevel 3
Badge +1
Hi, sorry about the late reply. I am not sure what AOS version you are on. System managed flag is removed from container once the file server is deleted post AOS version 5.10.1. This can be done using ncli command. Are you familiar and comfortable with ncli command line options?
Is it possible to choose which Storage Pool Nutanix Files creates the containers on? I don't see that in the workflow but we have different pools of disk in our cluster.
Userlevel 3
Badge +1
Well as of now it's by default. However, this a good feature to be added. As workaround, you may try to create a container with the name you want to use for your container in the SP.
For instance, pre-stage your container on the desired SP.

Let me know if this works.