GetVolumePathName() not working?
Status: Inactive
Brought to you by:
w77
Menu
▾
▴
#5 GetVolumePathName() not working?
Hi,
It seems, the function GetVolumePathName() is not working on the RAM-Disk. Maybe you can take a look at it?
To give you a bit more background, this is my actual problem: I am a java-developer, and wanted to run the current wildfly10 on my ram-disk. But I get exceptions during the start (can be ignored, but still annoying). However when using my SSD (C:) no errors happen. This is the java exception:
java.nio.file.FileSystemException: Z:\appserver\wildfly-10.1.0.Final\standalone\configuration\standalone.xml: Unzulässige Funktion.
[...]
at java.nio.file.Files.getFileStore(Files.java:1461)
[...]
Unzulässige Funktion - > german translation of 'Incorrect Function'
I wrote a small java-program to test this Files.getFileStore() Method, and debugged the java8 api. It is returning that exception, when calling the win32-function GetVolumePathName().
The actual FileStore is available in java; I dumped all available FileStores, and the RamDisk was there. In the case above, GetVolumePathName() should have returned "Z:\"
It would be great, if you can fix that bug.
I just tested GetVolumePathName on an imdisk volume, and I too get weird results. Not the error you mention, but I assume that it depends on the OS version. We also can see here and there other people having issues with that.
It is likely one of these functions that use at some point the Volume Mount Manager, which is not handled by the imdisk driver. For instance, there are other reports with GetFinalPathNameByHandle that does not work properly with the imdisk volumes.
Therefore, I am afraid that this issue will never be fixed.
Using an ImDisk volume is incompatible with Visual Studio 2017 unfortunately, I had to stop using ImDisk with it. At the start of a debugging session it display an error message "Invalid function", I don't know how I can get more information on the exact IO operation that visual studio tries to do, but it may be the one that is reported in this bug?
It worked great with visual studio 2015.
Why do you say this will never be fixed?
Cheers.
This also related to other ramdisk software.
Putting the source tree on ramdisk
Cannot debug program when compiled to RAM drive