From: Justin Clacherty <justin@redfish-group.com>
To: Nils Faerber <nils.faerber@kernelconcepts.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Again 2.6.18-RC6 XScale P30 issues
Date: Sun, 10 Sep 2006 08:00:49 +1000 [thread overview]
Message-ID: <45033991.20900@redfish-group.com> (raw)
In-Reply-To: <4502B082.1090401@kernelconcepts.de>
Nils Faerber wrote:
> not the issue here. If it would be I would get the other "unable to
> write to locked sector" error.
>
Yes, you're probably right about that.
> Instead the fs gets permanently corrupted, i.e. data is written and the
> written data is wrong.
>
hmmm,,,didn't realise it was getting permanently corrupted.
> Last night I found that the JFFS2 write cache is configured. I will
> disable that now and see if that helps - I have the impression that the
> fs may contain half-baked stuff after a write. On the other hand, the
> JFFS2 write cache is not marked as an experimental feature so I thought
> I should be safe...
>
Can't speak from experience here as I don't have write cache enabled,
but I don't imagine you'd lose the whole fs if you were using write
cache and lost power. I suspect you'd just lose your changes or maybe
the file that was being updated.
Justin.
prev parent reply other threads:[~2006-09-09 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 15:27 Again 2.6.18-RC6 XScale P30 issues Nils Faerber
2006-09-09 11:16 ` Justin Clacherty
2006-09-09 12:16 ` Nils Faerber
2006-09-09 14:10 ` Josh Boyer
2006-09-09 22:00 ` Justin Clacherty [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=45033991.20900@redfish-group.com \
--to=justin@redfish-group.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nils.faerber@kernelconcepts.de \
/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