public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Sergei Sharonov <sergei.sharonov@halliburton.com>
To: linux-mtd@lists.infradead.org
Subject: Re: mounting jffs2
Date: Wed, 20 Apr 2005 16:34:01 +0000 (UTC)	[thread overview]
Message-ID: <loom.20050420T180411-538@post.gmane.org> (raw)
In-Reply-To: 1114010417.32582.30.camel@sauron.oktetlabs.ru

Hi,
> On Wed, 2005-04-20 at 14:59 +0000, Sergei Sharonov wrote:
> > Hmm.. then what improvement does summary patch provide? In my case mount
> > returns in 1.5 minutes but then I cannot do anything to flash for
> > another 20+ minutes.
> Poor poor you 

More like stuck ;-)
I believe I got the hardware and the OS right - the only trouble is
a filesystem. I cannot believe that I am the only one who runs linux
with large FLASH and requires power-fail safe operation. So far I
checked into:
1. JFFS2 - seems stable, good support, mainstream, but long mount time
makes it unusable with large NAND FLASH.
2. YAFFS2 - still playing with it. Has a lot of promise but is not
IMHO a stable/usable product at this point of time.
3. Reliance/FlashFX Pro - a commercial product that promises to do
what I need but is not yet available for linux. I was told end of Q2,
early Q3.
4. Samsung RFS - there were a few announcements last summer. They never
answered my email though.
5. Stuff like TargetFFS, etc. that has not been ported (and no
intention?) to linux.
6. JFFS3 - still in design stage.
7. M-Systems software - AFAIK I cannot use it with raw NAND FLASH.

If anybody knows of a solution, please post.


> Summary should accelerate mounting but leave the other characteristics 
> inact in theory.

What exactly can I do after mount returns: ls is blocked, write is blocked..

Sergei Sharonov 
 

  reply	other threads:[~2005-04-20 16:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13 13:25 mounting jffs2 Sergei Sharonov
2005-04-13 13:50 ` Artem B. Bityuckiy
2005-04-13 14:22   ` Sergei Sharonov
2005-04-13 15:02     ` Artem B. Bityuckiy
2005-04-13 17:51       ` Sergei Sharonov
2005-04-14  8:41         ` Artem B. Bityuckiy
2005-04-14 12:39           ` Sergei Sharonov
2005-04-14 13:11             ` Artem B. Bityuckiy
2005-04-14 14:15               ` Sergei Sharonov
2005-04-14 15:18                 ` Artem B. Bityuckiy
2005-04-13 15:18     ` Artem B. Bityuckiy
2005-04-14 20:39   ` Sergei Sharonov
2005-04-14  9:01 ` Ferenc Havasi
2005-04-14  9:15   ` Artem B. Bityuckiy
2005-04-20 14:59     ` Sergei Sharonov
2005-04-20 15:20       ` Artem B. Bityuckiy
2005-04-20 16:34         ` Sergei Sharonov [this message]
2005-04-21  7:48       ` Artem B. Bityuckiy
2005-04-21 14:30       ` Ferenc Havasi
2005-04-21 15:31         ` Artem B. Bityuckiy
2005-04-26 13:35           ` Zoltan Sogor
2005-04-26 13:51             ` Artem B. Bityuckiy
2005-04-27  9:39               ` Zoltan Sogor
2005-04-21 15:34         ` Sergei Sharonov

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.20050420T180411-538@post.gmane.org \
    --to=sergei.sharonov@halliburton.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