AFV060
First Officer, A330-200
Joined on January 27 2006
Eastern Canada
1 legs, 8.5 hours
57 legs, 252.9 hours total
|
Posted onPost created on
February 25 2007 00:06 ET by Matthew Sark
|
DVA3432
First Officer, B777-200
Joined on August 07 2006
Century Club
"Mile High Blackout" Aurora, CO USA
152 legs, 525.6 hours
43 legs,
139.8 hours online 101 legs,
431.8 hours ACARS 3 legs,
5.4 hours event
|
Posted onPost created on
February 25 2007 12:18 ET by Mike Peterson
|
DVA1628
Captain, B767-300
Joined on April 09 2004
Online Double Century Club
Triple Century Club
"The DL757 at BNA is once again gone" Gallatin, TN USA
307 legs, 575.5 hours
297 legs,
559.5 hours online 234 legs,
441.8 hours ACARS
|
Posted onPost created on
February 25 2007 15:25 ET by Glen Novitsky
|
Defraging a drive is not necessary on your recovery partition. Defragging is needed on drives, because, as you write and delete files to the HD, the data gets chopped up. To make it simple, at first, if you delete a 100MB file, then add a 200MB file, then the HD will put the first 100MB of the 200MB in the open slot from the deletion, then down the HD road, at the next open spot, it puts the remaining 100MB. Thats why a fragmented drive is slower than one that hasn't been defragged. It has to go to two, and sometimes many more spots to load the data. Defragging simply puts as many of the data files into their each continuous file, in one location, not broken up on the HD. Now, this is an OVERLY simplfied example, but basically true.
If you haven't touched your recovery drive, all the data should still be in line, and thus nothing is needed to clean up. Besides that, even if it DID need to be defragged, you should only be using that partition during a recovery, so if its a little slow, it really wouldn't matter, as recovering is more a quality thing than a speed thing....
Glen NovitskyCaptain, B767-300
|
|