Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Defragmentation Question

Status
Not open for further replies.

kovacsa

MIS
Apr 3, 2003
100
CA
Hello .. Is it true that NTFS partitions do not require defragmenting as much as FAT or FAT32 partitions?

Thanks,

kovacsa
 
kovacsa;

All Windows file systems need defraging on a regular basis.

Follow this link:


Ed


Please let me know if the suggestion(s) I provide are helpful to you.
Sometimes you're the windshield... Sometimes you're the bug.
smallbug.gif
 
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
 
I'd tend to disagree. Have run 2k & XP on ntfs installs for years without defrag - with no noticeable degradation.

Have also tried defragging other installations - just to see if they improve - haven't notice any improvement.

This may be due to my human senses not being up to noticing the difference - but that's what matters to me (and defrags can take so long...)

PS. I also use partitions which are generally < 50% full, which probably also helps.

 
I also use partitions which are generally < 50% full, which probably also helps

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 are frequent in heavily fragmented scenarios in the case of Windows 2000 as well as Windows XP systems."

Could you provide some studies or other sources for this claim?

 

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.”
 
That MS KB article specificly says it does not apply to Windows 2000, and therefore presumably XP as the boot loader is similar.

The issue is that Windows NT can run out of RAM to process the MFT and find its loader files.
 
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.

Null illegitimus carborundum
 

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."


Null illegitimus carborundum
 
A regular defragmentation is a good idea. I do a thorough one twice a year, including boot time optomization during defragmentation.

But for the NT 5.x family under NTFS it is over-rated. See, for example,
This is decidedly a contrarion view, but the gist of it I agree with under NTFS.

Servers, they are quite a different issue. Let your server Administrators worry about this.
 
Hi,

I have used O&O Defragger on all installations of Windows 2000 (pro and server) and XP for about 2 years now since a colleague of mine suggested it.

As a result we have drastically cut the amount of failed disks and generic "my machine is slow" problems.

O&O runs as a service, its a "set and forget" method which keeps the disk defragmented.

Highly recommended
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top