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?
Best answer by Sudhir9View original
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
Please let us know if you see any errors in modifying the container from the command line.
I’ve read that article and unfortunately the command specified does not work for this share;
using nfs_ls i could see that it has a bunch of files/folders named “counters-xxx”
is there any way to fix this?
Please try this:
@Sudhir9 that worked,
an hour after the container was set to rf3 the extent group warning disappeared.