Although that statement may have "some" truth to it, like Ed said, all file systems should be defragged on a regular basis depending on the amount of change that occurs on the drive (moving data across partitions, adding/deleting files & programs, etc).
Typically for an end user, once every 4-5 weeks is good enough. If you find that you need to do it more often, then instead you should be looking for a way to better manage your data. Separate it into partitions (create at least one extra partition for non-system data/apps).
~cdogg
[tab]"All paid jobs absorb and degrade the mind";
[tab][tab]- Aristotle
[tab][navy]For general rules and guidelines to get better answers, click here:[/navy] faq219-2884
Yep. That makes a huge difference. The impact of fragmentation increases with the pecentage of disk space used on a partition.
Also remember that the type of usage is important. Unless newer data is replacing older data often, then you don't have to worry as much.
I, too, rarely defrag since moving to NTFS. My system partition remains almost constant with hardly any change, while my data partition though much more active is almost always at least 50% free. I've maybe only defragged twice in a year.
~cdogg
[tab]"All paid jobs absorb and degrade the mind";
[tab][tab]- Aristotle
[tab][navy]For general rules and guidelines to get better answers, click here:[/navy] faq219-2884
The amount of fragmentation also depends on file size. Here at work, I have a drive that is approx 50% full and highly fragmented (approx 4-50%). It's an NT4 NTFS volume and won't defrag. And yes, it's very slow. Actually I probably should take the server off line and defrag it. Another server containing a 7gig SQL table get backed up every night and the backups zipped and burned to a DVD from a local pc. The backup file is approx 4.7 gig and zipped is over 800 meg. Guess what, it fragments my drives and performance reduction can be noticeable. YES, I KNOW I need more drive space, but when money is tight, managers and VP's can be reluctant to spend the money needed to replace aging equipment.
And users know when something is going on with the system. And I definetly hear about it.
Boot problems are frequent in heavily fragmented scenarios in the case of Windows 2000 as well as Windows XP systems. High fragmentation of MFT in NTFS partitions can cause trouble and call for a routine defrag policy.
Boot problems can happen in the case of excessive fragmentation in 2000 and XP also.
You can refer Microsoft Knowledge Base Q228734. According to this document, “This issue can occur
when the NTFS bootsector code contained in logical sector zero of an NTFS
volume is unable to locate and load NTLDR into memory due to the Master
File Table (MFT) being highly fragmented.”
If circumstances permit, frequent defragging is a good idea cos a heavy backlog of fragmentation is prevented. The default defrag program supplied by Microsoft works quickly if the volume is lightly fragmented. It must reduce wear and tear on a HDD if the excess seeks that must result from a heavily fragmented disk are allowed to continue over a long period.
A SCSI drive (or other) which allows elevator seeks will considerably mitigate the effects of fragmentation. Also putting the page file on a HDD of its own will help enormously, especially with IDE HDDs. Vast quantities of RAM will allow a huge disk cache to reduce the evils of fragmentation.
There will never be agreement on this issue because we all conceptualise such a dynamic mechanism differently.
OOPS!
I meant to say "It must increase wear and tear on a HDD if the excess seeks that must result from a heavily fragmented disk are allowed to continue over a long period."
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.