public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Vipin Malik <vmalik@danielind.com>
To: MTD <mtd@imladris.mvhi.com>
Subject: [Fwd: Power Down]
Date: Wed, 08 Dec 1999 15:32:05 -0600	[thread overview]
Message-ID: <384ECE55.83FAD600@danielind.com> (raw)

David Woodhouse wrote:
> 
> Orono@m-sys.com said:
> > The only way to be resistant to power failures in the file system
> > level  is to use a log-structured file system.
> 
> > I heard ext3 is log-structured but I am sure one of the Linux guys here
> > knows more about this,
> 
> ext3 is a journalling filesystem. I believe that it's not log-structured.

Is ext3 already available in beta form? Is it included in the latest
2.3.x kernels?


> 
> Journalling is sufficient for protection from power failures. Stephen,
> would you care to elaborate on the difference?

What is the overhead of Journalling? (CPU AND flash space). Of course if
that solves the problem, then that is the most important thing (for me
at least).

> 
> > Any other file system  that takes power failures into account, (I am afraid
> > to guess NFTL ????).
> 
> I believe that NTFS is also journalling but not log-structured.
> 
> > Some of our customers use their own home brewed LFSs and do it successfully.
> 
> Personally, I'm inclined to believe that we should run a filesystem directly
> on the flash device - rather than faking a block device and running a 'normal'
> filesystem on top of that.

I think that would probably be the best idea also, since in repairing
low level partitions vs a higher level f/s, could get really difficult
to prove that it is reliable.

The only problem with this approach is that it is not the usual "linux"
layered approach. But maybe that approach does not work well with
embedded systems and is a hit we are willing to accept?

Another problem with the usual "layered" approach is that the VFS uses a
lot of buffering in its layer. This is usually desirable for read/write
performance, however for logs etc. on FLASH this is probably NOT
desirable.

When I write a log, I want it written and saved. I guess one could do
sync() etc. every time but not very elegant.

> 
> I've been rushed off my feet here with other things for a while, but as soon as
> I get back to it, after I've fixed the NFTL and DiskOnChip Millennium support,
> that's what I'm intending to look at.

Do you have an estimate for the time frame that you are looking at?

I am willing to help out with coding, as I am extremely interested in
this (and
have access to lots of different embedded hardware with FLASH, SRAM etc.
on it, and if needed I could possibly buy more :).


> 
> If you're running ext2 on a DiskOnChip you should mount it with the noatime
> option if you can - this will eliminate a lot of write activity.
> 
> --
> dwmw2
> 
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

             reply	other threads:[~1999-12-08 21:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-08 21:32 Vipin Malik [this message]
1999-12-09 11:10 ` [Fwd: Power Down] David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
1999-12-08 21:39 Vipin Malik
1999-12-08 21:36 Vipin Malik
1999-12-08 23:02 ` Bob Canup
1999-12-09 11:02   ` David Woodhouse
1999-12-09 14:56   ` Bob Canup
1999-12-20  4:22     ` Stuart Lynne
1999-12-08 20:48 Vipin Malik
1999-12-08 20:42 Vipin Malik
1999-12-07 16:36 [Fwd: power down] Oron Ogdan
1999-12-06 23:41 Vipin Malik
1999-12-07 15:47 ` Bob Canup
1999-12-20  4:03   ` Stuart Lynne
1999-12-07 20:36 ` Jon Burford
1999-12-13 14:49   ` Adi Linden
1999-12-13 19:07     ` Jon Burford
1999-12-08 15:10 ` David Woodhouse

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=384ECE55.83FAD600@danielind.com \
    --to=vmalik@danielind.com \
    --cc=mtd@imladris.mvhi.com \
    /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