5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
@etr.eric Thank you for posting the question. Could you please tell me what are your PE and PC versions? This issue occurs if there is version incompatibility between PE and PC. We have had similar issue in the past. We tried upgrading the PC. Please do let me know respective versions.
@DavidTeague @Claus Jan @DennisFFM @tanel @Joe_E @storm @Steven2018 @jeffearl Thank you for sharing your questions here, I apologize you had to wait it so long. To address your issue, the issue in specific was earlier resolved using a workaround which resulted in many other issues. But this issue is now resolved in AOS 5.11 and 5.10.5. The following cases are addressed by these changes: Allow images to be deleted if it owned by an older PC from a new PC. If image is an orphan image (which means just present on PC) it can be deleted. If image is on a PE and is not owned by that PE - The image can either be deleted by unregistering the PE or migrating image to new PC and deleting from PC. Recommendation to customers having this problem is to upgrade to 5.10.5 or later and then attempt to clean up the images again. As an alternative when an upgrade is not possible or the issue remains post upgrade is to use a new script has been developed by engineering. This script will be part of AO
@Uaifo Thank you for your question. The issue that you are facing could be because of the license_key.txt that would be generated on your cluster however not applied. I am attaching a KB article below for your reference. This should help you solve your problem. The article explains the exact issue that you are facing. Please find the attached link- https://portal.nutanix.com/#/page/kbs/details?targetId=kA0600000008eynCAA Please let me know if you still have any questions. Thank you, Sneha
@themingsen Defrag is only useful on physical systems with single disks. When using Nutanix, your data blocks may reside on multiple disks on multiple nodes across the cluster. Rearranging these blocks is done by Nutanix background jobs and Windows do not have control over the arrangement or contiguousness of these blocks. I hope this answers your question.
@themingsen Thank you for posting your question. We do have an internal KB that jots down steps for defragmenting vdisks, hence maybe was not accessible to you. Defragmentation process is complicated and we do not allow customers to do on their own but only under Support guidance as there are some high number of caveats present. Storage features applied on a container on a Nutanix cluster may cause vdiskblockmap metadata for the VM disk(s) to become heavily fragmented. This usually happens over a period of time for VMs with deduplication on disk and/or on VMs with workloads with small I/O overwrites and regular DR snapshots. High vdiskblockmap fragmentation can reduce performance across a number of operations. If deduplication is used, then a high fragmentation is expected. In that case, do not proceed as defragmenting deduplicated vdisks means that deduplication savings are being removed. Ideally to perform defragmentation: Ensure that cluster is running AOS >= 5.10.6 or >= 5.1
@nishantpanchal Yes, additionally there are some more requirements which you could have a look at in the above link that I shared.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
