From: Peter Menzebach <pm-mtd@mw-itcon.de>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Do I have to umount JFFS2?
Date: Thu, 15 Dec 2005 13:51:18 +0100 [thread overview]
Message-ID: <43A166C6.5060803@mw-itcon.de> (raw)
In-Reply-To: <43A1609C.80705@imc-berlin.de>
Steven Scholz wrote:
> Jarkko Lavinen wrote:
>> On Thu, Dec 15, 2005 at 11:12:31AM +0100, ext Steven Scholz wrote:
>>
>>> Now I wonder if it is needed to umount this partition explicitly before
>>> rebooting? Or mount it read only first by having
>>
>> JFFS2 is synhronous except for the write buffer (used with Nand chips).
>> Doing sync is enough and flushes the write buffer.
>
> Is "sync()" done by the kernel before reboot? Or do I have to call "sync"?
>
Hi Steven,
afaik,
and this this is inline with my experience, you have call sync before
reboot.
Since I write only complete files to jffs2, I reduced the timer, which
flushes the write buffer automatically from 3 seconds to 500 ms.
In that case, I normally get no errors even in case of a hard reset.
Otherwise I get some "found empty flash at" and some CRC errors. The
filesystem as whole should remain in a stable state in any case (that's
the main reason apart from wear levelling for jffs2, I think)
Best regards
Peter
--
Peter Menzebach
Menzebach und Wolff IT-Consulting GbR
Phone +49 751 355 387 1
next prev parent reply other threads:[~2005-12-15 12:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 10:12 Do I have to umount JFFS2? Steven Scholz
2005-12-15 10:26 ` Jarkko Lavinen
2005-12-15 12:25 ` Steven Scholz
2005-12-15 12:51 ` Peter Menzebach [this message]
2005-12-16 2:16 ` alfred hitch
2005-12-16 9:10 ` Peter Menzebach
2005-12-16 16:36 ` alfred hitch
2005-12-16 16:54 ` Peter Menzebach
2005-12-18 15:08 ` Steven Scholz
2005-12-19 7:52 ` Peter Menzebach
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=43A166C6.5060803@mw-itcon.de \
--to=pm-mtd@mw-itcon.de \
--cc=linux-mtd@lists.infradead.org \
--cc=steven.scholz@imc-berlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.