| To: | zhuzhenhua <zzh.hust@gmail.com> |
|---|---|
| Subject: | Re: how to choose journal filesystem for embedded linux? |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Wed, 24 Jan 2007 14:02:52 +0000 |
| Cc: | linux-mips <linux-mips@linux-mips.org> |
| In-reply-to: | <50c9a2250701231805y62ec67f0v83d2fcf3ae2c55da@mail.gmail.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <50c9a2250701231805y62ec67f0v83d2fcf3ae2c55da@mail.gmail.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.2.2i |
On Wed, Jan 24, 2007 at 10:05:10AM +0800, zhuzhenhua wrote: > i now work on a mips board, and want to store my system code > on NAND Flash. > our Flash driver can handle the Flash features(bad block, phy to > logic addr, spare,etc.), > so i just want to select a journal filesystem to handle sudden poweroff. > Our system code(writeable) is about 10M~50M. i am not sure what > journal filesystem will be suitable, ext3,xfs,jfs,or reiserFS? > i have try ext3, it runs well, but seems to waste too much space > while mkfs.ext3. Classic journaling filesystems are not suitable for flash as they tend to have write hot spots so will wear out certain parts of the flash fairly quickly. Don't forget atime updates, even those do matter! Of course if your filesystem is read-only these constraints matter much less. Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] seq_file conversion: APM on mips, Alexey Dobriyan |
|---|---|
| Next by Date: | [PATCH 3/8] signal: clean up sigframe structure, Franck Bui-Huu |
| Previous by Thread: | Re: how to choose journal filesystem for embedded linux?, zhuzhenhua |
| Next by Thread: | [PATCH] Fix wrong checksum calculation on 64-bit MIPS, Atsushi Nemoto |
| Indexes: | [Date] [Thread] [Top] [All Lists] |