reader50

Member
  • Content count

    89
  • Joined

  • Last visited

  • Days Won

    2

reader50 last won the day on December 14 2016

reader50 had the most liked content!

Community Reputation

3 Neutral

About reader50

  • Rank
    Member

Recent Profile Visitors

4284 profile views
  1. BackBlaze has posted their Q2 2017 Hard Drive Reliability stats. 83,151 drives this time. Not a lot of surprises. HGST still comes out on top, while Seagate has some problems with their 4TB models. The 8TB models look good regardless of manufacturer. Biggest surprise for me: BackBlaze has begun deployment of 12TB drives, and in decent quantity too. They don't say what model(s). HGST and Seagate both have 12TB drives shipping, so either is a safe bet. To my knowledge WD hasn't announced anything past 10TB, while Toshiba has just gotten their 8TB models shipping in quantity.
  2. When you save an updated file. Or the OS appends a log file. The change may be trivial from your perspective (perhaps only a few bits altered) but the SSD cannot erase/rewrite tiny spaces. Only the huge internal blocks.
  3. "Garbage collection" refers to software rather than drives. When a program no longer has use for variable space (usually strings or arrays) then that storage space becomes "garbage". Garbage collection refers to releasing that space to the memory manager for reuse. The user cannot do anything about garbage collection. The app developer has to do that, and the OS developer can provide tools to make it easier. "Trim" is a function used to help SSDs remain efficient. If you delete a file, the OS usually only wipes the filesystem directory entry and updates the bitmap to show those blocks are free space. The OS doesn't usually write zeroes to the blocks that the file used to occupy, because this would take time; the computer would act slower. However, the SSD is independent of any particular OS or filesystem. It doesn't know how to read directory entries or volume bitmaps. It keeps its' own map of blocks that have been written to, but internal SSD blocks are big. Say, 32 MB big. These are the smallest "zones" that an SSD can erase. Unlike a hard drive, an SSD cannot erase standard 512-byte blocks at will. Only relatively huge blocks. When it comes time to modify contents in an internal block, the SSD must do a dance. All unchanged data has to be copied to a standby block, along with the modified data. The old block is then erased and becomes a standby block. All of this takes time. If the SSD is running low on standby blocks (overprovisioning), it can take a lot of time for the SSD to consolidate used space into fewer blocks. Trim works by letting the OS notify the SSD that a particular space is actually free. Although data has been written to that space in the past, it should now be disregarded. When the SSD has to manage it's internal blocks, that space need not be copied. If the OS and SSD both support Trim, then it works automatically. Whenever a filesystem block is freed up, Trim passes the info to the SSD. The SSD uses the info to act more efficiently, which the user sees as the SSD running faster. As to your last question about Trim, the user could turn it off. But who would want to. A utility could be used to read an existing filesystem, then send Trim notices for every free block in the file system. This would be useful if the SSD had previously been used with an OS that didn't support Trim. Such OSes are in the past today, so such a utility wouldn't do anything.
  4. This is a timely and useful offer. Kudos to DriveSavers -- and it won't hurt them in the long run. People who need the service (or just hear of it) may well try DriveSavers first the next time. For anyone who does need it - remember, the drive(s) must be shipped by September 15.
  5. The recent DriveSavers story is missing its associated comment thread. I wanted to offer kudos to them for their timely offer. Also, I originally put this comment in the then-current comments thread here. My apologies - this feedback forum was the proper place. That misplaced comment should be deleted.
  6. Are the sizes a mistype? If accurate, the BX300 has regressed. BX100 (2015 review): 120, 250, 500 GB, 1 TB BX200 (2015 review): 240, 480, 960 GB BX300 (2017 review): 120, 240, 480 GB
  7. WD recently announced 4-bits-per-cell 3D NAND. Not sure what we'll call it - QLC? 4LC? They didn't mention when product will ship, so 2018 at the earliest. Probably not helpful for your needs, but with 3D QLC coming, I expect 3D TLC is stable today.
  8. Why would the 4, 6, and 8TB be done via dual drives today? Single-drive solutions would be quieter, cooler, and far cheaper for those sizes.
  9. From retail drive pictures, the WD Gold appear to be rebranded HGST He drives.
  10. HGST does have a 12TB enterprise drive out, currently running $630 on ebay. I've yet to see it in the regular channels. Look for HGST He12 If you are looking for large economical storage, drives in the 6-8 TB range are approaching half the price-per-TB of that He12. A RAID array in a NAS would get you more storage, and probably at a lower price. Admittedly with more noise.
  11. You posted your thread in the right place.
  12. I find myself in agreement.
  13. It's been 15 months now, still no sign of a 3 TB drive in 9.5mm. Unless I want to drop $1500 on a 4TB SSD. I didn't think it would take this long for an upgrade to appear. Larger drives used to appear like clockwork.