Re: [HTCondor-users] Using ram-dive on Windows OS

[John M Knoeller <johnkn@xxxxxxxxxxx>]

If that ramdrive does not show up as a value, it will not currently work with HTCondor because the STARTD will abort when it gets and error when trying to get the volume name of the ramdrive.  

 

I havenât had time to check through all of the code, but it looks to me like we can get away with treating failure to get the volume name as not an error. If we ignored that error the rest of the code would probably work, so Iâm making a special build for you to try that does that.

 

you can get the build from ftp://ftp.cs.wisc.edu/condor/temporary/winvolname

 

This was based on the 8.6.4 release, versioned as an 8.6.5 pre-release.

 

This build will still print an error when it fails to get the volume name, but will then treat the drive letter as the volume name an keep going.

If this solves your problem. I see about getting the change into the next 8.6 release.

 

-tj

 

 

From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Werner KoppelstÃtter
Sent: Thursday, June 22, 2017 7:41 AM
To: htcondor-users@xxxxxxxxxxx
Subject: [HTCondor-users] Using ram-dive on Windows OS

 

Hi,

 

I tried to use virtual-ram-drive for Windows-execute-machine.

I set the config-entry (EXECUTE = X:\Execute) in the config to the ram-drive.

 

When I try to set the job-execution-folder to the ram-drive (EXECUTE = X:\Execute), the Startd doesn't start.

The entries in the StartLog:

06/22/17 14:07:08 sysapi_partition_id: GetVolumeNameForVolumeMountPoint error: 4390
06/22/17 14:07:08 ERROR "Failed to get partition id for SLOT1_EXECUTE=X:\Execute" at line 81 in file C:\condor\execute\dir_14532\sources\src\condor_startd.V6\slot_builder.cpp

 

I test is on a Windows 7 with HTCondor 8.6.3.

For the ram-drive I used ImDisk Toolkit which is based on ImDisk Virtual Disk Driver for Windows Version 2.0.9.

 

The ram-drive works fine for all other programms I have tested.

 

I think the problem is how condor access the drive. I found the following compatibility description for the ImDisk:

ImDisk Virtual Disk Driver is designed to be a small, simple and yet powerful virtual disk driver. It runs on very old versions of Windows NT as well as modern Windows versions. However, because of this compatibility design and because it emulates disk volumes rather than complete disks, it is not always compatible with all applications and drivers. For instance, you cannot manage things like mount points, drive letters and similar for ImDisk drives using mountvol command line tool or in Disk Management in Windows. As another example, you cannot create or access shadow copies on ImDisk drives. So, applications that use similar Windows features as Disk Management dialog to enumerate disks and disk volumes to find disk properties like sector sizes and similar, might possibly not work as expected with ImDisk drives.

 

Do anyone have a hint to use the ram-drive with HTCondor?

 

Thanks in advance for hints

Werner KoppelstÃtter