From: llandre <r&d2@dave-tech.it>
To: linux-mtd@lists.infradead.org
Subject: JFFS2: file contents in case of data CRC error
Date: Thu, 31 Jan 2008 17:54:23 +0100 [thread overview]
Message-ID: <47A1FD3F.2020102@dave-tech.it> (raw)
I have a JFFS2 partition on 32MByte NAND device.
When reading a specific file - see below for details - JFFS2 reports a
Data CRC error but function nand_correct_data never returns -1, so I
assume ECC algorithm is able to correct errors.
However the file is not equal to the original one that has been written
to NAND. In fact, in the middle of the file, I see a 4-kByte "hole"
where all bytes are 0.
Anybody can help me about understanding if this is the expected
behaviour of JFFS2?
Thanks in advance.
bash-2.05# mount -t jffs2 -o ro /dev/mtdblock0 /mnt/nand0
mtdblock_open
ok
bash-2.05# cp -v /mnt/nand0/f.img /tmp/
jffs2_get_inode_nodes(): Data CRC failed on node at 0x01d55544: Read
0x80b8997f, calculated 0x57f0ea8e
`/mnt/nand0/f.img' -> `/tmp/f.img'
--
llandre
DAVE Electronics System House - R&D Department
web: http://www.dave.eu
email: r&d2@dave-tech.it
next reply other threads:[~2008-01-31 16:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 16:54 llandre [this message]
2008-01-31 19:19 ` JFFS2: file contents in case of data CRC error Korolev, Alexey
2008-02-01 14:00 ` llandre
2008-02-01 15:53 ` Korolev, Alexey
2008-02-01 17:43 ` Jamie Lokier
2008-02-02 17:11 ` llandre
2008-02-04 21:32 ` Jamie Lokier
2008-02-02 16:32 ` llandre
2008-02-04 14:25 ` Korolev, Alexey
2008-01-31 19:22 ` Jffss2_write_super erasing all the blocks Nikhil Bansal (nikbansa)
2008-02-02 19:30 ` SV: " Joakim Tjernlund
2008-01-31 19:42 ` JFFS2: file contents in case of data CRC error Matt Reimer
2008-01-31 22:57 ` Jamie Lokier
2008-02-01 14:01 ` llandre
2008-02-01 14:01 ` llandre
2008-02-02 17:03 ` llandre
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=47A1FD3F.2020102@dave-tech.it \
--to=r&d2@dave-tech.it \
--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