read_pnode: error -22 reading pnode at XX:YYYYY

[Rick Johnson]

> I do not know by heart, but I think cnext is about the list of nodes
> which should be written to the flash at the next commit. So if ->cnext
> == ->parent this means that our parent is the next in the list. Hmm, and
> I think we dirty nodes in the LPT tree from the bottom up to the root,
> and add them to the commit list (cnext), so cnext == parent should be
> very common.
> 
> But in 'read_pnode()' cnext must be NULL, I think.

That makes sense with what we're seeing.


> Anyway, as I said, that was not my code, so I myself have difficulties
> to deal with it. I asked Adrian to help  - may be he'll take a look at
> this if he has time.

Thank you for passing the word along.

> Sure. I hope you'll nail this. How well is it reproducible? Can you
> reproduce this on nandsim which has equivalent characteristics (PEB
> size, page size, count of PEBs) ?

This is real tough to reproduce.  It happens just enough to give us 
trouble.  We haven't tried nandsim before, but I'll see if we can get 
that going.

Thanks again.

Rick