UBIFS power cut issues

[Bill Gatliff]

Artem Bityutskiy wrote:
> And the text here, just in case someone would review it.
>   

When you mean "something is lost", the correct spelling is "lose".  To 
"loose" means to "disconnect", or "release" something.


> However, UBIFS is sometimes used as a JFFS2 replacement and people may
> want it to behave the same way as JFFS2 if it is mounted synchronously.
> This is doable, but needs some non-trivial development, so this was not
> implemented so far. On the other hand, there was no strong demand. You
> may implement this as an excercise, or you may try to convince UBIFS
> authors to do this.
>   

In summary, the differences in results between JFFS2 and UBIFS in the 
case of interrupted, large synchronous writes are related to differences 
in how the two store and/or compute file sizes?

Based on your documentation, my understanding is that with JFFS2 file 
sizes are stored along with the file data nodes, and are updated as the 
file grows in size--- so an interruption truncates the file at the point 
the interruption occurs.  For UBIFS, in contrast, file sizes are stored 
in separate nodes which might not have been written at the point of 
interruption--- so the state if the file when power is restored depends 
highly upon the precise moment that the interruption occurs.



b.g.

-- 
Bill Gatliff
bgat at billgatliff.com