public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Peter Menzebach <pm-mtd@mw-itcon.de>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: data  loss on jffs2 filesystem on dataflash
Date: Tue, 20 Sep 2005 18:11:03 +0400	[thread overview]
Message-ID: <43301877.3040306@yandex.ru> (raw)
In-Reply-To: <20050920133244.GC4634@wohnheim.fh-wedel.de>

Jörn Engel wrote:
> Still can't.  Block devices have the attribute that writing AAA... to
> a block containing BBB... gives you one of three possible results in
> case of power failure:
> 
> 1. BBB...BBB all written
> 2. AAA...AAA nothing written
> 3. AAA...BBB partially written.
> 
> Flash doesn't have 3, but two more cases:
> 4. FFF...FFF erased, nothing written
> 5. AAA...FFF erased, partially written
> 
> Plus the really obnoxious
> 6. FFF...FFF partially erased.  Looks fine but some bits may flip
>    randomly, writes may not stick, etc.
> 
> Now try finding a filesystem that is robust if 4-6 happens. ;)
Don't underastand this. If you mean the atomicity, CRC may help here. 
And no problems. Or may be you missed the the fact that we have 
eraseblock size = writeblock size?

>>JFFS2 orients to "classical" flashes. They have no "write page with 
>>built-in erase" operation.
> What does this thing do?
It erases individual page, then writes there. To put it differently, in 
your terminology, eraseblock size = writeblock size.

P.S. I actually missed the mailing list, this should have gone to the 
MTD ML. So let's move there please.

-- 
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.


  reply	other threads:[~2005-09-20 14:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <432812E8.2030807@mw-itcon.de>
     [not found] ` <432817FF.10307@yandex.ru>
     [not found]   ` <4329251C.7050102@mw-itcon.de>
     [not found]     ` <4329288B.8050909@yandex.ru>
     [not found]       ` <43292AC6.40809@mw-itcon.de>
     [not found]         ` <43292E16.70401@yandex.ru>
     [not found]           ` <43292F91.9010302@mw-itcon.de>
     [not found]             ` <432FE1EF.9000807@yandex.ru>
     [not found]               ` <432FEF55.5090700@mw-itcon.de>
2005-09-20 12:55                 ` data loss on jffs2 filesystem on dataflash Artem B. Bityutskiy
2005-09-20 13:32                   ` Jörn Engel
2005-09-20 14:11                     ` Artem B. Bityutskiy [this message]
2005-09-21 19:07                     ` Pavel Machek
2005-09-22 10:48                       ` Artem B. Bityutskiy
2005-09-22 16:46                         ` Valdis.Kletnieks
2005-09-22 17:03                           ` Artem B. Bityutskiy
2005-09-22 17:22                             ` linux-os (Dick Johnson)
2005-09-22 18:43                               ` jscottkasten
2005-09-23  8:51                           ` Jörn Engel
2005-09-22 11:34                       ` Jörn Engel
2005-09-22 11:54                         ` Jörn Engel

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=43301877.3040306@yandex.ru \
    --to=dedekind@yandex.ru \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pm-mtd@mw-itcon.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