JKdefrag 3.34 hangs with high cpu on vista32

[jonno]

JKdefrag 3.34 hangs while processing my D: then the CPU shows 50%.  Only solution is to power down the laptop, you cannot kill jkdefrag.

I have attached the log from a -d 6 output.

[WHRoeder]

The last lines of your log said:

Code:

19:03:28 D:\VPC\Vista\Vista Hard Disk.vhd
Moving 1166258 clusters from 19979666 to 19985478, VCN=2252887.

That's a 4555 mb file.  I'll will take at least 18 minutes to defrag at 10mb/s.  With many fragments, much longer with a lot of cpu.
Until the file move completes, you can't kill jkdefrag.
Let it run.

[jonno]

Hmm, yes I was able to diagnose that far

I have left it for 48+ hrs - its also worth pointing out that there is actually no IO activity from JKdefrag at this point.  Its as if its stuck in a processing loop rather than actually doing any work?

I was going to debug it, but I thought it would be more use to post it here...

I have attached a couple of screenshots that hopefully highlight the issue in more detail.  I also have a process dump at this point if anyone wants it?  If i can find 10 minutes tommorow I might take a look.  I would upload it here, but its 6MB after compressing it and the forum wont let me upload anything that large.

It seems pretty repeatable for me at the minute, so if I can do anything else, just shout

[jeroen]

JKdefrag 3.34 hangs while processing my D: then the CPU shows 50%.  Only solution is to power down the laptop, you cannot kill jkdefrag.

JkDefrag does not move files by itself. It is based on the Microsoft defragmentation API, and basically all it does is send "move this file to that location" commands to the API. Your problem is not caused by a bug in JkDefrag, but by something inside Windows. Perhaps the file is used by another process. Usually a problem like this will solve itself, after a minute or so the API will continue. To avoid the problem altogether simply exclude the file with the JkDefrag "-e" option.

[RJARRRPCGP]

Don't do a hard shut down! Now don't cry to us if you have MFT errors. Sorry.

Cannot help you more, ATM.

[Tekzel]

Don't do a hard shut down! Now don't cry to us if you have MFT errors. Sorry.

Cannot help you more, ATM.

If only it were that easy, sometimes you just have no other option.  I have experienced the same issue (as I have posted in another thread) and let it run for 3 days before just powering it off.  I am pretty certain I know WHY mine is happening, but I feel pretty confident it shouldn't be doing it.  It has to do with a 24gb file on that volume, but no other defrag program has that much of a problem with it.  The last one I ran, Defraggler, defragged the volume in about 1 hour.

[WHRoeder]

run jkdefrag under ubcd4win.  That way nothing else is interfering

[Tekzel]

run jkdefrag under ubcd4win.  That way nothing else is interfering

No, really?  You are suggesting in this day and age that someone boot their machine from a CD just so they can defrag it?  Come on, join us in the 2000s, its generally a pretty decent computing environment here.

[jeroen]

Don't do a hard shut down!

It is safe to stop JkDefrag at any time. A soft reboot (select reboot from the Windows menu) is perfectly safe. A hard reboot (power off) is a bit dangerous, but safe if your disks are NTFS.

[ewieldra]

run jkdefrag under ubcd4win.  That way nothing else is interfering

Indeed run defragmentation from a Preinstalled enviroment ..

The best advise for solving this kind of problems

[RJARRRPCGP]

Don't do a hard shut down!

It is safe to stop JkDefrag at any time. A soft reboot (select reboot from the Windows menu) is perfectly safe. A hard reboot (power off) is a bit dangerous, but safe if your disks are NTFS.

I can't guarantee a file won't be corrupted. It's even possible that Chkdsk or NTFS deletes the file as "orphaned".

[jeroen]

I can't guarantee a file won't be corrupted. It's even possible that Chkdsk or NTFS deletes the file as "orphaned".

Perhaps you are talking about some other defragmenter, or about some software you have build yourself. As the author of JkDefrag I am perfectly confident in claiming that (while using JkDefrag on NTFS) files can never get lost, corrupted, or orphaned. JkDefrag is based on the Microsoft defragmentation API, and this API has a very good track record and has proven to be extremely solid. NTFS is much better than FAT and has very good protections against losing files because of power-loss and other system crashes.