public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Andre <andre@rocklandocean.com>
To: linux-mtd@lists.infradead.org
Subject: Re: suggestion on use of linux-mtd
Date: Tue, 14 Jun 2005 17:01:25 +0000 (UTC)	[thread overview]
Message-ID: <loom.20050614T185630-101@post.gmane.org> (raw)
In-Reply-To: loom.20050614T135901-706@post.gmane.org

Sergei Sharonov <sergei.sharonov <at> halliburton.com> writes:

> You may forget about jffs2 on such large flashes. Depending on the size of the
> writes that filled the disk it will take anywhere from ten minutes to hours
> to mount jffs2. The only other alternative that uses mtd is yaffs. It does
> mount significantly faster, but the user base is small and there is no active
> development going on (as far as I can tell).

ok, I will not pursue jffs2.

> > What exactly does one get with *just* NFTL, i.e. does it makes sense to run
> > ext3 on top of NFTL? Is NFTL production ready?
> 
> Are you going to power cycle your nftl+ext3 setup? I would be
> interested in results.

Yes, as soon as I find out the state of NFTL. I got a little scared by the 
following comment in the howto:

quote: "DO NOT EVER USE THE nftl_format UTILITY WITHOUT FIRST SEEKING ADVICE
ON THE MAILING LIST. It will erase all blocks on the device,
potentially losing the factory-programmed information about bad
blocks. (Someone really ought to fix it one of these days - ed)"

Does NFTL include wear leveling and/or bad block remapping?

      parent reply	other threads:[~2005-06-14 17:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14  0:04 suggestion on use of linux-mtd Andre
2005-06-14  0:47 ` Coywolf Qi Hunt
2005-06-14  6:00 ` Raphael Zimmerer
2005-06-14 12:25 ` Sergei Sharonov
2005-06-14 12:48   ` Artem B. Bityuckiy
2005-06-14 17:01   ` Andre [this message]

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=loom.20050614T185630-101@post.gmane.org \
    --to=andre@rocklandocean.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