From: Kyle Harris <kharris@nexus-tech.net>
To: Vipin Malik <vipin.malik@daniel.com>,
MTD for Linux <linux-mtd@lists.infradead.org>
Subject: Re: safe flash filesystem
Date: Thu, 21 Jun 2001 17:17:17 -0400 [thread overview]
Message-ID: <3B32645D.BF65C965@nexus-tech.net> (raw)
In-Reply-To: 3B325156.271EE3C4@daniel.com
Hey,
I've read thru several posts and Vipin's jffs_guide. It appears that
JFFS, at his time, is about the most reliable open source fs for
embedded systems, even though it still has some problems. When JFFS
fails, is the filesystem still usable? My question is this. What if you
save only a small datafile (< 1K) and write it alternately to 2
different JFFS partitions (or even the same partition). At boot, you
read from both and get the latest, valid copy. This way if one is bad
you still have a backup. How reliable would this be?
Just wondering... Kyle.
Vipin Malik wrote:
>
> Tim Riker wrote:
>
> > ok,
> >
> > what about reiserfs on CF then?
> >
>
> I have tested one *major* brand of IDE flash devices and 2 brands of CF
> devices, in more than 20K power fail tests.
>
> Both suffer from low level failures, which cause the IDE driver layer to "give
> up" with
> "unrecoverable errors". The CF is so bad that I just gve up on the testing
> after a few hundred cycles.
>
> The IDE flash was better, but not much.
>
> Will raiserfs be happy if the underlying IDE /dev/hdxx driver returns
> "unrecoverable error" from the IDE device?
>
> Your call.
>
> Vipin
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2001-06-21 21:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 10:54 safe flash filesystem Abraham vd Merwe
2001-06-21 13:43 ` Vipin Malik
2001-06-21 13:57 ` Abraham vd Merwe
2001-06-21 14:29 ` Vipin Malik
2001-06-21 14:35 ` Abraham vd Merwe
2001-06-21 15:05 ` Vipin Malik
2001-06-21 15:36 ` Chris Read
2001-06-21 15:09 ` Joakim Tjernlund
2001-06-21 15:34 ` Vipin Malik
2001-06-21 19:34 ` Joakim Tjernlund
2001-06-21 19:47 ` Joakim Tjernlund
2001-06-21 15:11 ` Herman Oosthuysen
2001-06-21 17:54 ` Tim Riker
2001-06-21 19:43 ` Vipin Malik
2001-06-21 19:35 ` Tim Riker
2001-06-21 19:56 ` Vipin Malik
2001-06-21 21:17 ` Kyle Harris [this message]
2001-07-03 23:53 ` On the "safe filesystem" and write() topic Bjorn Wesen
2001-07-04 14:10 ` Vipin Malik
2001-07-05 18:16 ` Bjorn Wesen
2001-07-06 13:40 ` Vipin Malik
2001-07-07 9:25 ` Bjorn Wesen
2001-07-07 13:06 ` Vipin Malik
2001-06-21 21:26 ` safe flash filesystem Russ Dill
2001-06-22 8:22 ` Abraham vd Merwe
[not found] ` <20010622102154.E1828@crystal.2d3d.co.za>
2001-06-22 17:23 ` Russ Dill
2001-06-25 7:45 ` Abraham vd Merwe
2001-06-25 7:59 ` Russ Dill
2001-06-25 14:11 ` Vipin Malik
-- strict thread matches above, loose matches on Subject: below --
2001-06-21 16:05 Vipin Malik
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=3B32645D.BF65C965@nexus-tech.net \
--to=kharris@nexus-tech.net \
--cc=linux-mtd@lists.infradead.org \
--cc=vipin.malik@daniel.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