From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: "\"陳羿逞 \\\\(Chuck\\\\)\"" <ycchen@realtek.com.tw>
Cc: linux-mtd@lists.infradead.org
Subject: Re: CRC error of jffs2_get_inode_nodes() for JFFS2 on NAND
Date: Mon, 14 Nov 2005 12:43:36 +0300 [thread overview]
Message-ID: <43785C48.1010202@yandex.ru> (raw)
In-Reply-To: <007e01c5e8e4$5fb80490$135415ac@realtek.com.tw>
> Thanks for your information.
> Dose it to say that is there a possibility to make data missing if we
> interrupt the GC operation just like shutdowm the system before a wbuf flush
> ?
> In my system, the JFFS2 CRC error of inode always happens after a reboot.
Yes, in case of unclean reboots you loose the write-buffer's contents.
It contains the most recently data only. To force sync-ing you may do
fsync() in your applications.
--
Best Regards,
Artem B. Bityutskiy,
St.-Petersburg, Russia.
prev parent reply other threads:[~2005-11-14 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 8:36 CRC error of jffs2_get_inode_nodes() for JFFS2 on NAND 陳羿逞 \(Chuck\)
2005-11-13 13:09 ` Artem B. Bityutskiy
2005-11-14 6:26 ` 陳羿逞 \(Chuck\)
2005-11-14 9:43 ` Artem B. Bityutskiy [this message]
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=43785C48.1010202@yandex.ru \
--to=dedekind@yandex.ru \
--cc=linux-mtd@lists.infradead.org \
--cc=ycchen@realtek.com.tw \
/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