Slashdot Mirror


Enterprise SSDs, Powered Off, Potentially Lose Data In a Week

New submitter Mal-2 writes with a selection from IB Times of special interest for anyone replacing hard disks with solid state drives: The standards body for the microelectronics industry has found that Solid State Drives (SSD) can start to lose their data and become corrupted if they are left without power for as little as a week. ... According to a recent presentation (PDF) by Seagate's Alvin Cox, who is also chairman of the Joint Electron Device Engineering Council (JEDEC), the period of time that data will be retained on an SSD is halved for every 5 degrees Celsius (9 degrees Fahrenheit) rise in temperature in the area where the SSD is stored. If you have switched to SSD for either personal or business use, do you follow the recommendation here that spinning-disk media be used as backup as well?

35 of 184 comments (clear)

  1. I call BS by Anonymous Coward · · Score: 3, Insightful

    If the contents are lost in a week, we're probably talking about capacitor-backed SSDs that use some other technology than flash memory. Yes, it would be insane to use flash memory for archival purposes as well, but it still should easily retain its contents for at least a decade. When powered on, this problem does not exist as normally the controller slowly walks through the flash refreshing it.

    1. Re:I call BS by luther349 · · Score: 2, Insightful

      probably and no data center is going to not have power for a week and always have non flash based memory backups even if they did.

    2. Re:I call BS by gweihir · · Score: 5, Informative

      The statements are actually completely accurate, but a bit misleading. First, this is about what JEDEC requires, not what actual SSDs deliver. Second, this is when SSDs are stored in idle at 55C. And third the JEDEC requirements for minimum off-time data-retention are only 3 months @40C for enterprise-grade SSDs and only 12 months for consumer SSDs at 30C. These are kind of on the low side, although I have lost some OCZ drives that were off for just about a year. (Never buying their trash again...)

      That said, anybody conversant with SSD technology knows that SSDs are unsuitable for offline data storage as data obviously has potentially far shorter lifetimes than on magnetic disks, which in turn again have far shorter data lifetime than archival-grade tape. These is absolutely no surprise here for anybody that bothered to find out what the facts are. Of course, there are always those that expect every storage tech to keep data forever, and those dumb enough to have no or unverified backups and those often on media not suitable for long-term storage. Ignoring reality comes at a price.

      My personal solution is mixed HDD/SSD Raid1 and, of course, regular backups.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    3. Re:I call BS by Spazmania · · Score: 4, Informative

      Every write, not every read. Reads are satisfied as soon as either drive returns the data. And if the raid controller has a battery or supercap so it can cache writes, you'll almost never notice the difference.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    4. Re:I call BS by DarkTempes · · Score: 5, Informative

      I might be wrong but isn't it also when the SSD is stored at 55C AFTER having been stress tested at 55C to their endurance rating in terabytes written (page 39) under a given workload?
      And even then the cherry picked value was in example data submitted by Intel for unknown hardware and very likely extrapolated and quite possibly meaningless because it wasn't part of the chart targeted for the standard.

      The article seems to have totally misrepresented the presentation's purpose: which is to lay out endurance testing methodology/standards.

      The only important values were on page 26 where they set the minimum requirements of 40C 8hr/day load/30C 1 year retention for consumer (with a higher error ratio) and 55C 24hr/day load/40C 3 months retention for enterprise (with a lower error ratio.)
      And it looks like they haven't actually worked out the consumer workload for testing yet.

    5. Re:I call BS by dfghjk · · Score: 2

      "Reads are satisfied as soon as either drive returns the data. And if the raid controller has a battery or supercap so it can cache writes, you'll almost never notice the difference."

      RAID controllers do not launch reads on all involved drives. That would be stupid.

      Implementing battery backed write back cache on an array that uses SSD would be similarly stupid.

      RAID 1 with mixed SSD/HDD is the worst of both worlds further complicated by people who don't understand it.

    6. Re:I call BS by drsmithy · · Score: 2

      RAID controllers do not launch reads on all involved drives. That would be stupid.

      ?

      For a RAID1, most RAID controllers (and software RAID implementations) will absolutely read from all devices so as to service the read ASAP.

      For distributed parity forms of RAID, you inherently have to read from all devices.

      For dedicated parity disk forms of RAID, you have to read from all devices except the parity device.

      I've never tried a mixed RAID1 of SSD and magnetic disk, but with a large enough write cache the theory seems reasonable. Most controllers [with a BBU] acknowledge the write as soon as it hits cache.

    7. Re: I call BS by thogard · · Score: 2

      I've been thinking about getting a bunch of cheap usb sticks and building a zfs pool out of them with some redundancy and then using that for a zfs pool for a usenet spool just to see what can go wrong. If anything can abuse a disk its usenet.

    8. Re:I call BS by SharpFang · · Score: 2

      Cherry-picked for "a week" yes, but still disturbing. It's not an issue for datacenters, but for offices.

      Imagine an office PC set next to the radiator - oh, the employees are free to set up their desks as they like, and they really don't care about stuff like that. Given employee going for a holiday break for a month, taking the family for a skiing trip. The PC experiencing 50C on regular basis. That's quite enough to cause the data loss.

      Yes, in a responsible company there will be backups - or the data will be held on network drives. Visit your average office and see if they use these responsible practices; roughly half don't. Yes, once that occurs any admin who isn't a total idiot will spot the reason for the problem and recommend moving the PC away from the radiator. Still, the problem is not an impossible one - just needing a bad set of circumstances; iterate over enough PCs and offices and it *will* happen.

      --
      45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
    9. Re: I call BS by hr+raattgift · · Score: 2

      I've done this, experimentally, using not-super-cheap 128GiB patriot and hyper-x usb3 sticks.

      For a USENET load, performance will depend on whether your incoming feed is predominantly batched, streaming, or effectively random -- small writes bother these devices individually, and aggregating them into a pool works best if you can maximize write size. One way to do that is to use a wide stripe (e.g. zpool create foo raidz stick0 stick1 stick2 stick3 stick4 ...), which works well if your load is mainly batched or streaming, such that there is lots of stuff for zfs's various write aggregation strategies to cut down on the number of small writes.

      You'll also want a reasonably large ashift, for similar reasons.

      If your workload is mostly reading (e.g. you have lots of downstream feeds, especially synchronous or synchronously-batched ones, or many client readers), then a sufficiently large ARC should make your choice of pool layout somewhat less important. If you are VERY read-dominant, you'll likely want to take the hit on write performance and use n-way mirroring vdevs. (e.g. zpool create foo mirror stick0 stick1 mirror stick2 stick3 ...).

      If you're loss-intolerant, raidzN where N>1, or 3+-way mirroring.

      What can go wrong? Mostly that you'll run out of space. :-) For that reason, a mirroring strategy, even though it's space-intensive and slows down writes, provides useful flexibility, as you can always widen or narrow mirror vdevs, or add more mirror vdevs to a pool, and it's easier to swap out vdevs in a mirror with something else than it is to swap out vdevs in a wider individual vdev (a wide raidz stripe for instance). (But you can't remove mirror vdevs (or raidzN vdevs) from a pool...).

      Device names are likely be important considerations. Make sure the pool devices use device names that persist across reboots, USB3 hub failures, physical or logical disconnects and reconnects, and so forth. How to do that depends on the specific zfs port and operating system.

      What can go right? Negligible seek times! That makes *all* the difference compared to spinny disks. Even for super-cheap USB 3 sticks. Really.

      Final thing: no zfs port (none of the openzfs ones, and not opensolaris either) is good with USB 2 in general, and USB 2 sticks are often flaky. Avoid them.

    10. Re:I call BS by Spazmania · · Score: 2

      Implementing battery backed write back cache on an array that uses SSD would be similarly stupid.

      How do you figure? Write to ram is a whole lot faster than write to flash, especially if the flash block has to erase first.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    11. Re:I call BS by EndlessNameless · · Score: 2

      For a RAID1, most RAID controllers (and software RAID implementations) will absolutely read from all devices so as to service the read ASAP.

      For distributed parity forms of RAID, you inherently have to read from all devices.

      The problem is guaranteed with distributed parity raid; the controller will have to wait for the slowest disk to complete the read. Both reads and writes will be limited to mechanical disk performance levels.

      With a RAID1 mirror set, you can get a performance improvement on reads since the SSD would presumably service all of them. Writes will still be delayed by the mechanical drive(s).

      In addition, most RAID controllers do not support mixing drive types. Most of them don't even recommend mixing drive speeds (e.g., don't even mix 10K and 15K RPM drives). So you are proposing a whole new product essentially, and the expected gains are quite minimal.

      Rather than investing in new tech with questionable benefits, implement an existing solution. You can choose to setup a hot sync, cold sync, or backup device for a standard SSD array that is well-tested and performant.

      --

      ---
      According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
    12. Re:I call BS by unrtst · · Score: 2

      RAID controllers do not launch reads on all involved drives. That would be stupid.

      I think you mean that they do not launch a read request for the same chunk of data on all drives in a raid mirror. That would be accurate. However, they usually will read from both drives (read chunk 1 from drive A, read chunk 2 from drive B... doing so in parrallel can significantly increase read performance using a mirror).

      RAID 1 with mixed SSD/HDD is the worst of both worlds further complicated by people who don't understand it.

      Do you mean people like you?
      Look up "md raid write-mostly", or try this page (one of many found): http://tansi.info/hybrid/
      That setup is for a linux software RAID 1 mirror with one side being SSD and one side being HDD. The HDD has "writemostly" set. This causes the kernel to only do (slow) reads from the HDD if they are really needed, with all other reads going to the SSD.
      This is a very very simple setup that can easily give one a huge read performance boost with very safe HDD mirror backing the data. For much higher performance and tons of other data integrity options, see advanced ZFS setups (ex. with a dedicated SSD for the zil, another for L2ARC (a level 2 cache), and also in various hybrid style allocations for the pools).

  2. Re:How powered off is "powered off"? by TheRaven64 · · Score: 5, Informative

    Data loss in flash cells is probabilisitic, but the standard for wear levelling software is to mark a cell as dead if it can't guarantee holding its contents for a year. There have been some interesting proposals to expose this to the OS - there's a lot of data where even holding it for one day would be fine (e.g. browser caches, swap, other temporary files), so the more worn cells could be productively used for this data.

    --
    I am TheRaven on Soylent News
  3. no problem by Black+Parrot · · Score: 5, Funny

    Scotty will have the power back just in time.

    --
    Sheesh, evil *and* a jerk. -- Jade
    1. Re:no problem by Paradise+Pete · · Score: 2

      Scotty will have the power back just in time.

      But first he'll tell you it's impossible.

    2. Re: no problem by Buck+Feta · · Score: 2

      Oh shit I'm wearing a red shirt today

      --
      I am Audience.
  4. What it really says... by dshk · · Score: 5, Interesting

    The relevant table is on 27. page.

    In short: if you use the SSD in a cold environment AND store it in hot environment than you may lose data quite quickly. Quicker than two weeks.

    Client drives are also affected, but the data loss occurs slighly later. I guess reason of the difference is that enerprise drives assume a higher work temperature.

    So the advice is that if you use the SSD in your air conditioned basement in a good case then do not store your SSD on the sun for extended periods.

    And no, I do not use spinning media as a backup. I use tapes. Using spinning media for proper backups is almost impossible. See http://www.taobackup.com/

    1. Re:What it really says... by squiggleslash · · Score: 5, Interesting

      Interesting, because that could affect quite a few businesses in Florida.

      1. Business switches to SSDs. Uses them in a 75 degree air conditioned environment.
      2. Hurricane.
      3. Business unable to get power for a week. Computers down. No power to SSDs. No power for air conditioning. Temperature in office rises to over 100 degrees during the day.

      That's a very likely scenario, especially for smaller businesses (but not small) that wouldn't be organized enough to have back-up power or work from home capabilities.

      --
      You are not alone. This is not normal. None of this is normal.
  5. Re:How powered off is "powered off"? by jellomizer · · Score: 2, Interesting

    When ever something is "Enterprise" class it means it is vastly inferior to other solutions on the market but cost 3x as much.
    For some reason this isn't a buzzword that sends shivers down every IT workers spine yet.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  6. Re:How powered off is "powered off"? by dshk · · Score: 4, Interesting

    You may be right in case of other equipment, but enterprise grade drives are really better. For example I do not know any consumer SSD which has power loss capacitors (Intel 320 is not produced anymore). Most consumer drives don't contain even those capacitors which would be necessary to prevent the loss of - not the freshly written but the - old(!) data in case of a power loss. Consumer HDDs lied (or lying?) about sync, they confirm sync before they actually save the data to disk. And I am sure that consumer SSDs do something similar, because consumer SSD are usually faster (although their speed frequently fluctuates to extreme extents) than their corresponding enterprise variants, which is impossible in a safe way without power loss protection capacitors.

  7. Backup won't help you by cerberusss · · Score: 5, Insightful

    FTFS:

    If you have switched to SSD for either personal or business use, do you follow the recommendation here that spinning-disk media be used as backup as well?

    So how do backups help you? Except for ZFS and btrfs (?), no file systems check for data integrity. You're not going to detect the bitrot taking place, and you'll happily send that rotten data to your backup until the corruption is noticed in some other way.

    --
    8 of 13 people found this answer helpful. Did you?
    1. Re:Backup won't help you by bws111 · · Score: 5, Insightful

      The bit rot happens when the drives have been powered off for an extended period. The backups are taken before the power is removed.

  8. Re:Real enterprise has not gone to SSD by fluffernutter · · Score: 2

    To the people saying 'no datacenter goes without power for a week'. I know one that did due to a natural disaster. THey spent 1000's of hours bringing that datacenter up. Do you think they would have wanted to have been messing around reconfiguring raid arrays and rebuilding on top of that? It is not just the data you lose, it is the configuration.

    --
    Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
  9. Re:How powered off is "powered off"? by plover · · Score: 4, Informative

    Your stuff's cargo container was not heated during shipping. If it was stacked below the deck line, where it was not exposed to the sun, it didn't reach 55C during the journey.

    --
    John
  10. Re:Thumb Drives by Anne+Thwacks · · Score: 2

    If the temperature in my pockets exceeds 55C, then data on a flash drive is not likely to be my biggest concern. YMMV.

    --
    Sent from my ASR33 using ASCII
  11. Re:I image my SSD regularly by Dunbal · · Score: 3, Insightful

    Haha! I'm old enough to remember when Seagate was the best.

    --
    Seven puppies were harmed during the making of this post.
  12. Re:How powered off is "powered off"? by ihtoit · · Score: 2

    reason being that you shouldn't be buying Enterprise grade through a brick retailer. You should be leasing it via a support contract: the premium is with a tech on the other end of the phone who's out in a couple hours to replace a dud drive and have your RAID rebuilt before the day ends, rather than you running to the nearest PC World for a TB Seagate pocket spinny. Like I've just had to. If I'd had a support contract (hence Enterprise grade drives as they generally insist on anyway since they're easier for ICTs to RMA) then I'd've been at my mum's now sealing her windows rather than babysitting my new drive still.

    --
    Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
  13. Real world use cases needed by ITRambo · · Score: 2

    I skimmed though Seagate's paper. At first glance, it appears to have a hidden agenda. That is to make hard drives preferable to solid state drives for everyday use, as Seagate primarily sells hard drives. For long term storage that is what is generally done anyway due to cost, along with tape. For performance, 120+ GB SSD's cannot be beaten, one on one, by any hard drive. Does anyone know of data that indicates that (non-OCZ) drives lose data over time during use, not when powered off for many months after use? Seagate's paper may not be useful if it doesn't correspond to real world use.

  14. Backups by Rich0 · · Score: 2

    If you have switched to SSD for either personal or business use, do you follow the recommendation here that spinning-disk media be used as backup as well?

    First, anything stored on any kind of drive should be backed up if you care about it.

    Second, if you do backup, who backs up to SSD? You don't need frequent fast random-access on backups, and SSD is about the most expensive storage technology around per-GB. Anybody doing bulk storage is going to be doing it on either hard disks, tape, or something optical.

    So, if you're backing your data up, you'll be backing it up to something safe most likely.

    Of course, this does bring up the need for the ability to verify the integrity of your data at-rest, and right now I'd say ZFS/btrfs are the best way of accomplishing this. You could also do hashing above the filesystem layer, but that requires a lot of overhead if your files change frequently. If your files don't change much than something like tripwire would be fine. You'd want to run that more often than you rotate your backup media so that you don't discard the last-known-good version of anything.

  15. Re:How powered off is "powered off"? by fnj · · Score: 2

    Yes, conceptually all flash data has to decay when powered off. But implementation tradeoffs vary widely. A dirt-cheap Microchip PIC18F2580 microcontroller has flash data retention without refresh "conservatively estimated" at 40 YEARS MINIMUM and 100 years typical (page 3, 10, 435). The number of previous erase/program cycles that retention is predicated on is not given, but is probably a single one, or a few, out of a typical endurance of 100,000 cycles and a minimum of 10,000 from -40 to +85 C. AFAIK there is no wear leveling or block sparing in microcontroller flash memories.

    I have NEVER HEARD of an embedded guy ever running into a case of either cycle exhaustion or data decay in the program memory such microcontrollers (if data is written to flash during operation, specs do have to be considered).

    SSDs have flash design tradeoffs remarkably different from this. For example, MLC individual cell endurance is around 1000-10,000, and retention is far less as seen in the article and comments here. In return, the access time is vastly faster and the density vastly higher.

  16. Re:Thumb Drives by jarfil · · Score: 5, Insightful

    Tape is some of a myth.

    The only safe media, is that which you keep copying before it deteriorates. Not HDDs, not SSDs, not CDs, not thumbdrives, and not tape. Any media you leave untouched past its data retention period, will lose data.

    What you need is to check every copy of your data for any sign of degradation, and replace it with a fresh copy as soon as, or before, it begins to fail. Tape may give you the most time between checks, but it doesn't change the fact that data you forget about is data you will lose.

  17. Does anyone still return faulty drives? by Anonymous+Brave+Guy · · Score: 2

    You should be leasing it via a support contract: the premium is with a tech on the other end of the phone who's out in a couple hours to replace a dud drive and have your RAID rebuilt before the day ends

    I always think the idea of giving back a storage device that has had real data on it under some long-term warranty or rapid on-site service agreement is mostly marketing spin.

    Every company I work with has a simple policy on this, for basic security/privacy reasons: a drive that is DOA can go back, but anything that has ever been touched by real data is written off and securely destroyed. Any warranty longer than a few days is therefore worthless to us, as is any rapid service support contract if all it's going to do is swap the failed drive out for a new one.

    Obviously this is only applicable to drives where recovering data is potentially possible. If everything (including things like swap space) was encrypted before it hit the drive's controller then returning the unit is in theory an option. But usually it's not worth the trouble to verify that this was the case throughout whatever working life any drive had, and permanent encryption introduces a significant performance hit.

    I've seen enterprise support contracts from major brands that specifically say a failed drive won't have to be returned for exactly these reasons.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  18. Charge trap vs floating gate NAND... by AcquaCow · · Score: 4, Interesting

    Newer 3D NAND is using a charge trap design which basically solves the electron leakage issue found with the older floating gate NAND...

    Also, the move to the newer 3D NAND brings us back up to 40nm processes vs the 10nm gates we are currently working with, allowing for much better reliability.

    Disclaimer: I've been selling enterprise flash storage for the last 6 years.

    --

    up 12 days, 22:30, 2 users, load averages: 993.20, 994.21, 994.56
    *makes note to limit user processes...
  19. Re:Eureka! by Sertis · · Score: 2

    Read again - more temperature means less time. So if there's no lower limit, SSD without power will be best stored at 0 Kelvin

    No I read the article. It's related to electron mobility at the time the data is written. If you heat up the SSD after it's turned off, electron mobility increases and you'll get more leakage. But if you wrote data when it was hot, you have a better signal to noise ratio.