linux-kernel - Re: Compact Flash Question

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 8 May 2008 16:59:44 +0200
From:	Willy Tarreau <w@....eu>
To:	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>
Cc:	Bart Van Assche <bart.vanassche@...il.com>,
	St?phane ANCELOT <sancelot@...e.fr>,
	Helge Hafting <helge.hafting@...el.hist.no>,
	Tomasz Chmielewski <mangoo@...g.org>,
	LKML <linux-kernel@...r.kernel.org>, YSadgat1@...e.com,
	linux-os@...logic.com, Alan <alan@...rguk.ukuu.org.uk>,
	Linux IDE <linux-ide@...r.kernel.org>,
	Jeff Woods <jeff@...fwoods.us>
Subject: Re: Compact Flash Question

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/