From: "Artem B. Bityuckiy" <dedekind@yandex.ru>
To: jp.francois@cynove.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: Understanding jffs2 warning message
Date: Tue, 19 Jul 2005 17:06:06 +0400 [thread overview]
Message-ID: <42DCFABE.7040002@yandex.ru> (raw)
In-Reply-To: <1121776529.2565.34.camel@fedorabox>
Jean-Philippe Francois wrote:
> I am doing some test on a JFFS2 file system.
> It is installed on a Macronix Flash 29LV320, with top boot block.
> The part are cfi probed, and it works (almost) fine.
>
> I am doing some tar/untar loop [1]. Every six or seven loop, I have a
> serie of 8 warning messages :
>
> Node totlen on flash (0xffffffff) != totlen in node ref (0x00001040)
> Node totlen on flash (0xffffffff) != totlen in node ref (0x00001044)
You don't do unclean reboots? If not, this is wierd. This means that the
node on flash is somehow got corrupted.
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2005-07-19 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 12:35 Understanding jffs2 warning message Jean-Philippe Francois
2005-07-19 13:06 ` Artem B. Bityuckiy [this message]
2005-07-19 13:16 ` Jean-Philippe Francois
2005-07-20 7:30 ` Jean-Philippe Francois
2005-07-21 14:24 ` Jean-Philippe Francois
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=42DCFABE.7040002@yandex.ru \
--to=dedekind@yandex.ru \
--cc=jp.francois@cynove.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