From: "陳羿逞 \\(Chuck\\)" <ycchen@realtek.com.tw>
To: <linux-mtd@lists.infradead.org>
Subject: CRC error of jffs2_get_inode_nodes() for JFFS2 on NAND
Date: Tue, 8 Nov 2005 16:36:12 +0800 [thread overview]
Message-ID: <010201c5e43f$796bd5f0$135415ac@realtek.com.tw> (raw)
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
Hello all,
Our system use JFFS2 on NAND flash, and code base is linux 2.6.10-rc3.
A few days ago, we dived into the JFFS2 for the CRC error after a system reboot.
We found that it is caused by an incomplete writing and it always happens in the end of file.
If we write some data into flash which size is not the multiple of page_size (512-byte),
there is a remainder (under a page-size) in 'wbuf' of function jffs2_flash_writev().
Then, at this time, we reset the system, JFFS2 will not yet write the remainder into flash and it will cause the inode incomplete.
Is it normal ? What time will JFFS2 flush wbuf out to sync the data if there is a remainder in wbuf ?
I appreciate if anyone can give us some suggestion.
best regards,
Chuck Chen
[-- Attachment #2: Type: text/html, Size: 2008 bytes --]
next reply other threads:[~2005-11-08 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 8:36 陳羿逞 \(Chuck\) [this message]
2005-11-13 13:09 ` CRC error of jffs2_get_inode_nodes() for JFFS2 on NAND Artem B. Bityutskiy
2005-11-14 6:26 ` 陳羿逞 \(Chuck\)
2005-11-14 9:43 ` Artem B. Bityutskiy
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='010201c5e43f$796bd5f0$135415ac@realtek.com.tw' \
--to=ycchen@realtek.com.tw \
--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