From: Willy Tarreau <w@1wt.eu>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Bart Van Assche <bart.vanassche@gmail.com>,
St?phane ANCELOT <sancelot@free.fr>,
Helge Hafting <helge.hafting@aitel.hist.no>,
Tomasz Chmielewski <mangoo@wpkg.org>,
LKML <linux-kernel@vger.kernel.org>,
YSadgat1@gcte.com, linux-os@analogic.com,
Alan <alan@lxorguk.ukuu.org.uk>,
Linux IDE <linux-ide@vger.kernel.org>,
Jeff Woods <jeff@jeffwoods.us>
Subject: Re: Compact Flash Question
Date: Thu, 8 May 2008 16:59:44 +0200 [thread overview]
Message-ID: <20080508145943.GT8474@1wt.eu> (raw)
In-Reply-To: <20080508142714.GD6957@csclub.uwaterloo.ca>
On Thu, May 08, 2008 at 10:27:14AM -0400, Lennart Sorensen wrote:
> On Wed, May 07, 2008 at 06:46:25PM +0200, Bart Van Assche wrote:
> > Silicon Systems CompactFlashes are the among the most reliable
> > CompactFlashes I have used in embedded devices. See also
> > http://www.siliconsystems.com/silicondrive/whitepapers/SSWP03-Endurance-R.pdf
> > for a whitepaper that explains their wear leveling and error
> > correction algorithms. Furthermore, Silicon Systems has a technology
> > called SiSMART that allows to monitor by how far the CompactFlash is
> > worn out, such that it can be monitored whether or not it is time to
> > replace the CompactFlash. (Note: I am not affiliated in any way to
> > Silicon Systems.)
>
> We too have switched to Silicon Systems and are very happy with them.
> And even industrial temperature versions are hardly expensive. They may
> cost more than you pay for a generic slow piece of junk at a retail
> store, but you are getting a better card.
Interestingly, we once got a bunch of those and had a lot of problems
with them. Typically unbootable systems. We finally noticed that there
was a real corruption problem, because 3 MD5s of the kernel in a row
returned 3 different values. Our provider assured us that he never heard
about that, and insisted that we try again on a new batch. We have had
no trouble since. I guess we really got a bad batch. At least it was
noticeable early in the deployment process (the worst ones being a few
days after installation). However, we never had any problem with PQI
industrial.
> Len Sorensen
Willy
next prev parent reply other threads:[~2008-05-08 15:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48215673.3060201@wpkg.org>
[not found] ` <e2e108260805070044v42f596bbj39c5b52b6f0a096@mail.gmail.com>
2008-05-07 7:54 ` Compact Flash Question Tomasz Chmielewski
2008-05-07 7:58 ` Bart Van Assche
2008-05-07 12:31 ` Helge Hafting
2008-05-07 15:01 ` Stéphane ANCELOT
2008-05-07 16:46 ` Bart Van Assche
2008-05-08 13:26 ` Mark Lord
2008-05-08 14:27 ` Lennart Sorensen
2008-05-08 14:59 ` Willy Tarreau [this message]
2008-05-07 7:27 Tomasz Chmielewski
-- strict thread matches above, loose matches on Subject: below --
2008-05-06 21:59 Yigal Sadgat
2008-05-06 22:09 ` Alan Cox
2008-05-13 17:13 ` Yigal Sadgat
2008-05-06 22:22 ` linux-os (Dick Johnson)
2008-05-07 6:15 ` Bart Van Assche
2008-05-07 7:39 ` Alan Cox
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=20080508145943.GT8474@1wt.eu \
--to=w@1wt.eu \
--cc=YSadgat1@gcte.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bart.vanassche@gmail.com \
--cc=helge.hafting@aitel.hist.no \
--cc=jeff@jeffwoods.us \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=mangoo@wpkg.org \
--cc=sancelot@free.fr \
/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;
as well as URLs for NNTP newsgroup(s).