mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Pavel Machek <pavel@suse.cz>
Cc: Chris Snook <csnook@redhat.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	linux-kernel@vger.kernel.org
Subject: Re: Filesystem for block devices using flash storage?
Date: Tue, 14 Oct 2008 14:04:48 -0400	[thread overview]
Message-ID: <20081014180448.GC22851@csclub.uwaterloo.ca> (raw)
In-Reply-To: <20081011143552.GA1556@ucw.cz>

On Sat, Oct 11, 2008 at 04:35:52PM +0200, Pavel Machek wrote:
> I don't think ext3 is safe w.r.t. whole eraseblocks disappearing. So
> if you write data 'nearby' root directory and power fails, bye bye
> filesystem, and journal will not help.
> 
> Actually ext2 will at least detect damage...

I have never seen a flash device that worked that way.  All the ones I
have seen have extra spare blocks and will copy an existing block to an
empty block changing the required bits while doing the copy to represent
the new data to be written.  When done, they update the block map of the
device to point to the new block, then the old block is erase and added
to the spare block list.

This is also used as part of wear leveling, where better devices will
occationally take a rarely written block, move it to a more used spare
block, and then add the previously rarely used block to the spare list
for more use.

In cases of decent devices like this, ext3 works great.  I have never
had a chunk of the filesystem disappear yet, although perhaps 2000
compact flash using units isn't a large enough data set to say much.

-- 
Len Sorensen

  parent reply	other threads:[~2008-10-14 18:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08 16:38 Stefan Monnier
2008-10-08 20:51 ` Chris Snook
2008-10-11 14:35   ` Pavel Machek
2008-10-11 16:29     ` Arjan van de Ven
2008-10-11 17:51     ` Alan Cox
2008-10-12 13:01     ` Jörn Engel
2008-10-13 10:57       ` Pavel Machek
2008-10-13 12:10         ` Jörn Engel
2008-10-14 18:04     ` Lennart Sorensen [this message]
2008-10-12 14:35   ` Jörn Engel
2008-10-13 17:30     ` Chris Snook
2008-10-13 18:13       ` Jörn Engel
2008-10-13 18:38         ` Chris Snook
2008-10-14 11:18 ` Jörn Engel
2008-10-14 13:05   ` Stefan Monnier

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=20081014180448.GC22851@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=csnook@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=pavel@suse.cz \
    /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

all inboxes | Powered by JetHome®