From: Tomasz Chmielewski <mangoo@wpkg.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: maxdamage@aladin.ro
Subject: Re: ext2 on flash memory
Date: Mon, 11 Jun 2007 13:53:00 +0200 [thread overview]
Message-ID: <466D379C.6000809@wpkg.org> (raw)
Eduard-Gabriel Munteanu wrote:
(...)
> Your USB pendrive will wear faster if you use an inappropriate
> filesystem. Such filesystems require frequent writes and change their
> internal state often.
>
> This could be alleviated by COWing the filesystem somehow and flushing
> writes when you're finished. But the modifications will be lost if
> crashes occur. The filesystem structures will still change a lot and
> require big writes to update it.
>
> Really, why don't you try a more suitable fs for your pendrive, one that
> changes itself less than usual fs's?
Hmm, are there any fs (read+write) alternatives for pendrives?
jffs2 only works on mtd devices, and that excludes pendrives, which are
block devices. I know LogFS will work with block devices one day, but
currently, it doesn't (and is not in the kernel yet as well).
Also, ext2 provides a nice feature other filesystems lack: xip.
Especially, if a pendrive is used as a rootfs for a small device.
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2007-06-11 11:53 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 11:53 Tomasz Chmielewski [this message]
2007-06-12 0:17 ` ext2 on flash memory Arnd Bergmann
2007-06-14 16:38 ` Jörn Engel
2007-06-14 17:19 ` Tomasz Chmielewski
2007-06-14 17:46 ` Jörn Engel
2007-06-14 22:46 ` DervishD
2007-06-15 12:08 ` Jörn Engel
2007-06-15 16:22 ` DervishD
2007-06-15 16:22 ` Jörn Engel
2007-06-18 11:31 ` DervishD
-- strict thread matches above, loose matches on Subject: below --
2007-06-14 21:40 Tomasz Chmielewski
2007-06-11 10:13 DervishD
2007-06-11 11:11 ` Eduard-Gabriel Munteanu
2007-06-11 17:36 ` DervishD
2007-06-13 13:16 ` Ph. Marek
2007-06-13 23:02 ` DervishD
2007-06-14 5:16 ` Ph. Marek
2007-06-11 14:58 ` alan
2007-06-11 17:42 ` DervishD
2007-06-11 19:27 ` Juergen Beisert
2007-06-13 13:48 ` DervishD
2007-06-14 19:36 ` Jan Knutar
2007-06-14 20:07 ` DervishD
2007-06-11 23:53 ` Kevin K
2007-06-12 0:35 ` Kevin Bowling
2007-06-12 1:18 ` Bernd Eckenfels
2007-06-13 13:44 ` DervishD
2007-06-12 7:53 ` Juergen Beisert
2007-06-12 13:29 ` Eduard-Gabriel Munteanu
2007-06-12 16:46 ` Eduard-Gabriel Munteanu
2007-06-13 13:43 ` DervishD
2007-06-12 21:09 ` Jason Lunz
2007-06-13 6:49 ` Juergen Beisert
2007-06-14 17:45 ` Jörn Engel
2007-06-14 18:22 ` Jörn Engel
2007-06-14 20:20 ` DervishD
2007-06-14 20:43 ` Jörn Engel
2007-06-15 16:20 ` DervishD
2007-06-15 16:27 ` Jörn Engel
2007-06-14 20:17 ` DervishD
2007-06-14 20:38 ` Jörn Engel
2007-06-15 16:16 ` DervishD
2007-06-15 16:36 ` Jörn Engel
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=466D379C.6000809@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxdamage@aladin.ro \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.