From: Ed W <lists@wildgooses.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] quickpkg and PKG_INSTALL_MASK
Date: Fri, 27 Jan 2012 18:27:45 +0000 [thread overview]
Message-ID: <4F22ECA1.7010002@wildgooses.com> (raw)
In-Reply-To: <20120126145920.20149.qmail@stuge.se>
[-- Attachment #1: Type: text/plain, Size: 2140 bytes --]
On 26/01/2012 14:59, Peter Stuge wrote:
>> I do have the impression that any block emulating device such as
>> SSD are unreliable w.r.t power cuts. I would love to be proven
>> wrong though :)
> Supposedly, Intel SSDs never report write completed before flash has
> actually been updated. Good luck verifying that.
>
> Everyone else buffers writes. The Samsung 830 series has 256MB of
> SDRAM, and their multicore ARM controller handles the magic
> buffering. Samsung 830 is built entirely by Samsung from Samsung
> parts. All manufacturers besides Intel and Samsung use a mishmash
> of components and firmware in their SSD products, and all do magic
> buffering.
I can't find a reference right now, but I am under the impression that
the more expensive "enterprise" SSD modules now have some battery backup
onboard to allow writes to complete in sudden power down situations? I
read recently of one consumer report (probably on Anand tech, but can't
find it now...) which had also been fitted with some kind of supercap to
handle unexpected powerloss
(Update, google "SSD supercap" - seems like some of the higher end
Sandforce boards have such a thing, and on skimming it is implied that
the Vertex3 might have such a thing?)
I also found this paper which seemed interesting:
http://cseweb.ucsd.edu/users/swanson/papers/DAC2011PowerCut.pdf
Seems like it's a rocky road ahead...
Cheers
Ed W
P.S. I think this phenomena explains what surely everyone here has
experienced, that if you rip out a USB flash drive while it's still
writing then every so often the whole drive just disappears (and stays
dead)? Also I have killed one CF almost certainly due to a sudden
reboot (but it was the design that has since been recalled by
PCEngines), and a few others that on reflection might have had a sudden
powerdown in a camera or while removing pictures from the camera flash
card... Read random amazon reviews of flash drives and there are always
a bunch of people who post when their drive totally fails while it's new
- again my bet would be many of these would be explained by sudden
unplugs during write...
[-- Attachment #2: Type: text/html, Size: 2908 bytes --]
prev parent reply other threads:[~2012-01-27 19:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 13:23 [gentoo-embedded] quickpkg and PKG_INSTALL_MASK Joakim Tjernlund
2011-12-25 9:34 ` Kfir Lavi
2011-12-25 17:52 ` solar
2011-12-26 18:03 ` Joakim Tjernlund
2011-12-26 20:38 ` solar
2011-12-27 9:40 ` Joakim Tjernlund
2011-12-27 11:44 ` Kfir Lavi
2011-12-29 9:48 ` Joakim Tjernlund
2012-01-23 18:43 ` Ed W
2012-01-24 7:52 ` Joakim Tjernlund
2012-01-24 14:06 ` Todd Goodman
2012-01-25 13:21 ` Ed W
2012-01-26 11:11 ` Joakim Tjernlund
2012-01-26 13:30 ` Todd Goodman
2012-01-27 18:15 ` Ed W
2012-01-26 14:59 ` Peter Stuge
2012-01-27 18:27 ` Ed W [this message]
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=4F22ECA1.7010002@wildgooses.com \
--to=lists@wildgooses.com \
--cc=gentoo-embedded@lists.gentoo.org \
/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