我正忙着安装一个6节点集群，出现了一些错误或疑问。
我的环境:3块，6个节点(2个节点/块)AOS 4.6.2
一.当我创建一个新的容器，使启用Erasure编码按钮选中，错误弹出“启用EC-X将打破当前块感知!”似乎意味着ECX将禁用块级别感知?
二.我们很多人都知道，如果需要定位磁盘的物理插槽位置，您可以简单地引导该驱动器。但可能会导致功能不准确或禁用，在这种情况下，必须根据硬盘id规则(如shelf id)定位硬盘。slot/bay ID，但在prism硬件部分的DISK ID似乎是随机的/无规则的数字，我无法找到一个磁盘的物理位置。
三.当我做关于从nutanix集群中删除一个节点的测试时，一个疑问出现了:在删除节点之前，我需要还是执行存储vmotion(除了vmotion vm的)是最佳实践?我认为这两种方法的区别在于谁是数据移动者，一个是ESXI svmotion，另一个是CVM RF ?也许我完全错了，即使我选择svmotion, RF恢复还会发生吗?提前感谢你们宝贵的时间和帮助!
四.我第一次启用RF3，几天后，用户想恢复到RF2, nutanix支持这个吗?我知道我可以在线将RF2更改为RF3;
RF的另一种情况:当我使用Foundation工具图像节点时，我选择默认RF2，并选择“Can I enable RF3 support by NCLI command ?”(我注意到NCLI中有相关的命令)
类似地，我可以启用EC-X并再次禁用它吗?我想知道可以改变两次或多次的共同特征，而不是一次改变是永久的。
感谢社区朋友们!
最佳答案乔恩
RE ECX<\/b>
\nYes, ECX and block awareness do not mix. There is a long technical explanation of why, but the short of it is that the majority of customers who would use ECX wouldn't have enough physical blocks to actually enforce block awareness on ECX data (due to the different way that ECX stores blocks on disk), so we have delayed working on making the two work together as of now.
\n
\nRE Physical disk LED \/ finding a disk<\/b>
\nThe disk ID is really an \"internal\" construct, do not pay much attention to it.
\n
\nIf the LED on a disk was not working, or perhaps a HDD was 100% \"dead\" and the disk was just 100% offline, you would just simply look for the node that it is attached to (which is visibile in the Prism hardware display diagram) and go to that physical node and remove it.
\n
\nAlternatively, You could flash the LED on that node as well, which would help, OR perhaps flash all of the LED's of the disks around the dead disk, so that the dead disk stands out as \"not flashing\"
\n
\nIf there was any doubt, you would compare the serial number from the Disk in Prism to the physical one printed on the drive to double check.
\n
\nThis is the general approach for almost all storage systems.
\n
\nRE Removing a node<\/b>
\nYou do not need to svMotion anything at all. The CVM's will move the data off that node.
\n
\nEven if you did \"svMotion\" all of those VM's, you'd still have data on that CVM before it is removed from the cluster, as it is a part of the clusters overall capacity, so the svMotion literally doesn't do anything but waste time.
\n
\nJust regular vMotion the VM's to another node first, then remove the node using Prism and wait for the task to complete.
\n
\nRE RF3 to RF2 change<\/b>
\nAre you talking at the cluster level? or the container level?
\n
\nCluster level can not be changed back. I *think* the container level can be changed back, but I've never tried it. Absolute worst case, just provision another container at RF2 and storage vMotion the data.
\n
\nThat said, this question is one of those that you should really think through before arbitrarily changing. This is why the \"change RF\" command is NCLI only, and not in the GUI.
\n
\nRE Foundation RF2<\/b>
\nThis is setting up the \"cluster level\" RF, but regardless of foundation, if you have a cluster that is RF2, you can go to RF3 with NCLI, yes.
\n
\nRE Enable\/Disable ECX<\/b>
\nSure, you can change that all you want. Just note that encoded data will stay encoded until the data is overwritten.
\n
\nThis is slightly different behavior than enable\/disable compression, which does actively compression\/decompress data when the setting is changed.","className":"post__content__best_answer"}">
查看原始
\nYes, ECX and block awareness do not mix. There is a long technical explanation of why, but the short of it is that the majority of customers who would use ECX wouldn't have enough physical blocks to actually enforce block awareness on ECX data (due to the different way that ECX stores blocks on disk), so we have delayed working on making the two work together as of now.
\n
\nRE Physical disk LED \/ finding a disk<\/b>
\nThe disk ID is really an \"internal\" construct, do not pay much attention to it.
\n
\nIf the LED on a disk was not working, or perhaps a HDD was 100% \"dead\" and the disk was just 100% offline, you would just simply look for the node that it is attached to (which is visibile in the Prism hardware display diagram) and go to that physical node and remove it.
\n
\nAlternatively, You could flash the LED on that node as well, which would help, OR perhaps flash all of the LED's of the disks around the dead disk, so that the dead disk stands out as \"not flashing\"
\n
\nIf there was any doubt, you would compare the serial number from the Disk in Prism to the physical one printed on the drive to double check.
\n
\nThis is the general approach for almost all storage systems.
\n
\nRE Removing a node<\/b>
\nYou do not need to svMotion anything at all. The CVM's will move the data off that node.
\n
\nEven if you did \"svMotion\" all of those VM's, you'd still have data on that CVM before it is removed from the cluster, as it is a part of the clusters overall capacity, so the svMotion literally doesn't do anything but waste time.
\n
\nJust regular vMotion the VM's to another node first, then remove the node using Prism and wait for the task to complete.
\n
\nRE RF3 to RF2 change<\/b>
\nAre you talking at the cluster level? or the container level?
\n
\nCluster level can not be changed back. I *think* the container level can be changed back, but I've never tried it. Absolute worst case, just provision another container at RF2 and storage vMotion the data.
\n
\nThat said, this question is one of those that you should really think through before arbitrarily changing. This is why the \"change RF\" command is NCLI only, and not in the GUI.
\n
\nRE Foundation RF2<\/b>
\nThis is setting up the \"cluster level\" RF, but regardless of foundation, if you have a cluster that is RF2, you can go to RF3 with NCLI, yes.
\n
\nRE Enable\/Disable ECX<\/b>
\nSure, you can change that all you want. Just note that encoded data will stay encoded until the data is overwritten.
\n
\nThis is slightly different behavior than enable\/disable compression, which does actively compression\/decompress data when the setting is changed.","className":"post__content__best_answer"}">
