Solved

NutanixManagementShare change RF2 to RF3

  • 25 October 2020
  • 4 replies
  • 1071 views

Userlevel 2
Badge +1

Hi all,

Running AOS 5.10.5, i have changed my cluster from RF2 to RF3, 

including my main container and the “SelfServiceContainer”,

however a week after the change I’m still seeing this error regarding extent groups,

I believe that this is due to NutanixManagementShare still being RF2 (with no ability to change it, since its a systemmanaged container), or is there some other reason?

icon

Best answer by Sudhir9 26 October 2020, 08:30

View original

This topic has been closed for comments

4 replies

Userlevel 2
Badge +4

Hello @DenisF ,

Yes if there is any data in NutanixManagementShare it can cause the extent group to remain on 1. 

As described in https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v5_18:wc-cluster-fault-tolerance-update-ui-t.html you can modify NutanixManagementShare using the command line. 

 

You can confirm if there is any data in the NutanixManagementShare using the command 

nfs_ls -al 

 

Please let us know if you see any errors in modifying the container from the command line. 

Userlevel 2
Badge +1

Thanks @Sudhir9 ,

I’ve read that article and unfortunately the command specified does not work for this share;

nutanix@NTNX******:~$ ncli ctr edit name=NutanixManagementShare rf=3
Error: Storage container NutanixManagementShare is Nutanix managed system container and cannot be changed.

 

using nfs_ls i could see that it has a bunch of files/folders named “counters-xxx”

is there any way to fix this?

Userlevel 2
Badge +4

Hello @DenisF ,

Please try this:

ncli -h true
ctr update name=NutanixManagementShare rf=3 force=true

 

Userlevel 2
Badge +1

Thanks @Sudhir9  that worked,

an hour after the container was set to rf3 the extent group warning disappeared.

thanks!!