This is a very old version of the code. This check was dropped about 18 months 
ago.

This means that a block was found with a higher sequence number. That might be 
a corrupted block.

I would recommend trying a newer version of yaffs2 to see if this is 
corrected.

-- Charles


On Friday 11 December 2009 18:46:19 ??? wrote:
>   Dear sir...
>
>   I found error message. i was occurrence debug error message.
>
>   why do error messag make?
>   what is cause and effect? and what is solve  method?
>
>   i don't know... why do it occurrence?...
>
>   you 'll know.. please , tell me. about  "yaffs: Allocation block xx was
> not highest sequence ""
>
>   please... you'll send E-maill to me. I wish ...
>
>
>   thank you..... Have a good time.... sir
>
>
>
>   [source code contens]
>    In yaffs_guts.c
>    at function : static int yaffs_ScanBackwards(yaffs_Device * dev)
>    version Info : const char *yaffs_guts_c_version =    "$Id:
> yaffs_guts.c,v 1.31 2006/03/08 07:59:20 charles Exp $";
>
>
>
>   /* Yaffs2 sanity check:
>         * This should be the one with the highest sequence number
>         */
>        if (dev->isYaffs2
>            && (dev->sequenceNumber !=
>         bi->sequenceNumber)) {
>         T(YAFFS_TRACE_ALWAYS,
>           (TSTR
>            ("yaffs: Allocation block %d was not highest sequence "
>             "id: block seq = %d, dev seq = %d"
>             TENDSTR), blk,
>            bi->sequenceNumber,
>            dev->sequenceNumber));
>        }