From: Artem Bityutskiy <dedekind1@gmail.com>
To: Cliff Brake <cliff.brake@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 loss of power expectations
Date: Fri, 22 Apr 2011 10:36:21 +0300 [thread overview]
Message-ID: <1303457781.2757.26.camel@localhost> (raw)
In-Reply-To: <BANLkTi=b6XGamVPAfuQZJo=sRQy286xh0g@mail.gmail.com>
Hi,
On Fri, 2011-04-22 at 01:05 -0400, Cliff Brake wrote:
> I'm helping debug a system that is running the 2.6.27 kernel with
> JFFS2 (with summary) on SLC NAND. The CPU is a PXA270 (cm-x270), and
> appears to be using NAND_ECC_SOFT. We are experiencing some file
> system corruption if we lose power when the system is booting up.
> There is some amount of file system activity when udev and other
> system components start, but overall there is not much that is being
> written to the file system.
>
> A few questions:
>
> 1) should this combination be fairly robust to power failure (are
> failures expected, or possible)?
Probably, but you have to test this anyway.
1. Despite JFFS2 is considered old and robust - it is not maintained
very well for the last couple of years.
2. SLC NANDs in the past were more robust than modern SLCs and new
challenges like unstable bits may have changed the situation with JFFS2
robustness.
So - test it.
> 2) any suggestions for debugging this?
Some kind of device which may cut power is needed. Then you may write a
test program or script, cut power at random point, boot up, make sure
the FS look ok.
Or simply cut the power at random point between [0-N] seconds, then boot
up all the way to the end, check everything is ok, reboot, cut power,
etc.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-04-22 7:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 5:05 JFFS2 loss of power expectations Cliff Brake
2011-04-22 7:36 ` Artem Bityutskiy [this message]
2011-05-03 20:08 ` Cliff Brake
2011-05-03 22:03 ` Ivan Djelic
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=1303457781.2757.26.camel@localhost \
--to=dedekind1@gmail.com \
--cc=cliff.brake@gmail.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;
as well as URLs for NNTP newsgroup(s).