mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <mkp@mkp.net>
To: Bryan Andersen <bryan@bogonomicon.net>
Cc: Pavel Machek <pavel@ucw.cz>, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Compactflash cards dying?
Date: 03 Feb 2003 09:08:49 -0500	[thread overview]
Message-ID: <yq1isw1qwwe.fsf@austin.mkp.net> (raw)
In-Reply-To: <3E3E1643.2080807@bogonomicon.net>

>>>>> "Bryan" == Bryan Andersen <bryan@bogonomicon.net> writes:

Bryan> Use a file system that is designed for use on FLASH devices.
Bryan> In general FLASH devices are not very useable for systems that
Bryan> need to modify data on the disk often.

Just a heads up that flash (as in MTD) != Compact Flash.

For all practical purposes a Compact Flash is an IDE disk (Or a an IDE
controller with a disk behind it.  Depends how you wire it).

Internally, the Compact Flash does all the wear averaging that a flash
filesystem like jffs2 provides.  Transparently to the application.

All Linux sees is a linear stream of bytes.  Just like a disk.  And it
should be treated as such.


Bryan> You may wish to look at the virtual memory file system
Bryan> available in the kernel if you have enough RAM.  You would
Bryan> mount your CompactFlash device read only and have all updates
Bryan> go to the virtual memory filesystem. When you want to commit
Bryan> the changes, remount the CompactFlash read/write and save the
Bryan> changes then remount it read only.

tmpfs to the rescue!


Bryan> You would be surprised how fast a million writes can happen on
Bryan> a disk.

Yup.

You would also be surprised how long it takes to actually *perform* a
million writes on a slow piece of media like Compact Flash ;)

-- 
Martin K. Petersen	Wild Open Source, Inc.
mkp@wildopensource.com	http://www.wildopensource.com/

  reply	other threads:[~2003-02-03 13:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02 22:30 Pavel Machek
2003-02-02 23:57 ` Willy Tarreau
2003-02-03 12:53   ` Pavel Machek
2003-02-03  0:36 ` Daniel Egger
2003-02-03  2:04   ` Martin K. Petersen
2003-02-03  8:39     ` Jörn Engel
2003-02-03 13:58       ` Martin K. Petersen
2003-02-03  8:50   ` Miquel van Smoorenburg
2003-02-03  7:12 ` Bryan Andersen
2003-02-03 14:08   ` Martin K. Petersen [this message]
2003-02-03 14:10     ` Padraig
2003-02-03 14:30       ` John Bradford
2003-02-03 14:25     ` John Bradford
2003-02-03 21:18       ` Bryan Andersen
2003-02-04 20:59       ` Bill Davidsen
2003-02-04 21:07         ` John Bradford
2003-02-03  7:30 ` Andreas Jellinghaus
2003-02-03 12:54   ` Pavel Machek
2003-02-03 23:12     ` David Woodhouse
2003-02-04  3:39       ` H. Peter Anvin
2003-02-04 11:24       ` Pavel Machek
2003-02-04 11:30         ` David Woodhouse
2003-02-04 19:28           ` Pavel Machek
2003-02-03 23:56 ` Roger Larsson
2003-02-04  0:10   ` David Woodhouse
2003-02-04 23:28     ` Pavel Machek
2003-02-04  0:34   ` Andrew McGregor
2003-02-04 23:27   ` Pavel Machek

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=yq1isw1qwwe.fsf@austin.mkp.net \
    --to=mkp@mkp.net \
    --cc=bryan@bogonomicon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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

all inboxes | Powered by JetHome®