From: Charles Manning <manningc2@actrix.gen.nz>
To: Ludovic Guilhamat <lguilhamat@perax.fr>,
uClinux development list <uclinux-dev@uclinux.org>,
linux-mtd@lists.infradead.org
Subject: Re: Samsung RFS Filesystem
Date: Wed, 1 Jun 2005 16:41:50 +1200 [thread overview]
Message-ID: <20050601044012.1392D47AF@blood.actrix.co.nz> (raw)
In-Reply-To: <429C4D96.7000302@perax.fr>
On Tuesday 31 May 2005 23:42, Ludovic Guilhamat wrote:
> Hi,
>
> I would maybe interested in testing the Samsung RFS File System...
>
> Does someone, here, already used it, and what are the conclusions ?
Please do do some testing. It would be good to see the results, positive or
negative.
I have not used it, but from a description I can draw some immediate
conclusions.
RFS = Robust FAT file system
>From the blurb at
http://www.samsung.com/Products/Semiconductor/Flash/TechnicalInfo/rfs.htm
this looks a bit like FATFS running on top of DOC. It might have some
transactioning which would make it look a bit more like Microsoft's TFAT.
Neither of these are a proven reliable system. DOC can still get FAT
corruptions if you don't umount before power loss (== potentially a
completely scrambled fs). TFAT is completely unprovedn and is slower and not
always robust (not robust with typical mount options). Perhaps RFS gets the
robustness right.
Running FAT on NAND costs some performance due to the FTL etc. To make a
journaling system on FAT, as RFS claims, costs even more performance.
IMHO: If you want robustnes on NAND use a log structured fs designed for
flash: YAFFS or JFFS2.
For completeness, I will state that I wrote YAFFS, but I don't think this
biases my answer.
-- CHarles
next prev parent reply other threads:[~2005-06-01 4:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 11:42 Samsung RFS Filesystem Ludovic Guilhamat
2005-06-01 4:41 ` Charles Manning [this message]
2005-06-01 6:28 ` Ludovic Guilhamat
2005-06-01 23:49 ` Charles Manning
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=20050601044012.1392D47AF@blood.actrix.co.nz \
--to=manningc2@actrix.gen.nz \
--cc=lguilhamat@perax.fr \
--cc=linux-mtd@lists.infradead.org \
--cc=uclinux-dev@uclinux.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