topic Re: Can't see new files in Windows Server 2012 in ONTAP Discussions

Can't see new files in Windows Server 2012

nguyensonbach2410 — Tue, 24 Oct 2017 04:39:17 GMT

I have LUN with LUN type is Windows 2003 MBR.
I use for 2 Windows Server 2012, they can see LUN but when i create new files ( text,mp3... ) in server A, server B can't see this file.

I try to create new LUN with LUN type is Windows 2008 but i have same issue.
So, what can i do ?
Thanks for supporting me.
Bach

Model: FAS2240-2
Version:NetApp Release 8.1RC3 7-Mode

Re: Can't see new files in Windows Server 2012

sgrant — Wed, 25 Oct 2017 08:30:59 GMT

Hi Bach,

To confirm the reason for the LUN OS type is purely about the offset. The offset ensures that the LUN and OS are matched regarding where blocks are written. If they do not align then we have misalignment which causes performance degregation, please see: What is an unaligned I/O?

For your WIndows 2012 servers you must use LUN OS type windows_2008.

Also, you are using an Release Candidate (RC) release of an old ONTAP version that went out of Engineering Support on 30-Aug-15. If possible you should be looking to upgrade to the Supported Data ONTAP 8.2.5.

However, your issue is that the second server cannot see changes to the LUN. I am assuming this is not a Windows Cluster enviornment. In which case only one server can connect to the LUN at a time otherwise you risk data corruption. If you are only connecting to the LUN via Server A, then this is not a problem and rather is your issue that at a file system level Server B cannot see the changes?

Can you clarify how Server B is attempting to view the files; is it via connecting to the LUN on the storage an mounting it as a drive in disk manager, or connecting to a share hosting on Server A?

Thanks,

Grant.

Re: Can't see new files in Windows Server 2012

wareer — Thu, 06 Feb 2025 01:33:18 GMT

Guidelines for mapping LUNs to igroups

You can map a LUN only once to an igroup.
As a best practice, you should map a LUN to only one specific initiator through the igroup.
You can add a single initiator to multiple igroups, but the initiator can be mapped to only one LUN.
You cannot use the same LUN ID for two LUNs mapped to the same igroup.
You should use the same protocol type for igroups and port sets.