Re: Defragment flash drive on Vista


"Bill in Co." <not_really_here@xxxxxxxxxxxxx> wrote in message
news:OIyM5SOsIHA.1236@xxxxxxxxxxxxxxxxxxxxxxx
Updated below...

Bill in Co. wrote:
M.I.5¾ wrote:
"Michael Lanier" <jamaica@xxxxxxxxxxx> wrote in message
news:0a85f12c8e9f42d79f10e0b727be1849@xxxxxxxxxxxxx
XP allows me to defragment drives other than my hard drive. I am
unable
to find that capability on my Vista. Is it available and how would I
access it.
Thanks.

url:http://www.ureader.com/gp/1279-1.aspx

Under any operating system, I would be reluctant to defragment any FLASH
memory drive for 2 reasons.

1. The multiple file fragment shifts that are required during any
defragment
operation are going to severely tax the limited life of the FLASH memory
blocks (limited to an *average* of 1000 erase/write cycles).

Is that documented somewhere? Or does it vary all over the place?

Actually, I just spent a bit of time looking this lifetime thing up now,
and I'm seeing articles mentioning 10,000 - 100,000 erase/write cycles,
not 1000. So while it's true that defragging will tap into this a bit,
occasionally doing it probably wouldn't be all that harmful (although
there isn't much point).

There is confusion because there are 2 lives associated with FLASH memory
cells. The regular memory blocks (the ones that actually hold the data) are
lifed for an average of 1000 erase/write cycles. These blocks are utilised
on a rotating basis to ensure that the least recently erased and written
block is the next one to be erased and written (this is called 'wear
levelling' and is designed to extend the life as far as possible). However,
every FLASH memory device also has a block that holds the houskeeping data
such as the FATs and in which block the data is actually held. This block
has to have a much greater life because it has to be completely erased and
rewritten every time the memory is altered. It is this block that is lifed
for 100,000 erase write cycles. The architecture of FLASH memory cells is
designed to keep the cost down as much as possible, and it is a fact of
these devices that if one block fails (be it data or houskeeping), the whole
memory device is rendered useless.

Fortunately it is only the erase/write that is life limited. If the memory
can be written and verified, then the read life is, thankfully, relatively
infinite. That makes this type of memory ideal for holding device firmware
that may be updated relatively infrequently, but its use in USB thumb
drives, though not ideal, is considered acceptable because the low cost of
the memory means that the drives can be cheaply replaced when a failure does
occur. I have got through several.

If you have ever watched the graphic representation of file fragment
movements that occur when a drive is defragmented, you will appreciate that
a FLASH drive will get one hell of workout as the defragmentation proceeds.


.

Relevant Pages

  • Re: NAND Based Flash RAID
    ... >>> Flash memory is a popular choice for smaller drives. ... >>> to the same addresses will quickly wear out that portion of the memory. ... "Flash drives have taken over mobile drives in extreme environments"? ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: Life Expectancy of Flash Memory Drives
    ... my PNY Atache flash memory stick drive started to fail on me. ... > these type drives to last under daily use as a Knoppix persistant home ...
    (comp.os.linux.setup)
  • Re: Life Expectancy of Flash Memory Drives
    ... my PNY Atache flash memory stick drive started to fail on me. ... > these type drives to last under daily use as a Knoppix persistant home ...
    (comp.os.linux)
  • Re: Cropping Sunlight
    ... Unfortunately the memory cost has been dropping largely because the ... The expensive flash drives meant for inside laptop computers store a lot ... write life. ...
    (uk.business.agriculture)
  • Re: Mars Rover Not Responding - Update - NASA Makes Contact With Mars Rover
    ... operations that we performed on the vehicle last night. ... that memory. ... "We have flash memory. ... confirmed because later we had a UHF communications session with Odyssey ...
    (comp.object)