View Single Post
  #14  
Old March 24th 21, 05:28 PM posted to alt.comp.os.windows-10,comp.sys.ibm.pc.hardware.storage
J. P. Gilliver (John)[_3_]
external usenet poster
 
Posts: 24
Default SSD "overprovisioning"

On Wed, 24 Mar 2021 at 08:24:36, Paul wrote (my
responses usually follow points raised):
J. P. Gilliver (John) wrote:

If, after some while using an SSD, it has used up some of the slack,
because of some cells having been worn out, does the apparent total
size of the SSD - including unallocated space - appear (either in
manufacturer's own or some third-party partitioning utility) smaller
than when that utility is run on it when nearly new?


The declared size of an SSD does not change.

The declared size of an HDD does not change.

What happens under the covers, is not on display.


That's what I thought.

The reason you cannot arbitrarily move the end of a drive,
is because some structures are up there, which don't appear
in diagrams. This too is a secret.

Any time something under the covers breaks, the
storage device will say "I cannot perform my function,
therefore I will brick". That is preferable to moving
the end of the drive and damaging the backup GPT partition,
the RAID metadata, or the Dynamic Disk declaration.

Paul


So how come our colleague is telling us we can change the amount of
"overprovisioning", even using one of many partition managers _other_
that one made by the SSD manufacturer? How does the drive firmware (or
whatever) _know_ that we've given it more to play with?
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

It's no good pointing out facts.
- John Samuel (@Puddle575 on Twitter), 2020-3-7