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
On 3/27/2014 12:26 PM, rh_ wrote:
On Thu, 27 Mar 2014 07:41:11 -0500
Charles Steinkuehler char...@steinkuehler.net
wrote:
On 3/26/2014 10:22 PM, Yiling Cao wrote:
Thanks Brandon for your experience. I do agree with that better to
put whole disk read only.
But how do iPhone and Android
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
Rh, my earlier reply was to you, and that link shows that it is now a
problem with androids use of ext4.
On Thu, Mar 27, 2014 at 4:55 PM, rh_ richard_hubb...@lavabit.com wrote:
On Thu, 27 Mar 2014 13:41:24 -0500
Charles Steinkuehler char...@steinkuehler.net
wrote:
On 3/27/2014 12:26 PM,
On 03/27/2014 07:04 PM, rh_ wrote:
On Thu, 27 Mar 2014 16:25:29 -0500
David Lambert d...@lambsys.com wrote:
I have had a long and painful history using flash in general, and
have come to the conclusion that asynchronous removal of power is a
asynchronous? Like pulling the plug and not pushing
