TrueCrypt support?

[campr]

First, thanks for the excellent tool.

I've tried to run JkDefrag on a mounted TrueCrypt volume, but it seems to ignore the drive argument in this case. Are TrueCrypt drives not supported (yet)?

Cheers,
Tom

[jeroen]

See the JkDefrag.log file for more information. Does TrueCrypt support defragmentation by the standard Windows defragger? Then JkDefrag will be able to defragment/optimize it, otherwise not.

[Ratte]

Code:

20:18:17 Commandline argument '-a' accepted, optimizemode = 3
20:18:17 Commandline argument '-f' accepted, freespace = 0.0%
20:18:17 Commandline argument '-d' accepted, debug = 6
20:18:17 JkDefrag v3.25
20:18:17 Date: 2007/09/17
20:18:17 NtfsDisableLastAccessUpdate is active, ignoring LastAccessTime for SpaceHogs.
20:18:17 Starting JkDefrag for 'j:\'
20:18:17 Cannot find volume name for mountpoint 'j:': [87] Falscher Parameter.

[Tron04]

I can defrag Truecrypt volumes without any problem with JKDefrag 3.25.
Cannot replay the problem, which was mentioned here...

[jeroen]

Code:

20:18:17 Cannot find volume name for mountpoint 'j:': [87] Falscher Parameter.

This is a TrueCrypt drive? Then the message means that the TrueCrypt drive is not registered in Windows as a disk, it does not have a volume name. JkDefrag uses that to access the disk, even when it is not mounted.

[Ratte]

This is a TrueCrypt drive?

Yes. Drive is a encrypted partition (\Device\Harddisk1\Partition1) and is specified as \Device\TrueCryptVolumeJ.

jkdefrag -a3 -f0 -d6 \Device\TrueCryptVolumeJ

Code:

07:26:25 Commandline argument '-a' accepted, optimizemode = 3
07:26:25 Commandline argument '-f' accepted, freespace = 0.0%
07:26:25 Commandline argument '-d' accepted, debug = 6
07:26:25 JkDefrag v3.25
07:26:25 Date: 2007/09/18
07:26:25 NtfsDisableLastAccessUpdate is active, ignoring LastAccessTime for SpaceHogs.
07:26:25 Starting JkDefrag for '\Device\TrueCryptVolumeJ'
07:26:25 Opening volume '\\?\Volume{67d7e852-d2a8-11da-9849-806d6172696f}' at mountpoint 'E:'
07:26:25 Phase 1: Analyze
07:26:25 Analyzing: \Device\TrueCryptVolumeJ\*
07:26:25 Zone[1] = 0
07:26:25 Zone[2] = 0
07:26:25 Zone[3] = 0
07:26:25 Phase 2: Fixup
07:26:25 Finished.
07:26:25 - Total disk space: 0 bytes (0.00 gigabytes), 1964489 clusters
07:26:25 - Bytes per cluster: 0 bytes
07:26:25 - Number of files: 0
07:26:25 - Number of directories: 0
07:26:25 - Total size of analyzed items: 0 bytes, 0 clusters
07:26:25 - Number of fragmented items: 0
07:26:25 - Total size of fragmented items: 0 bytes, 0 clusters
07:26:25 - Free disk space: 0 bytes, 337701 clusters, 17.19% of disk
07:26:25 - Number of gaps: 2994
07:26:25 - Number of small gaps: 1804, 60.25% of all gaps
07:26:25 - Size of small gaps: 0 bytes, 8024 clusters, 2.38% of free disk space
07:26:25 - Number of big gaps: 1190 (39.75% of all gaps)
07:26:25 - Size of big gaps: 0 bytes, 329677 clusters, 97.62% of free disk space
07:26:25 - Average gap size: 112.79 clusters
07:26:25 - Biggest gap: 0 bytes, 21468 clusters, 6.36% of free disk space

Hmm why "07:26:25 Opening volume '\\?\Volume{67d7e852-d2a8-11da-9849-806d6172696f}' at mountpoint 'E:'"? That is the wrong drive assembly! The disk map actually corresponds to the drive assembly E: but everything remains grey.

Result of the call of mountvol:

Code:

Mögliche Werte für "Datenträgername" und aktuelle Bereitstellungspunkte sind:

    \\?\Volume{0e2f5131-c4c9-11d9-a8da-806d6172696f}\
        *** Keine Bereitstellungspunkte ***

    \\?\Volume{0e2f5130-c4c9-11d9-a8da-806d6172696f}\
        *** Keine Bereitstellungspunkte ***

    \\?\Volume{67d7e850-d2a8-11da-9849-806d6172696f}\
        C:\

    \\?\Volume{67d7e851-d2a8-11da-9849-806d6172696f}\
        D:\

    \\?\Volume{67d7e852-d2a8-11da-9849-806d6172696f}\
        E:\

    \\?\Volume{fcad96f0-c4cb-11d9-a8dc-a4e803811fad}\
        F:\

    \\?\Volume{35c4c1b0-5ea6-11dc-8f51-000c6ecbbe05}\
        *** Keine Bereitstellungspunkte ***

    \\?\Volume{2d98a354-0d3c-11db-be57-806d6172696f}\
        *** Keine Bereitstellungspunkte ***

    \\?\Volume{0cd0b0e0-15e7-11db-8e55-f8202f8074a9}\
        Z:\

    \\?\Volume{7edf3732-5e85-11d9-99b5-806d6172696f}\
        L:\

    \\?\Volume{7edf3730-5e85-11d9-99b5-806d6172696f}\
        A:\

    \\?\Volume{e1913ab0-1eb4-11dc-af3d-806d6172696f}\
        K:\

    \\?\Volume{e1913ab1-1eb4-11dc-af3d-806d6172696f}\
        M:\

Then the message means that the TrueCrypt drive is not registered in Windows as a disk, it does not have a volume name.

Wouldn't that exclude the use in the Explorer and other programs?

JkDefrag uses that to access the disk, even when it is not mounted.

Disk is mounted.

OS Win2kSP4

[jeroen]

Hmm why "07:26:25 Opening volume '\\?\Volume{67d7e852-d2a8-11da-9849-806d6172696f}' at mountpoint 'E:'"? That is the wrong drive assembly!

It sounds like the standard Windows calls for disks do not work properly for the TrueCrypt driver. I would say it's a problem in the TrueCrypt driver, but I don't know. I have put it on the list to look at it in future, maybe I can find a workaround. I'm not sure if I should, because if I find a workaround then it might open up problems for other virtual disks.

Disk is mounted.

No, I meant that JkDefrag accesses disks (any disk) via the volumename so it can also defrag disks when they are not mounted. That's why it translates driveletters into volumenames using the GetVolumeNameForVolumeMountPoint() Windows call.

[Tron04]

I did not test it with commandline switches.
Simply running "jkdefrag J:" (J: is the mounted truecrypt volume) worked...

[campr]

I have mounted a file as truecrypt volume. The mounted volume is available as drive E:. The windows defragmenter does not list drive E: and when I execute 'JkDefrag.exe e:', I'm getting following output in the JkDefrag.log:

Code:

12:18:35 JkDefrag v3.25
12:18:35 Date: 2007/09/18
12:18:35 NtfsDisableLastAccessUpdate is inactive, using LastAccessTime for SpaceHogs.
12:18:35 Starting JkDefrag for 'e:'
12:18:35 Cannot find volume name for mountpoint 'e:': [87] Falscher Parameter.

'mountvol' shows following output:

Code:

Mögliche Werte für "Datenträgername" und aktuelle Bereitstellungspunkte sind:

    \\?\Volume{c023a280-3477-11db-a2f9-806d6172696f}\
        C:\

    \\?\Volume{efea338a-3b46-11dc-af49-001560c8bebc}\
        *** Keine Bereitstellungspunkte ***

    \\?\Volume{efea338c-3b46-11dc-af49-001560c8bebc}\
        *** Keine Bereitstellungspunkte ***

    \\?\Volume{ad2bcd57-cfbf-11db-af46-806d6172696f}\
        *** Keine Bereitstellungspunkte ***

    \\?\Volume{ad2bcd59-cfbf-11db-af46-001560c8bebc}\
        D:\

    \\?\Volume{ad2bcd5a-cfbf-11db-af46-001560c8bebc}\
        F:\

    \\?\Volume{af1b3c6f-346e-11db-a25e-001560c8bebc}\
        Z:\

    \\?\Volume{af1b3c70-346e-11db-a25e-001560c8bebc}\
        Y:\

BTW, I'm working on a W2kSP4-system.

[jeroen]

I did not test it with commandline switches.
Simply running "jkdefrag J:" (J: is the mounted truecrypt volume) worked...

Which Windows version? Which TrueCrypt version? Perhaps you have a tip for the people who are having problems? How should they configure TrueCrypt?

[Tron04]

Which Windows version? Which TrueCrypt version? Perhaps you have a tip for the people who are having problems? How should they configure TrueCrypt?

I am running german Windows XP SP2 with all released Microsoft Patches installed. Truecrypt V4.3a.
I mounted the TrueCrypt-Container-File as a removable media and also as fixed media. In both cases I was able to run JKDefrag on it.

Maybe it is an issue that only appears on Win2K?

[Capsaicin]

TrueCrypt has a known limitation on Win2k with the way it mounts drives that prevents most defraggers from working. Sysinternal's contig works, though.

[Donn Edwards]

TrueCrypt has a known limitation on Win2k with the way it mounts drives that prevents most defraggers from working. Sysinternal's contig works, though.

It must be a Windows 2000 problem, because I have used JKD from version 3.8 onwards on my Truecrypt volumes on Windows XP Pro SP2

Since you're using contig, try this registry change to make it easier.