Defraggler 1.05 apparently looping round huge list of files

[John Gray]

Little of what I did may be relevant, but this is the sequence.

 

I've used Defraggle 1.04 build 098 (GUI version) on two computers, on four drives, over the last couple of weeks. Very pleasing.

 

I then installed 1.05 build 111 on both PCs today, and have defragged one drive on each PC successfully.

 

On my external drive I then tried the command-line version of 1.05 (DF E:), and it gave all the expected messages up to the "Defragging 90% complete", and just stuck there. CPU usage was nearly 50% (i.e. 100% of one core), and the I/O Read and Write bytes were static. There was a continuous chuff-chuff-chuff noise from the hard disk (head movement) about twice a second, but nothing else happened for well over an hour, at which point I cancelled the Command Prompt window.

 

I then ran the GUI version of 1.05 with /debug, and this again stopped at 90%, with an enormous list of files being displayed one at a time below the "Current State; total fragments 0" line. The debug log is over 2 MB so far after an hour, and there is a set of lines for each file culminating in the final part of the message line "The destination block is not free" (new file name, next block number in sequence from the previous).

 

After another hour or so I will probably get bored and cancel the execution of Defraggler, and then run a CHKDSK on the drive. There doesn't seem much point posting 2MB of mostly repetitive log, but if a Mod would send me a PM I could attach it to a reply (I hope!).

 

Any ideas what else I should do?

 

Thanks!

[hazelnut]

I'm sure MrRon, one of the bug fixers, will spot this post so hang on.

[John Gray]

I'm sure MrRon, one of the bug fixers, will spot this post so hang on.

 

Thank you! I can report that after 1? hours the screen suddenly started 'doing something', and after 2? hours (and 3,713 KB of log file) the defragment actually finished.

 

At present I am doing an equivalently agonisingly lengthy CHKDSK, and it looks as thought it will need to continue to run overnight.

 

I would however, be interested to know if what I experienced was SUPPOSED to happen that way - the proffered log file is still available (fortunately it ZIPs down to 363 KB)!

 

Thanks

 

PS I am right in thinking that MrRon is one of the Mysterons?!

[crazedfred]

Almost exact same problem here - defrag works fine for awhile, then goes to 50% CPU (100% on one core), and defragging slows to a crawl. I have 250 GB of stuff on a 500 GB drive, and it's taken 3 hours of chugging so far. It looks like if you abort the defrag halfway through, and start over (CLOSING AN RE-OPENING DEFRAGGLER), defraggler works well again until it gets to about 50%, then slows to a crawl with huge CPU usage again. Specifically, it will take forever to do tiny files. A 20 MB .mp3 file will take 30 seconds to relocate, even though nothing is using it. This is a brand new Vista 64-bit install so things are fragmented, but not THAT bad!

 

If somebody wants a debug file or anything, let me know. Only changes from default are relocate files > 2GB to end of disc.

 

Very frustrating bug, best of luck squashing it!

 

 

 

EDIT: this is a laptop, and I am de-fragging the hard drive. Sorry that wasn't clear.

[davey]

If somebody wants a debug file or anything, let me know. Only changes from default are relocate files > 2GB to end of disc.

Very frustrating bug, best of luck squashing it!

I would think MrRon could use your help as regards the "debug report".

Especially due to your set up.

PM me for an email address to send it to, or you can post it directly in the forum (if it's not too big).

 

MrRon

Thanks for your Post and report. davey

[TurtleWax]

The noise on your external hard drive may be indication of a BAD sector on the hard drive. Try running a full checkdisk/scandisk on it including testing unused space to mark the bad sector.

 

Note to others: If it is not a external Hard drive, it is not recommended to defrag. USB thumb drives usually use a method to reduce the number of times each memory location is written to increase the life of the thumb drive due to limited number of writes before the drive fails. Defragging a usb key should be done sparingly at most.

 

Sincerely,

TurtleWax

 

Little of what I did may be relevant, but this is the sequence.

 

I've used Defraggle 1.04 build 098 (GUI version) on two computers, on four drives, over the last couple of weeks. Very pleasing.

 

I then installed 1.05 build 111 on both PCs today, and have defragged one drive on each PC successfully.

 

On my external drive I then tried the command-line version of 1.05 (DF E:), and it gave all the expected messages up to the "Defragging 90% complete", and just stuck there. CPU usage was nearly 50% (i.e. 100% of one core), and the I/O Read and Write bytes were static. There was a continuous chuff-chuff-chuff noise from the hard disk (head movement) about twice a second, but nothing else happened for well over an hour, at which point I cancelled the Command Prompt window.

 

I then ran the GUI version of 1.05 with /debug, and this again stopped at 90%, with an enormous list of files being displayed one at a time below the "Current State; total fragments 0" line. The debug log is over 2 MB so far after an hour, and there is a set of lines for each file culminating in the final part of the message line "The destination block is not free" (new file name, next block number in sequence from the previous).

 

After another hour or so I will probably get bored and cancel the execution of Defraggler, and then run a CHKDSK on the drive. There doesn't seem much point posting 2MB of mostly repetitive log, but if a Mod would send me a PM I could attach it to a reply (I hope!).

 

Any ideas what else I should do?

 

Thanks!

[crazedfred]

Turtle: I am talking about de-fragmenting my laptop's hard drive. Sorry I wasn't clear.

I will start a new defraggler session with debug & post results later.

 

 

EDIT: as soon as defraggler stops rocking & starts sucking, it generates the following:

(note, I have censored the file paths and the computer name)

[2008-12-08] [00:43:14.856] 00c98 1 DefragVolumeSinglePassHelper::LayFileAt#650 MoveFileRegionWithMarking for file "CENSORED" to 11224134, 0, 9466 finished (hr=0x00000000). Destination block is not free.

[2008-12-08] [00:43:15.040] 00140 1 CVolume::UpdateDriveMap#317 Map generated in 0.12596 seconds.

[2008-12-08] [00:43:21.070] 00c98 1 DefragVolumeSinglePassHelper::LayFileAt#650 MoveFileRegionWithMarking for file "CENSORED" to 11233588, 0, 9466 finished (hr=0x00000000). Destination block is not free.

[2008-12-08] [00:43:21.627] 00140 1 CVolume::UpdateDriveMap#317 Map generated in 0.06931 seconds.

[2008-12-08] [00:43:27.599] 00c98 1 DefragVolumeSinglePassHelper::LayFileAt#650 MoveFileRegionWithMarking for file "CENSORED" to 11243030, 0, 9466 finished (hr=0x00000000). Destination block is not free.

[2008-12-08] [00:43:27.781] 00140 1 CVolume::UpdateDriveMap#317 Map generated in 0.13741 seconds.

[2008-12-08] [00:43:36.700] 00c98 1 DefragVolumeSinglePassHelper::LayFileAt#650 MoveFileRegionWithMarking for file "CENSORED" to 11252356, 0, 9466 finished (hr=0x00000000). Destination block is not free.

[2008-12-08] [00:43:37.210] 00140 1 CVolume::UpdateDriveMap#317 Map generated in 0.06476 seconds.

[2008-12-08] [00:43:37.588] 00c98 1 DefragVolumeSinglePassHelper::LayFileAt#650 MoveFileRegionWithMarking for file "CENSORED" to 11261603, 0, 219 finished (hr=0x00000000). Destination block is not free.

[2008-12-08] [00:43:37.787] 00140 1 CVolume::UpdateDriveMap#317 Map generated in 0.07450 seconds.

 

Here is the header of the debug log:

[2008-12-08] [00:38:12.115] 00920 0 Logger::HostLogger::LogApplicationInfo#617 C:\Program Files (x86)\Defraggler\Defraggler.exe

[2008-12-08] [00:38:12.115] 00920 0 Logger::HostLogger::LogApplicationInfo#619 CmdLine: "C:\Program Files (x86)\Defraggler\Defraggler.exe" /debug

[2008-12-08] [00:38:12.115] 00920 0 Logger::HostLogger::LogApplicationInfo#623 Version: 1_5_111

[2008-12-08] [00:38:12.115] 00920 0 Logger::HostLogger::LogApplicationInfo#649 FileVersion: 1.5.0.111

[2008-12-08] [00:38:12.115] 00920 0 Logger::HostLogger::LogApplicationInfo#650 ProductVersion: 1.5.0.111

[2008-12-08] [00:38:12.115] 00920 0 Logger::HostLogger::LogApplicationInfo#651 Flags: 0x00000000, OS: 0x00000004, Type: 0x00000002, Subtype: 0x00000000

[2008-12-08] [00:38:12.115] 00920 0 Logger::HostLogger::LogApplicationInfo#652 Flags description: Release

[2008-12-08] [00:38:12.115] 00920 0 Logger::HostLogger::LogSystemInfo#670 Computer name: CENSORED

[2008-12-08] [00:38:12.115] 00920 0 Logger::HostLogger::LogSystemInfo#677 User name: CENSORED

[2008-12-08] [00:38:12.115] 00920 0 Logger::HostLogger::LogSystemInfo#685 OEM ID: 0

[2008-12-08] [00:38:12.115] 00920 0 Logger::HostLogger::LogSystemInfo#686 Number of processors: 2

[2008-12-08] [00:38:12.115] 00920 0 Logger::HostLogger::LogSystemInfo#687 Page size: 4096

[2008-12-08] [00:38:12.115] 00920 0 Logger::HostLogger::LogSystemInfo#688 Processor type: 586

[2008-12-08] [00:38:12.115] 00920 0 Logger::HostLogger::LogSystemInfo#689 Minimum application address: 10000

[2008-12-08] [00:38:12.115] 00920 0 Logger::HostLogger::LogSystemInfo#690 Maximum application address: 7ffeffff

[2008-12-08] [00:38:12.115] 00920 0 Logger::HostLogger::LogSystemInfo#691 Active processor mask: 3

[2008-12-08] [00:38:12.120] 00920 0 Logger::HostLogger::LogSystemInfo#694 Clean boot: 0

[2008-12-08] [00:38:12.120] 00920 0 Logger::HostLogger::LogSystemInfo#695 Monitors: 1, Display: 1680x1050, Virtual: 0x0 1680x1050

[2008-12-08] [00:38:12.120] 00920 0 Logger::HostLogger::LogSystemInfo#705 Major: 0x00000006, Minor: 0x00000000, Build: 6001, PlatformId: 0x00000002

[2008-12-08] [00:38:12.120] 00920 0 Logger::HostLogger::LogSystemInfo#706 SPMajor: 0x0001, SPMinor: 0x0000, CSDVersion: "Service Pack 1"

[2008-12-08] [00:38:12.120] 00920 0 Logger::HostLogger::LogSystemInfo#707 SuiteMask: 0x00000100, ProductType: 0x00000001

[2008-12-08] [00:38:12.120] 00920 0 Logger::HostLogger::LogSystemInfo#719 Memory: Load: 44, Physical: 2362957824/4292354048, PageFile: 6874701824/8768520192, Virtual: 2077175808/2147352576, Extended 0

[2008-12-08] [00:38:12.120] 00920 1 wWinMain#135 /debug

[2008-12-08] [00:38:12.120] 00920 1 CDriveListForm::CDriveListForm#37 GetSystemWindowsDirectory returned "C:\Windows" (system volume is C:).

[2008-12-08] [00:38:12.120] 00920 1 CMainFrame::CMainFrame#174 Entering CMainFrame::CMainFrame

[2008-12-08] [00:38:12.120] 00920 1 CMainFrame::CMainFrame#174 Leaving CMainFrame::CMainFrame

[2008-12-08] [00:38:12.125] 00920 1 CMainFrame::OnCreate#438 Entering CMainFrame::OnCreate

[2008-12-08] [00:38:12.130] 00920 1 CMainFrame::CreateChildWindows#308 Creating driveListForm_.

[2008-12-08] [00:38:12.135] 00920 1 CMainFrame::CreateChildWindows#310 Creating driveMapForm_.

[2008-12-08] [00:38:12.135] 00920 1 CMainFrame::CreateChildWindows#312 Creating fileListForm_.

[2008-12-08] [00:38:12.145] 00920 1 CMainFrame::PrepareLayout#339 Updating layout.

[2008-12-08] [00:38:12.155] 00920 1 CCheckForUpdates::CheckForUpdates#36 Checking for updates

[2008-12-08] [00:38:12.155] 00920 1 CCheckForUpdates::CheckForUpdates#52 Update check is not needed

[2008-12-08] [00:38:12.155] 00920 1 CCheckForUpdates::CheckForUpdates#57 Forcing update check

[2008-12-08] [00:38:12.155] 00920 1 CMainFrame::OnCreate#472 Registering object for message filtering.

[2008-12-08] [00:38:12.155] 00920 1 CMainFrame::Initialize#362 Initializing VolumeManager.

[2008-12-08] [00:38:12.155] 00920 1 CVolumeManagerBase::CVolumeManagerBase#10 Entering CVolumeManagerBase::CVolumeManagerBase

[2008-12-08] [00:38:12.155] 00920 1 CVolumeManagerBase::CVolumeManagerBase#10 Leaving CVolumeManagerBase::CVolumeManagerBase

[2008-12-08] [00:38:12.155] 0060c 1 CCheckForUpdates::CheckThread#68 Update check thread started

[2008-12-08] [00:38:12.155] 00920 1 CVolumeManager::CVolumeManager#10 Entering CVolumeManager::CVolumeManager

[2008-12-08] [00:38:12.155] 00920 1 CVolumeManager::CVolumeManager#10 Leaving CVolumeManager::CVolumeManager

[2008-12-08] [00:38:12.155] 00920 1 CVolumeManager::Initialize#19 Entering CVolumeManager::Initialize

[2008-12-08] [00:38:12.155] 00920 1 CVolumeManagerBase::Initialize#18 Entering CVolumeManagerBase::Initialize

[2008-12-08] [00:38:12.155] 00920 1 CVolumeManagerBase::Initialize#28 Enabling SE_BACKUP_NAME privilege succeeded.

[2008-12-08] [00:38:12.155] 00920 1 CVolumeManagerBase::Initialize#34 Enabling SE_RESTORE_NAME privilege succeeded.

[2008-12-08] [00:38:12.155] 00920 1 CVolumeManagerBase::Initialize#18 Leaving CVolumeManagerBase::Initialize

[2008-12-08] [00:38:12.155] 00920 1 CVolumeManager::Initialize#19 Leaving CVolumeManager::Initialize

[2008-12-08] [00:38:12.155] 00920 1 CMainFrame::Initialize#367 Initializing VolumeNavigator.

[2008-12-08] [00:38:12.155] 00884 1 CVolumeManagerBase::RebuildVolumesMap#103 Logical drives mask: 0x0000003c, arrival mask: 0xffffffff, removal mask: 0x00000000.

[2008-12-08] [00:38:12.155] 00920 1 CDriveMap::CDriveMap#14 Entering CDriveMap::CDriveMap

[2008-12-08] [00:38:12.155] 00920 1 CDriveMap::CDriveMap#14 Leaving CDriveMap::CDriveMap

[2008-12-08] [00:38:12.155] 00884 1 CVolumeManagerBase::UpdateVolume#262 Start update for volume C:.

[2008-12-08] [00:38:12.160] 00884 1 CVolume::CVolume#31 CVolume object created for volume C:.

[2008-12-08] [00:38:12.160] 00884 1 CVolumeManagerBase::UpdateVolume#277 Volume: C:, size: 392733655040, free: 222590447616, fs: NTFS, name: "".

[2008-12-08] [00:38:12.160] 00884 1 CVolumeManager::OnVolumeAdded#56 Entering CVolumeManager::OnVolumeAdded

[2008-12-08] [00:38:12.160] 00884 1 CVolumeManager::ChangeNotificationOwner::ChangeNotificationOwner#47 Registered notification for "C:\", handle: 0x000001bc

[2008-12-08] [00:38:12.160] 00884 1 CVolume::Initialize#49 Intialization for volume C: started.

[2008-12-08] [00:38:12.160] 00884 1 CVolume::Initialize#82 Volume C: open, handle 0x0000014c.

[2008-12-08] [00:38:12.160] 00884 1 IsFatVolume#16 File system type for volume 0x0000014c is NTFS.

[2008-12-08] [00:38:12.160] 00884 1 CVolume::Initialize#94 GetClustersCount for volume C: returned 95882239 clusters.

[2008-12-08] [00:38:12.175] 00920 1 CVolumeNavigator::CVolumeNavigator#9 Entering CVolumeNavigator::CVolumeNavigator

[2008-12-08] [00:38:12.175] 00920 1 CVolumeNavigator::CVolumeNavigator#9 Leaving CVolumeNavigator::CVolumeNavigator

[2008-12-08] [00:38:12.175] 00920 1 CVolumeNavigator::Initialize#23 Entering CVolumeNavigator::Initialize

[2008-12-08] [00:38:12.355] 0060c 1 CCheckForUpdates::CheckThread#131 CheckForUpdate succeeded. (isUpdateAvailable: 0, newVersion: "1.05.111")

[2008-12-08] [00:38:12.444] 00884 1 CVolume::ReloadMap#226 00 00 00 00 00 00 00 00 ff 0b b7 05 00 00 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

[2008-12-08] [00:38:12.444] 00884 1 CVolume::ReloadMap#239 MftZone: <86759040, 86810272).

[2008-12-08] [00:38:12.464] 00884 1 CVolume::Initialize#120 Raise VolumeMapChangedSignal for volume C:.

[2008-12-08] [00:38:12.464] 00884 1 CVolume::Initialize#124 Intialization for volume C: finished.

[2008-12-08] [00:38:12.464] 00884 1 CVolumeManager::OnVolumeAdded#56 Leaving CVolumeManager::OnVolumeAdded

[2008-12-08] [00:38:12.464] 00884 1 CVolumeManagerBase::UpdateVolume#298 Finish update for bvi C:.

[2008-12-08] [00:38:12.464] 00884 1 CVolumeManagerBase::UpdateVolume#262 Start update for volume D:.

[2008-12-08] [00:38:12.464] 00884 1 CVolume::CVolume#31 CVolume object created for volume D:.

[2008-12-08] [00:38:12.464] 00884 1 CVolumeManagerBase::UpdateVolume#277 Volume: D:, size: 107372085248, free: 74433196032, fs: NTFS, name: "".

[2008-12-08] [00:38:12.464] 00884 1 CVolumeManager::OnVolumeAdded#56 Entering CVolumeManager::OnVolumeAdded

[2008-12-08] [00:38:12.464] 00884 1 CVolumeManager::ChangeNotificationOwner::ChangeNotificationOwner#47 Registered notification for "D:\", handle: 0x00000414

[2008-12-08] [00:38:12.464] 00884 1 CVolume::Initialize#49 Intialization for volume D: started.

[2008-12-08] [00:38:12.464] 00884 1 CVolume::Initialize#82 Volume D: open, handle 0x00000418.

[2008-12-08] [00:38:12.465] 00884 1 IsFatVolume#16 File system type for volume 0x00000418 is NTFS.

[2008-12-08] [00:38:12.465] 00884 1 CVolume::Initialize#94 GetClustersCount for volume D: returned 26213887 clusters.

[2008-12-08] [00:38:12.542] 00884 1 CVolume::ReloadMap#226 00 00 00 00 00 00 00 00 ff fd 8f 01 00 00 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

[2008-12-08] [00:38:12.542] 00884 1 CVolume::ReloadMap#239 MftZone: <4533408, 4573728).

[2008-12-08] [00:38:12.548] 00884 1 CVolume::Initialize#120 Raise VolumeMapChangedSignal for volume D:.

[2008-12-08] [00:38:12.548] 00884 1 CVolume::Initialize#124 Intialization for volume D: finished.

[2008-12-08] [00:38:12.548] 00884 1 CVolumeManager::OnVolumeAdded#56 Leaving CVolumeManager::OnVolumeAdded

[2008-12-08] [00:38:12.548] 00884 1 CVolumeManagerBase::UpdateVolume#298 Finish update for bvi D:.

[2008-12-08] [00:38:12.548] 00884 1 CVolumeManagerBase::UpdateVolume#262 Start update for volume E:.

[2008-12-08] [00:38:12.549] 00884 1 CVolumeManagerBase::GetBasicVolumeInfo#217 Unsupported drive type 5 for volume E:

[2008-12-08] [00:38:12.549] 00884 1 CVolumeManagerBase::UpdateVolume#298 Finish update for bvi E:.

[2008-12-08] [00:38:12.549] 00884 1 CVolumeManagerBase::UpdateVolume#262 Start update for volume F:.

[2008-12-08] [00:38:12.549] 00884 1 CVolumeManagerBase::GetBasicVolumeInfo#217 Unsupported drive type 5 for volume F:

[2008-12-08] [00:38:12.549] 00884 1 CVolumeManagerBase::UpdateVolume#298 Finish update for bvi F:.

[2008-12-08] [00:38:12.550] 00920 1 CVolumeNavigator::ConnectToVolumeSignals#110 Connecting to volume C: signals.

[2008-12-08] [00:38:12.550] 00920 1 CVolumeNavigator::ConnectToVolumeSignals#110 Connecting to volume D: signals.

[2008-12-08] [00:38:12.550] 00920 1 CVolumeNavigator::Initialize#23 Leaving CVolumeNavigator::Initialize

[2008-12-08] [00:38:12.606] 00920 1 CDriveListForm::OnVolumesMapChange#412 Select default volume C.

[2008-12-08] [00:38:12.606] 00920 1 CVolumeNavigator::SelectVolume#271 New volume selected: C:.

[2008-12-08] [00:38:12.607] 00920 1 CFilesListViewImpl::DoSort#263 Sorting 0 elements took 0.0000 seconds

[2008-12-08] [00:38:12.625] 00920 1 CMainFrame::OnCreate#438 Leaving CMainFrame::OnCreate

[2008-12-08] [00:38:12.626] 00920 1 CVolumeNavigator::ConnectToVolumeSignals#107 Signals already connected to volume C:.

[2008-12-08] [00:38:12.632] 00920 1 CVolumeNavigator::ConnectToVolumeSignals#107 Signals already connected to volume D:.

[2008-12-08] [00:38:12.692] 00140 1 CVolume::UpdateDriveMap#317 Map generated in 0.08499 seconds.

[2008-12-08] [00:38:12.754] 00140 1 CVolume::UpdateDriveMap#317 Map generated in 0.06185 seconds.

[2008-12-08] [00:38:28.932] 00920 1 CMainFrame::OnDefragDrive#1008 Moving large files to end fo drive is enabled

[2008-12-08] [00:38:28.932] 00920 1 CMainFrame::OnDefragDrive#1015 Minimum size of large file: 2042

[2008-12-08] [00:38:28.932] 00920 1 CMainFrame::OnDefragDrive#1026 Moving selected types of files is enabled

[2008-12-08] [00:38:28.933] 00920 1 CMainFrame::OnDefragDrive#1034 Categories string: Restore;1|Movie files;1|Disk images;1|Archives;1

[2008-12-08] [00:38:28.933] 00920 1 CMainFrame::OnDefragDrive#1035 Extensions string: *.datan<*.avi|*.mkv|*.mpg|*.mov|*.mp4|*.mpeg|*.wmv<*.bin|*.iso|*.mdf<*.arj|*.tar|*.rar|*.zip

[2008-12-08] [00:38:28.933] 00920 1 CMainFrame::OnDefragDrive#1065 Defrag filtering enabled for extensions: *.datan *.avi *.mkv *.mpg *.mov *.mp4 *.mpeg *.wmv *.bin *.iso *.mdf *.arj *.tar *.rar *.zip

[2008-12-08] [00:38:28.934] 00c98 1 CVolumeOperationScheduler::ExecuteQueuedMethods#201 ---------------- Long task started ----------------

[Guest MrRon]

I will PM you with details of where to send the log.

MrRon

[John Gray]

I will PM you with details of where to send the log.

MrRon

Sent, thanks!

[Darryl]

Almost exact same problem here - defrag works fine for awhile, then goes to 50% CPU (100% on one core), and defragging slows to a crawl. I have 250 GB of stuff on a 500 GB drive, and it's taken 3 hours of chugging so far. It looks like if you abort the defrag halfway through, and start over (CLOSING AN RE-OPENING DEFRAGGLER), defraggler works well again until it gets to about 50%, then slows to a crawl with huge CPU usage again. Specifically, it will take forever to do tiny files. A 20 MB .mp3 file will take 30 seconds to relocate, even though nothing is using it. This is a brand new Vista 64-bit install so things are fragmented, but not THAT bad!

 

If somebody wants a debug file or anything, let me know. Only changes from default are relocate files > 2GB to end of disc.

 

Very frustrating bug, best of luck squashing it!

 

 

 

EDIT: this is a laptop, and I am de-fragging the hard drive. Sorry that wasn't clear.

 

 

Very similar issue here as well. After installing MS Office on a fresh (and previously defragged - with Defraggler) Windows XP SP3 installation with all the latest from Windows Update, I tried to defrag with Defraggler. All seemed to go well until reaching 38% completion, then it appears that it was caught in some type of loop of endless defragging attempts, which actually causeed the number of fragmented files to slowly grow continuously. I started and stopped it three times last evening and let it try to defrag all night.

 

I CHKDSK'ed through XP disk management and am defragging with the built-in XP defragger now. Looking forward to any progress you make with this issue. PM me if you feel I can be of more help in identifying the problem. I am not sure if the defrag loop will be replicable for me again.

[mrmadness]

Note to others: If it is not a external Hard drive, it is not recommended to defrag. USB thumb drives usually use a method to reduce the number of times each memory location is written to increase the life of the thumb drive due to limited number of writes before the drive fails. Defragging a usb key should be done sparingly at most.

 

Just saw this and wanted to clarify further. Defragging anything flash memory (SSD, Jumpdrive etc.) should NEVER, I repeat NEVER, be done. It is not necessary, needed or useful for anything. Defragmenting rearranges files into a contiguous line to minimize access times and cycles on a disk style arrangement. This speeds access times and reduces the amount of head movement that slows read times. Flash memory DOES NOT have this con. It is accessed the same as system RAM. Jumping from one sector to the next in a continuous line requires no more access time than jumping from one sector to the middle or end resulting in 0 latency time. So, if you want to fry your flash memory earlier than predicted, defrag it and notice the 0 improvement in anything except the looks of the colors on the screen. Otherwise, leave it alone. Damage is only done when WRITING! You can read from flash memory an indefinite number of times resulting in no damage (in theory, wear is almost negligible). So, never defrag flash memory. Keep the life up. And save defragging for disk style storage.

 

As a side note, if there was a way to determine if a drive was flash or disk, it would be a beneficial safety mechanism if flash had the option of not being allowed to be defragged. Just a thought.