locked
SP1 Defragmenting is now on hour 12 and still not done... RRS feed

  • Question

  •  

    The drive is a RAID 0 - two Raptor 150 GB 10K rpm drive for total of 279 GB.  The drive only has 80GB of data on it.

     

    Defragmenting this drive has been going on for 12 hours now.  I still see disk activity, but the useless defragmenting interface shows NO progress indication at all, just the spinning wheel.  Now, correct me if I'm wrong, but WinXP at least did an analysis, reported the fragmentation, and then showed what it was doing and the progress of what it was doing.

     

    I paid $400 for this OS, and I get less than what WinXP can do for defragmentation????

     

    Perhaps the message should say "This may take from a few minutes to a few weeks" -- ya know, cover all your basis...

     

    What happened Microsoft??  How could one company get so lost?  Too much out sourcing?  Just ignorance?  Bad executive management?  What happened to a company that used to split their stock prices every year?

    • Moved by Carey FrischMVP, Moderator Wednesday, December 21, 2011 5:22 PM Move to more appropriate forum category (From:Windows Vista Service Packs/Windows Server 2008 Service Packs)
    Tuesday, September 9, 2008 2:55 PM

Answers

  • Rob

     

    I'm sorry that this was not what you wanted to hear, but all I can do is explain the way Vista works, and point you to the explanations about why certain components were changed.

     

    Microsoft does respond to feedback and they do make changes based on that feedback. Being an operating system that does 'everything' for 'everybody' would be nice, but of course this would be impossible to attain for obvious reasons.

     

    In the case of the defrag component, the most asked for change was the ability to select or deselect the drives when manually running defrag. This was changed in SP1.

     

    The old defrag was very problematic and this is why it was reconfigured to run as a low priority background process. The user can now simply use the system and defrag does it's job,  stays out of the way, and only runs when the system is idle. The user can continue getting their work done.

     

    Don't mistake 'low priority' with 'slow'. If a component is running a low priority process, this simply means that it will pause and 'stay out of the way' if a higher priority process starts. You also have the option of 'elevating' the priority for any process by using the Task Manager.

     

    I'm not sure why defrag is taking so much time on that drive, but it could simply be that it has a lot of files to move around.

     

    Microsoft provides a very good feedback mechanism. You can tell them your concerns and what you would like changed at the following website.

     

    Windows Vista Product Feedback:
    https://feedback.windowsvista.microsoft.com/default.aspx?productkey=winvista

     

    Hope this helps.


    If this post helps to resolve your issue, click the Mark as Answer or Helpful button at the top of this message.
    By marking a post as Answered, or Helpful you help others find the answer faster.


    Ronnie Vernon
    Microsoft MVP
    Windows Desktop Experience

    Tuesday, September 9, 2008 6:01 PM
    Moderator

All replies

  • Rob

     

    The Disk Defragmenter has been deprecated to a low priority background process for various reasons. Take a look at the following pages for the specific reasons and thoughts about why this was done.

     

    The Storage Team at Microsoft - File Cabinet Blog : Don’t judge a book by its cover – why Windows Vista Defrag is cool:
    http://blogs.technet.com/filecab/archive/2007/01/26/don-t-judge-a-book-by-its-cover-why-windows-vista-defrag-is-cool.aspx

     

    The Storage Team at Microsoft - File Cabinet Blog : Disk Defragmenter FAQ:
    http://blogs.technet.com/filecab/articles/440717.aspx

     

    Advanced users can still run an analysis and get the current state of file fragmentation on a particular drive using the command prompt. Type  defrag /?  to see the syntax and paramenters.

     

    If you have SP1 installed, you can select or deselect individual drives in the UI.

     

    Hope this helps.


    If this post helps to resolve your issue, click the Mark as Answer or Helpful button at the top of this message.
    By marking a post as Answered, or Helpful you help others find the answer faster.


    Ronnie Vernon
    Microsoft MVP
    Windows Desktop Experience

    Tuesday, September 9, 2008 4:22 PM
    Moderator
  •  

    Ronnie,

     

    Thank you for the response.  I can understand the low priority setting when disk defrag is running "unattended", BUT I'm running the process "attended" -- as in the interface/window is open (not minimized).  I would hope that my intentions are clear (from an end user perspective) that I'm wanting the task to be of elevated priority since I actively have the interface window open.

     

    Since I'm a developer, I know it's not terribly difficult to determine "attended" vs. "unattended" and issue worker thread process with appropriate priority.  Or provide the option to the end user if you don't want to "risk" (of which there really is none) the assumption.

     

    2nd point, the same disk defrag on my WinXP PC finished in 1 hour and 25 minutes.  As you can see, Vista Defrag still has got some serious problems in SP1.

     

    Sorry if I seem harsh, but again, this is a $400 OS (Ultimate version) that took 5 years to produce and another 18 months to SP1 -- so 6.5 years in the making.  I expect the OS to be more intelligent rather than "just enough".

     

    To sum up the Microsoft experience, the OS has no logic for "intelligent use of user context" -- this is one of many reasons why Vista has not become an OS the people want.  Your consumers don't want to be bombarded with questions (some of which they can't possibly understand nor answer), they want and expect the OS to have some intelligence about what context the user is in and how to come up with appropriate settings for that context.  Optimally the disk defrag process should be aware that no other tasks are running that require/demand priority based on there CPU usage (again all available to an intelligent application) and increase is priority on the fly.

     

    No the post didn't help resolve my issue.

     

    Rob.

     

     

    Tuesday, September 9, 2008 4:54 PM
  • Rob

     

    I'm sorry that this was not what you wanted to hear, but all I can do is explain the way Vista works, and point you to the explanations about why certain components were changed.

     

    Microsoft does respond to feedback and they do make changes based on that feedback. Being an operating system that does 'everything' for 'everybody' would be nice, but of course this would be impossible to attain for obvious reasons.

     

    In the case of the defrag component, the most asked for change was the ability to select or deselect the drives when manually running defrag. This was changed in SP1.

     

    The old defrag was very problematic and this is why it was reconfigured to run as a low priority background process. The user can now simply use the system and defrag does it's job,  stays out of the way, and only runs when the system is idle. The user can continue getting their work done.

     

    Don't mistake 'low priority' with 'slow'. If a component is running a low priority process, this simply means that it will pause and 'stay out of the way' if a higher priority process starts. You also have the option of 'elevating' the priority for any process by using the Task Manager.

     

    I'm not sure why defrag is taking so much time on that drive, but it could simply be that it has a lot of files to move around.

     

    Microsoft provides a very good feedback mechanism. You can tell them your concerns and what you would like changed at the following website.

     

    Windows Vista Product Feedback:
    https://feedback.windowsvista.microsoft.com/default.aspx?productkey=winvista

     

    Hope this helps.


    If this post helps to resolve your issue, click the Mark as Answer or Helpful button at the top of this message.
    By marking a post as Answered, or Helpful you help others find the answer faster.


    Ronnie Vernon
    Microsoft MVP
    Windows Desktop Experience

    Tuesday, September 9, 2008 6:01 PM
    Moderator
  • I, too, am having a problem with how slow the defrag is taking; however, I know that I have about 250g for it to run through.  I tried using the defrag/?  in the comman prompt, but it just tells me that a defrag or volume shrink op is already in progress, and to wait until the current process finishes and then try again.

    I would like to see if the defrag is working or if it is just stalled.  Any advice?  It's been running for about 10 hours now.

    TIA!

    Wednesday, December 21, 2011 2:30 PM
  • Consider using a robust third-party solution, such as PerfectDisk.  There is a free trial version available.
    Carey Frisch
    Wednesday, December 21, 2011 5:21 PM
    Moderator