[Sugar-devel] Additional data for corrupted SoaS

[Sascha Silbe]

On Sun, Aug 02, 2009 at 09:47:22AM +1000, James Cameron wrote:

> This means that a particular block could not be read from the device,
> either due to a communication problem between your CPU and the device,
> or because the device itself has the block marked as flawed.
My point is that this stick is too unreliable for regular use. Normal 
filesystems (ext3 et al.) aren't fault-tolerant.

>> If it's sucessfull, the whole stick will have been read:
> Actually, it is better to say if it is successful then the return 
> status will be zero.  Judging only by the size of the data or the lack 
> of error messages is not as reliable.
Care to elaborate? Why would it return a non-zero error code, but not 
print an error message?

> Cause of the flaw?  Either a block has deteriorated to the point that 
> it
> cannot be read (the lifetime is not infinite), or it was erased as 
> part
> of being written but the write did not complete.
I can rule both out as the same stick reads fine on a different computer 
(both results are repeatable, so not just an intermittent error). It's 
the USB interface that's unreliable, not the NAND (=storage).
The stick hasn't ever been used (by me), BTW - only written once by 
Caroline. So tear cannot be an issue.

CU Sascha

-- 
http://sascha.silbe.org/
http://www.infra-silbe.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: Digital signature
Url : http://lists.sugarlabs.org/archive/sugar-devel/attachments/20090802/622e50da/attachment.pgp