All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Compactflash cards dying?
Date: Wed, 5 Feb 2003 00:28:33 +0100	[thread overview]
Message-ID: <20030204232833.GE128@elf.ucw.cz> (raw)
In-Reply-To: <1044317447.27957.63.camel@imladris.demon.co.uk>

Hi!

> > > I had compactflash from Apacer (256MB), and it started corrupting data
> > > in few months, eventually becoming useless and being given back for
> > > repair. They gave me another one and it is just starting to corrupt
> > > data.
> > 
> > That is very bad... I wonder if you do something that the CF does
> > not like - like power off while writing (can actually destroy the
> > disk - read in some newsgroup)
> 
> I am led to believe that this is normal for CompactFlash. I seem to
> recall that the phrase 'bogroll technology' was used by the last person
> to attempt any serious testing.
> 
> It's fine for short-term storage of stuff like digital photos, but don't
> try using it for long-term storage. Think of it like a floppy disc -- if
> you have any _important_ data, make sure it's backed up or copied onto
> at least three of them to avoid loss.

Well, this seems *way* more crappier than floppies. Floppies will not
fail within five minutes if you only start using them :-(.
								Pavel
-- 
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?

  reply	other threads:[~2003-02-05 13:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02 22:30 Compactflash cards dying? 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
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 [this message]
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=20030204232833.GE128@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roger.larsson@skelleftea.mail.telia.com \
    /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.