Re: [PATCH] mmc: Multi-sector writes

[Pierre Ossman]

Pavel Machek wrote:

>>* Transport problem. The driver will report back a CRC error, timeout or
>>whatnot and break. We might not know how many sectors survived so we try
>>again, going sector-by-sector. We might get a transfer error again,
>>possibly even before the previous one. But at this point the transport
>>is probably so noisy that we have little chans of doing a clean umount
>>anyway. So when the device gets fixed, either by replaying the journal
>>    
>>
>
>Well, but then you can get:
>
>good data #1
>trash #2
>good data #2
>trash #1
>
>I'm not sure how much journalling filesystems will like that in their journals...
>
>  
>

Unless the card is horribly broken it will not write sectors that cannot
be transfered successfully. If there would be a transport error that
goes undetected by the CRC we would just continue, believing that
everything is peachy.

The scenario you're describing could show up in the case of a media
error though. But that would mean that a sector went bad in an extremely
short time, which isn't likely unless the wear leveling has gone crazy
or the card is completely worn out. Either way the card is no longer useful.

Rgds
Pierre

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/