Reconstructing Directory Tree

[mdoenges]

Hello,
This particular step of the process is taking forever 14% over 22 hours
I am not sure if it is supposed to do this or not
Please HELP

[Alexey V. Gubin]

Could you please provide some more details, like

Filesystem type?
Volume size?
What is the indicated CPU usage?
What is at the end of the log file, C:\Program Files\ZAR\logfile.txt?

[mdoenges]

File System is NTFS
80 gig hdd -
Reconstructing Directory Tree at 21% now after 38 hours
2882561 files in 16764 folders

in task manager, the memory for zar grows for a while, then drops back down
when it drops back down the proc jumps to like 24% for a min , otherwise proc usage never seems to exciede 2%

Please advise, Any info would be appreciated. Thank you so much


last modify date on log file was 10/26 at 11:35pm


ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 9520
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 13456
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 12704
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 6176
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 2801
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 2768
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 5760
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 2736
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 5680
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 2720
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 8688
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 6000
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 8544
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 11728
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 5552
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 11408
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 14688
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 2864
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 2752
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 5792
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 16082
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 34800
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 53568
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 76144
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 98112
ALERT!: MISSING RL ENTRY ; AttrType=00000080; RealSize=0; AllocSize=0; RlCount=1; Need 0, found 5664

[mdoenges]

Quick Update
23% at 44 hours

[mdoenges]

Another update with picture
30% 62 hours

any info would be appreciated.
Is this a savepoint?
Should i be rebooting here to try and speed things up
I will continue to let this run until i am told otherwise but any information you can give me will help/
Mike

[Alexey V. Gubin]

We're probably looking at the extermely fragmented volume, or the volume is damaged bad enough so that it appears fragmented. I'd say just leave it as it goes. If you restart, make sure you turn logging off, in "Advanced Configuration", that should give some improvement. Something about 10-20% speed up, that would be.