From: Artem Bityutskiy <dedekind1@gmail.com>
To: Shane Volpe <shanevolpe@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 what file is a given node in?
Date: Tue, 24 Aug 2010 16:10:49 +0300 [thread overview]
Message-ID: <1282655449.24044.173.camel@localhost> (raw)
In-Reply-To: <AANLkTikWFqbH-s2Uo8TjW-fX2jkYdGH=9oKp17yVqZ7F@mail.gmail.com>
On Tue, 2010-08-24 at 08:52 -0400, Shane Volpe wrote:
> I get the following message:
> <4>Data CRC 0550f35b != calculated CRC 81fbb81c for node at 02aedb74
> I want to find out what file this node is in so I can further
> investigate the corruption, how do I do that?
Add a printk to the corresponding piece of code?
Also, notice that these messages are usually harmless and appear because
or unclean reboots.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-08-24 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 12:52 JFFS2 what file is a given node in? Shane Volpe
2010-08-24 13:10 ` Artem Bityutskiy [this message]
2010-08-24 17:53 ` David Woodhouse
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=1282655449.24044.173.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=shanevolpe@gmail.com \
/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