IO issues on Windows Server 2012

[Richard_S_6]

We recently added a Dell Poweredge R420 to our compute server mix. Because of the newer hardware we had to install Windows Server 2012 STD. To which we added the HPC addon to make it similar to our other compute servers running Windows 2003 Compute Cluster Edition.

Our existing software built with Intel Visual Compiler XE 13.1.2.190 runs without problems on the older setup. But on the new configuration we get an IO error at what seem to be random (maybe load dependent). If the application writes a very large file followed by a close then open it again we get an IOSTAT=30. The writes are to a local raid 1 disk with a controller with 1GB cache. Which is similar to our older compute servers.

Is there a compatibility issue between Visual Fortran and Windows Server 2012.

[Bernard]

>>>handle.exe and the Resource Monitor in Server 2012 work fine and show that the low level code used by Fortran has not kept up with OS changes and is not always deleting handles as it should on close.  We have other programs written in C# including one that runs as a service for days and do very similar things and they always have only a minimum number of handles.>>>

I agree with you,but handle.exe does not have such low level capabilities as windbg has.Handles are created and managged by kernel mode codeWindbg has excellent logic and heuristic which can help you to track per  handle leaking with the thread and function granularity.

[Richard_S_6]

Still working on example. The first simple one I put together with the same write subroutines as the main application and some do loops did not show a problem. Updating sample to be a full windows application using windows message pump like the main application. Suspect that the problem may relate to running inside a windows message pump.

[Richard_S_6]

I did not give up, all my examples even the full windows app failed to show the handle issue. So after a lot of trial and error I stripped the real application down to the essentials and it still shows the handle issue. To summarize the application creates a huge number of orphan handles when run on Windows Server 2008R2 HPC and Windows Server 2012 STD with or without HPC, also on Windows 8.1.  But does not on Windows Server 2003 Compute Cluster Edition, Windows XP and Windows 7. All versions of the application have same problem 32bit/x64 and Debug/Release.

Attach is Lynx_new - stripped.zip 2010 Visual Studio solution with everything needed to build each version, x64 debug is already built. Test.zip is test files. Instructions.docx is some simple instructions for running. Key routine is DeckModProcessor.f90 which opens a template file then creates a new file in a working directory copies the template with changes to that file and closes it.

Give it a try on one of your test server's. All my tests were on Dell Servers varying from old PowerEdge 1950's to new PowerEdge R420's. It looks like its not directly related to hardware but operating systems from Server 2008R2 (windows 8) on.

[Steven_L_Intel1]

I don't see the attachment.

[Richard_S_6]

They show up under my files tab, so I selected them and did another submit.

[Steven_L_Intel1]

Ok, thanks. We'll see what we can find.