Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
There was an update of VMware up to 6.5 version on the host side, after that was made a decision to format datastores file system from VMFS5 to VMFS6.
After one of datastores was formatted, it was decided to test datastore with VMFS5 and datastore with VMFS6 inside, during that process high latency was mentioned on datastore with VMFS6.
Feature difference between VMFS5 and VMFS6 was analyzed and compared.
It was found that in VMFS6 was added space automatically reclamation feature. It needed to manually reclaim space in VMFS5.
During the storage vMotion, every one block is migrated, this block will be reclaimed immediately by sending VMFS6 unmap command with multiple huge IOs to write zero to the storage.
These huge IO (16MB) will get higher latency than small normal R/W IO, therefore this will affect the other business performance by increasing latency.
Space automatically reclamation feature in VMFS6.
Disable space automatically reclamation feature of VMFS6 in VMware's vSphere and manually reclaim the space during peak-off hours.
To perform this operation check the attachment to this KB.
To find peak-off hours performance logs can be analyzed.
It should pay more attention to release notes/new features before perform any upgrade.