ScheduledDefrag running when it shouldn't be!

[Guest]

I have the default defrag scheduled for 01:00am every Wednesday, which is
fine. I understand that if the PC is shutdown then this defrag continues
after it starts up once the PC is idle.

So, the defrag was scheduled to start wed 22/8.

From the "Computer Management" console window I select "System Tools -> Task
Scheduler" which displays the task status of all scheduled tasks. I can see
here the following entries:

Task Name Run Result Run Start Run End
- ScheduledDefrag (last run was stopped at 24/08/2007 10:32:21)
ScheduledDefrag Stopped 24/08/2007 10:29 24/08/2007
10:32
SchedulesDefrag Stopped 24/08/2007 09:15 24/08/2007
09:17
ScheduledDefrag Success 23/08/2007 19:24 23/08/2007
19:56

The question is, why, if the scheduled Defrag succeeded on the 23/08/2007
19:56 is it running again on the 24/08/2007?


In the Active Tasks section of the window, I can see the entry:
Task Name Next Run Time Triggers
ScheduledDefrag 29/08/2007 01:00 At 01:00 every Wednesday


Can anyone help me understand why defrag is running again?

Thanks,

Rob

 

[Guest]

I have the default defrag scheduled for 01:00am every Wednesday, which is
fine. I understand that if the PC is shutdown then this defrag continues
after it starts up once the PC is idle.

defrag works in this way:
1. it begins to work at scheduled time, if you're not using your PC;
2. you have a coffee break, then defrag will start
3. you return using your PC, then defrag will pause
4. you go to restroom, then defrag will continue to work
etc.
.... until the disk is defragmented.
So the defrag is executed at steps, during severals days when you're not
using your PC.

 

[Guest]

Thanks Bill,

I understand that, but I thought that "Success" meant that the task had
completed. Then it seems to have started again - before the next scheduled
date. That's the part I don't understand..

/Rob

 

[Guest]

Found the history data under the properties for the task. It's a bit of a
mess filled with lots of errors regarding failed task starts due to already
running instances.. Think somehow I've got multiple tasks trying to run at
the same time - not sure why though!

I'm going to temporarily turn off the scheduling to try to clear out the
active tasks...

/Rob