"Gennady Dagman" wrote on Tuesday, September 05, 2006 1:24 PM:
> Bingo !
>
> After applying proposed fix we were able to get rid of various long
> chased yaffs file-system corruptions (yaffs tragedy messages in boot
> time, strange objects in lost+found, kernel Oops'es, lost data in files
> etc). The trigger for all these problems were system reset/reboot
> WITHOUT unmounting yaffs partitions.
>
I would like to understand better what is going on here.
If the filesystem is not properly unmounted, then YAFFS2 can get into an
inconsistent state? This would seem to negate one of the biggest advantages
of yaffs over other filesystems, namely its ability to gracefully handle a
power failure (assuming no write is currently in progress).
> Thanks a lot.
>
> I believe this fix should be applied ASAP to yaffs code in repository.
What fix are you referring to? This? -->
>>I propose to call
>> yaffs_FlushFilesChunkCache(in)
>>before marking object as clean in yaffs_UpdateObjectHeader() function
> Gennady Dagman.
>
Michael
(text/plain)