Quote:
Originally Posted by knc1
Correcting the source of the error message you received.
Of course fsck is drastically faster on spinning rust, spinning rust is drastically faster than flash rom.
|
Not so. fsck does relatively few writes -- it tries to keep the amount of change to a minimum, though the change will be scattered across eraseblocks and thus have a horrible write amplification. What it does is a *lot* of seeking, which is nearly instantaneous on flash.
Quote:
*) Each time an error, either in the data recorded (in this case a file system) or in the underlying storage media, is encountered - -
**After** the device corrects itself internally, the whole fsck process has to be started again.
|
Oh god. If it's repeatedly rerunning fsck in the blind hope that maybe it'll work if it keeps trying enough, that might explain it.
Quote:
The reason you don't see this situation with the SSD in your (whatever) other device is because it is hidden by the controller inside of the device.
The micro-controller in an SSD is much more "intelligent" than that of an eMMC device.
|
Good point. (Though I'm not the person who had the problem, I'm just a curious bystander who knows how e2fsck works.)