From: Jean-Philippe Francois <jp.francois@cynove.com>
To: linux-mtd@lists.infradead.org
Subject: Understanding jffs2 warning message
Date: Tue, 19 Jul 2005 14:35:29 +0200 [thread overview]
Message-ID: <1121776529.2565.34.camel@fedorabox> (raw)
Hi,
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)
Node totlen on flash (0xffffffff) != totlen in node ref (0x00001044)
Node totlen on flash (0xffffffff) != totlen in node ref (0x00001044)
Node totlen on flash (0xffffffff) != totlen in node ref (0x00001044)
Node totlen on flash (0xffffffff) != totlen in node ref (0x00001044)
Node totlen on flash (0xffffffff) != totlen in node ref (0x00001044)
Node totlen on flash (0xffffffff) != totlen in node ref (0x00000768)
I looked at the code, but I don't understand what is the meaning of
these messages.
Do you think it can be related to the Top Boot Block layout of this
flash (ie last 64 k sector is replaced by 8 8k sector) ?
I might be wrong, but I think the sector layout and erase size is taken
into account by CFI probing ?
Regards,
JP Francois
[1] : tar/untar loop
#!/bin/sh
i=0
while [ true ]
do
tar -xzf /test.tar.gz
rm /test.tar.gz
sync
echo "pass $i"
md5sum /usr/test/etc/rc3
tar -czf /test.tar.gz /usr/test/
rm -r /usr/test/
sync
let i=i+1
done
next reply other threads:[~2005-07-19 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 12:35 Jean-Philippe Francois [this message]
2005-07-19 13:06 ` Understanding jffs2 warning message Artem B. Bityuckiy
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=1121776529.2565.34.camel@fedorabox \
--to=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