默认情况下，所有Nutanix容器都是精简的配置;这是NDFS的一个特征。精简配置是一项广泛接受的技术，通过多个存储供应商随着时间的推移被证明，包括VMware。由于默认情况下作为NFS数据存储到VMware vSphere主机，因此默认情况下，所有VM也将默认配置。如果没有传统的性能影响，这导致大大提高了存储能力利用率。如果有限用例（例如容错（FT）或高苛刻的数据库和I / O工作负载等有限用例，则可以在VMDK级别上提供厚的供应。可以通过创建急切零厚的VMDK来完成厚的配置。急切零厚VMDK将自动保证NDFS内的空间预留。
这就是脱节的地方。当我提供一个延迟置零或即时置零的1TB VM时，这两者都会导致容器存储利用率上升2TB(使用的复制因子为2)。我希望只看到主动置零的VM引起跳转，因为lazy应该被精简配置。此外，当我创建一个延迟置零的虚拟机，在虚拟机创建完成后，磁盘被列为主动置零?
最佳答案j
\n\nThick ANY causes NOS to reserve the space on the backend. The only difference is whether it zeros it out up front or not, as you know lazy vs eagar.
\n
\nThis is because if you are telling Nutanix you want thick, we dont want to accidently have the system run out of space, like some other storage systems do, so we'll respect that lazy reservation for you automagically.
\n
\nSummary - the jump you are seeing is because we automatically reserve the space. This doesnt mean we zero it out for you, just make a reservation.
\n
\n
\nAnyhow, fun fact, win NOS 4.6, we added Zero avoidance to the write cache layer (aka oplog), so zero operations should be much faster now, because we just see the zero and update metadata, instead of writing the zero to cache. very slick and cool stuff.","className":"post__content__best_answer"}">
