Error in configuring deduplication in container | Nutanix Community
Skip to main content
Hi all,



I have already posted this problem in other forum section but maybe it should not be there so I repost it here so that I could get an appropriate and fast answer



To summarize the problem, I am in the same situation in which I cannot enable the deduplication on HDD and I have also tried running the commands below and the result seems a little bit inadequate because I have configured the CVM RAM up to 32GB



nutanix@NTNX-13SM31320001-B-CVM:10.9.120.115:~$ allssh 'grep "for on-disk deduplication feature" ~/data/logs/stargate*'Executing grep "for on-disk deduplication feature" ~/data/logs/stargate* on the cluster================== 10.9.120.114 =================FIPS mode initializedNutanix Controller VM================== 10.9.120.115 =================FIPS mode initializedNutanix Controller VM================== 10.9.120.116 =================FIPS mode initializedNutanix Controller VM/home/nutanix/data/logs/stargate.NTNX-13SM31320001-C-CVM.nutanix.log.INFO.2016120424949.13003:W1209 01:08:28.571275 13361 stargate_cluster_state.cc:1146] The system, which has 16GB RAM and 716GB SSD, does not satisfy the minimum requirements of 24GB RAM and 300GB SSD for on-disk deduplication feature================== 10.9.120.117 =================FIPS mode initializedNutanix Controller VMnutanix@NTNX-13SM31320001-B-CVM:10.9.120.115:~$
If this is for a production system, please file a support ticket and we can help you clear that error via CLI.
Hi Jon,



This is not a production system but I have to build up the same system with customer to figure out the answer for their questions about deduplication



And I think that could be a good point if you give me some susggestion on troubleshooting on this problem.
hienle - Posting this same response on both of your open posts.



Just double checking here, did you verify that CVM 10.9.120.116 actually has 24GB+ of RAM (which you can validate with allssh "free -m")?



If so, no worries, the serial number of the system you posted (13SM31320001) has a support contract running until Februrary 20th 2017. Please file a support ticket and ask them to send you the commands from KB 2684 to clear the disable_fingerprinting setting in zeus.
Hi Jon,



Because of some unexpected reason, unlucklily I cannot create the case for this time.



By the way, below is my result from your recommendation command:



nutanix@NTNX-13SM31320001-B-CVM:10.9.120.115:~$ allssh 'free -m'Executing free -m on the cluster================== 10.9.120.114 =================FIPS mode initializedNutanix Controller VMtotal used free shared buffers cachedMem: 32240 7874 24366 0 526 3798-/+ buffers/cache: 3548 28691Swap: 0 0 0================== 10.9.120.115 =================FIPS mode initializedNutanix Controller VMtotal used free shared buffers cachedMem: 32240 7649 24590 0 526 3500-/+ buffers/cache: 3622 28617Swap: 0 0 0================== 10.9.120.116 =================FIPS mode initializedNutanix Controller VMtotal used free shared buffers cachedMem: 32240 14955 17285 0 544 3511-/+ buffers/cache: 10899 21340Swap: 0 0 0================== 10.9.120.117 =================FIPS mode initializedNutanix Controller VMtotal used free shared buffers cachedMem: 32240 12079 20161 0 541 3472-/+ buffers/cache: 8064 24175Swap: 0 0 0nutanix@NTNX-13SM31320001-B-CVM:10.9.120.115:~$
Interesting, ok, I understand. I asked our support team to reach out, as the commands to get this cleared are generally only give out by support, since they are CLI operations.



Jon
Terms & Conditions