Why does ONTAP require OS type information in an igroup when Windows and Linux hosts are connected?

Why does ONTAP require OS type information in an igroup when Windows and Linux hosts are connected?

• A. To determine which network protocol to use for access.
• B. To align client file system blocks with the LUN blocks correctly.
• C. To enforce per-OS user ACLs.
• D. To set replication policies per OS.

Answer: (B)

The need for OS type information in an igroup is about aligning the host’s file-system blocks with the LUN’s physical blocks. Windows and Linux manage and address blocks differently, so ONTAP uses the OS type to map the host’s I/O to the correct block boundaries on the LUN. When the alignment is correct, reads and writes stay within the intended blocks, improving performance and reducing cross-boundary I/O. This is not about choosing a network protocol, enforcing per-OS ACLs, or setting replication policies per OS.

The need for OS type information in an igroup is about aligning the host’s file-system blocks with the LUN’s physical blocks. Windows and Linux manage and address blocks differently, so ONTAP uses the OS type to map the host’s I/O to the correct block boundaries on the LUN. When the alignment is correct, reads and writes stay within the intended blocks, improving performance and reducing cross-boundary I/O. This is not about choosing a network protocol, enforcing per-OS ACLs, or setting replication policies per OS.