tag:blogger.com,1999:blog-2250573236194682558.post2351465516961589103..comments2023-07-04T15:40:52.637+01:00Comments on Austin's blog: VMware and ESXi with 4k DisksAustin Toveyhttp://www.blogger.com/profile/01120969262369106035noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-2250573236194682558.post-70798047736966335652016-03-10T20:14:56.796+00:002016-03-10T20:14:56.796+00:00Not to be a stickler but actually the 512e block s...Not to be a stickler but actually the 512e block size was only introduced after the 4K was introduced due to the legacy(which are not really legacy) applications and operating systems which do not yet have drivers to support the 4k block size. So 512e was introduced to emulate the 512 sectors to the logical while the physical remains 4k. Problem with this configuration is that the emulation causes a lot of overhead as it's writing chunks of 512 to DRAM and then moves it to disk as a 4K chunk. This causes a lot of performance issues in VMware storage I/O latency and VMFS partitioning. I just encountered an issue with a new R730xd server that was shipped with 4Kn drives and learned the hard way how ESXi and vCenter dont play nice with 4k block/sector sizes. Anonymoushttps://www.blogger.com/profile/02038436803497941693noreply@blogger.com