From: Rick Johnson <rick22@wi.rr.com>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: read_pnode: error -22 reading pnode at XX:YYYYY
Date: Mon, 09 May 2011 12:41:03 -0500 [thread overview]
Message-ID: <4DC8272F.5040908@wi.rr.com> (raw)
In-Reply-To: <1304706750.7222.95.camel@localhost>
> 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
next prev parent reply other threads:[~2011-05-09 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 21:08 read_pnode: error -22 reading pnode at XX:YYYYY Rick Johnson
2011-04-21 13:20 ` Artem Bityutskiy
2011-05-05 21:07 ` Rick Johnson
2011-05-06 18:32 ` Artem Bityutskiy
2011-05-09 17:41 ` Rick Johnson [this message]
2011-05-20 21:16 ` Rick Johnson
2011-05-24 8:41 ` Artem Bityutskiy
2011-05-24 11:43 ` Artem Bityutskiy
2011-05-27 20:26 ` Rick Johnson
2011-05-30 16:07 ` Artem Bityutskiy
2011-05-24 19:37 ` Rick Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DC8272F.5040908@wi.rr.com \
--to=rick22@wi.rr.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).