From: Ludovic Guilhamat <lguilhamat@perax.fr>
To: manningc2@actrix.gen.nz
Cc: linux-mtd@lists.infradead.org,
uClinux development list <uclinux-dev@uclinux.org>
Subject: Re: Samsung RFS Filesystem
Date: Wed, 01 Jun 2005 08:28:30 +0200 [thread overview]
Message-ID: <429D558E.5040706@perax.fr> (raw)
In-Reply-To: <20050601044012.1392D47AF@blood.actrix.co.nz>
Charles Manning a écrit :
>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
>
>
>
Thanks.
Actually, the system I work on uses Jffs2 (Coldfire with uClinux). But,
mount times are very long (the memory is a Flash Nand 16Mb). So, I
planned to test Jffs2 patches (from the Jffs2 Improvement Project), then
Yaffs. And as RFS is not freely distributed, and I don't know yet its
cost, I wanted to know if someone had tested it.
Thanks for your response.
Ludovic.
next prev parent reply other threads:[~2005-06-01 6:28 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
2005-06-01 6:28 ` Ludovic Guilhamat [this message]
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=429D558E.5040706@perax.fr \
--to=lguilhamat@perax.fr \
--cc=linux-mtd@lists.infradead.org \
--cc=manningc2@actrix.gen.nz \
--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