Am 27.03.2014 20:43, schrieb Brandon I:
That's because your phone uses a sane filesystems that takes into
account this use case and isn't writing constantly (write one byte, the
disk writes a whole erase block). This doesn't protect you from eventual
disk corruption. The wear leveling bad-block type tables will eventually
corrupt/run out of memory loooong before your disk space is eaten by bad
blocks.
Here you are talking about wear-leveling running out of storage because
of too many writes.
It is now an issue with Android!
"T'so says that there isn't much need for concern. Google and the
handset makers will catch platform-level filesystem reliability issues,
ensuring that the high-level storage APIs are safe."
Is the API you use for disk writes safe? Nope.
This article from 2010 seems to talk about inconsistent file systems
because of buffering, i.e. delayed and too few writes.
So which is it? Do you see unrepairable SD-cards or simply SD-cards that
work again after a mkfs? Is it too few or too many writes?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
