public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Peter Menzebach <pm-mtd@mw-itcon.de>
To: alfred hitch <alfred.hitch@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Do I have to umount JFFS2?
Date: Fri, 16 Dec 2005 17:54:50 +0100	[thread overview]
Message-ID: <43A2F15A.6070407@mw-itcon.de> (raw)
In-Reply-To: <29f916510512160836q21a0b585h9894990b0fc0d7f3@mail.gmail.com>

alfred hitch wrote:
> Hi Peter,
> 
> We happened to have our system in rw mode (dont ask me why,I will be
> embarassed).
> Now, we have made it ro.
> Files in question happened to be "sh"  or libc.so. etc.. basically one
> which appeared to be in memory at that time before kernel oops or
> sudden resets etc. So, to answer your question, yes they were from
> start there. After making ro as ofnow we havent seen any corruptions.
> But, my head has been looking for a reason as to why would it be
> executables be ever written back to flash ??
> 
I do not know exactly. But a question to the others: Does the wear 
leveling affect only free blocks, or does it reorganize seldom written 
used blocks too?

> Well jffs2 version we are using happened to be from snapgear 3.0 from
> net. so I am kinda biased and hoping we arent with a such a broken
> one.
> (How to update to latest btw ? 2.4 backwards compatible ?)
> 
> Didnt get this comment of ur's :
> 1. Single files can be still corrupted, when you write them and press reset.
> 
When you press reset, when a file is written, you get a partly written 
block. So you get a file, which is not written completely. This 
corruption is detected by jffs2 and issues warnings. The filesystem as 
whole stays intact, but the file as such doesn't have the contents you 
might expect.


Best regards
Peter

-- 
Peter Menzebach
Menzebach und Wolff IT-Consulting GbR
Phone +49 751 355 387 1

  reply	other threads:[~2005-12-16 16:54 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
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 [this message]
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=43A2F15A.6070407@mw-itcon.de \
    --to=pm-mtd@mw-itcon.de \
    --cc=alfred.hitch@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