Slashdot Mirror


Seagate's Shingled Magnetic Recording Tech Boosts HDD Capacities to 5TB and Up

crookedvulture writes "Seagate has begun shipping hard drives based on a new technology dubbed Shingled Magnetic Recording. SMR, as it's called, preserves the perpendicular bit orientation of current HDDs but changes the way that tracks are organized. Instead of laying out the tracks individually, SMR stacks them on top of each other in a staggered fashion that resembles the shingles on a roof. Although this overlap enables higher bit densities, it comes with a penalty. Rewrites compromise the data on the following track, which must be read and rewritten, which in turn compromises the data on the following track, and so on. SMR distributes the layered tracks in narrow bands to mitigate the performance penalty associated with rewrites. The makeup of those bands will vary based on the drive's intended application. We should see the first examples of SMR next year, when Seagate intends to introduce a 5TB drive with 1.25TB per platter. Traditional hard drives top out at 4TB and 1TB per platter right now."

195 comments

  1. 25% improvement in space ... by Covalent · · Score: 4, Informative

    ... for a significant reduction in speed?

    No thanks.

    --
    Great warrior...hrmph! Wars not make one great.
    1. Re:25% improvement in space ... by The+MAZZTer · · Score: 5, Informative

      Only write speed, it sounds like. So storing one-write/many-read files might be a good use case; such as videos, photos, music, etc...

    2. Re:25% improvement in space ... by jedidiah · · Score: 1

      You still have to get the data on there. If that process is too bothersome when compared to alternatives, then us data hoarders may just pass on these drives.

      Plus, these drives will likely go for a hefty premium above and beyond smaller drives (like 4TB ones) that also perform better.

      They really don't need any additional reasons to dissuade potential buyers.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    3. Re:25% improvement in space ... by Anonymous Coward · · Score: 1

      and only degraded write speed once the disk is near full. fresh writes are appended on the end and stuff in the middle is marked "to be reclaimed."

    4. Re:25% improvement in space ... by Anonymous Coward · · Score: 0

      I don't think the description should be taken literally, the drive will not wait for a whole platter rotation to rewrite the damaged data. This would kill write speeds by an order of magnitude. Rather, i would speculate that a more complex magnetic head reads, writes and corrects the data in a single pass.

    5. Re:25% improvement in space ... by Anonymous Coward · · Score: 2, Insightful

      Pretty sure these will be marketed towards the write-rarely "backup/media dump" segment. At lower $/GB than a non-shingled 5.4kRPM.

    6. Re:25% improvement in space ... by jedidiah · · Score: 1

      It's not how frequently you're going to be writing to the drive but how much data you want to put on it when you do. Being unable to clone a drive WILL be a problem.

      You are trying to argue with precisely the sort of user you're trying to speak for.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    7. Re:25% improvement in space ... by pwizard2 · · Score: 1

      How much of a speed reduction are we talking about here? If it's a few seconds slower, I can live with that--I'd rather have more space.

      --
      "It is a denial of justice not to stretch out a helping hand to the fallen; that is the common right of humanity."
    8. Re:25% improvement in space ... by sjames · · Score: 1

      It could be fine for some applications, especially with an SSD cache. For other uses, not so good.

    9. Re:25% improvement in space ... by sjames · · Score: 3, Insightful

      You would be able to clone a drive, just not as quickly.

      But from the sound of it, it is probable that well formed sequential writes (such as cloning a whole disk) might run at full speed, there's no need to read and rewrite a track if you can hint that it will be overwritten anyway.

    10. Re:25% improvement in space ... by Anonymous Coward · · Score: 0

      First HD to benefit from being TRIMmed?

    11. Re:25% improvement in space ... by mattack2 · · Score: 1

      For something like DVR recordings, I don't need the speed, and just want the space.. So it could be a reasonable tradeoff.. I didn't see how much of a difference it would make in cost.

    12. Re:25% improvement in space ... by sjames · · Score: 1

      TRIM could do it, or even big write requests that span the triplet.

    13. Re:25% improvement in space ... by Anonymous Coward · · Score: 0

      ... for a significant reduction in speed?

      No thanks.

      And this is where hybrid SSD design comes into play. These type of harddrives utilitizing SMR stacking need to take advantage of real SSD chips as priority 1 storage to ensure that the data is able to write to the platters without the user being immediately affected. At the very least, depending on how much SSD is bundled in with these harddrives, would delay the user experiencing the poor write speeds. For most things, given enough SSD, you probably wouldn't observe the penalty hit for higher capacities. But say, if you were creating or moving more data than can be placed on an SSD, you'll feel the burn pretty soon.

      Then again, when it comes to the end of the day and considering how reliable magnetic spindle-based harddrives in general are, is it really worth losing 5 TB of data off a single drive compared to what is possible on an ordinary non-SMR'd drive? SMR'd drives aren't even close to being a viable alternative to classic magnetic tape storage -- they last longer and are far more reliable than SMR'd drives (partially theoretically, just taking into account what we already know of current non-SMR'd drives). An SMR'd drive is almost like a hybrid bridge between non-SMR'd drives and magnetic tape storage. Bad alternative IMO. X_x

    14. Re:25% improvement in space ... by swillden · · Score: 1

      Only write speed, it sounds like. So storing one-write/many-read files might be a good use case; such as videos, photos, music, etc...

      Add a good-sized solid-state non-volatile cache and that write speed degradation can be made invisible... or even reversed. Writes can appear to be extremely fast -- no need to wait for seeks -- and fully reliable. There may be pathological workloads which continuously write small, scattered pieces to many different locations on disk, such that eventually the cache fills up with unpersisted changes and new writes have to be delayed, so the resulting drive would be inappropriate for those workloads. About the only example I can think of is a heavily-loaded database server, and not even most of those would have the pathological workload characteristic.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    15. Re:25% improvement in space ... by bingoUV · · Score: 1

      Better handled in software. Otherwise the device is kaput once either of the contained ssd or hdd fail. With software we can decide the aggression of caching better.

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
  2. clearly I don't understand something... by Anonymous Coward · · Score: 2

    rewriting data compromises data on the next track, which needs to be read/written, which compromises...
    So you need to rewrite the whole damn 5TB disk?

    "higher bit densities come with a penalty"
    That sounds like an understatement.

    1. Re:clearly I don't understand something... by intermodal · · Score: 2

      TFA says they've limited the overlap to prevent the need to rewrite the whole disk. Only the three-track segments, which do not affect the tracks beside the trio.

      That said, I won't be an early adopter on this one. We'll see how it pans out in the real world before I consider deploying this.

      --
      In SOVIET RUSSIA... erm...NSA AMERICA, the Internet logs onto YOU!
    2. Re:clearly I don't understand something... by TheCarp · · Score: 1

      that is where they got the name,... it runs down your platter like shingles down your torso. What you pictured a roof?

      --
      "I opened my eyes, and everything went dark again"
    3. Re:clearly I don't understand something... by BigMike · · Score: 1

      rewriting data compromises data on the next track, which needs to be read/written, which compromises...
      So you need to rewrite the whole damn 5TB disk?

      "higher bit densities come with a penalty"
      That sounds like an understatement.

      You're gonna want to get rid of all that DRAM you've got then ...

    4. Re:clearly I don't understand something... by Anonymous Coward · · Score: 0

      Then RTFSummary
      SMR distributes the layered tracks in narrow bands to mitigate the performance penalty associated with rewrites

    5. Re:clearly I don't understand something... by X0563511 · · Score: 1

      DRAM refreshes and rewriting data are two different things.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    6. Re:clearly I don't understand something... by Anonymous Coward · · Score: 0

      clearly I don't understand something...

      That sounds like an understatement.

    7. Re:clearly I don't understand something... by Anonymous Coward · · Score: 0

      I think the joke was "Never, ever write to the disk"

    8. Re:clearly I don't understand something... by Joce640k · · Score: 1

      So you need to rewrite the whole damn 5TB disk?

      You failed to read even the summary?

      --
      No sig today...
    9. Re:clearly I don't understand something... by Richy_T · · Score: 1

      I'd imagine with some creative techniques, it would be possible to attempt to write in such a way that rewrites are minimized. If you can write next to unused sectors etc. That could be bad for something like truecrypt though depending on the algorithm.

  3. leaked map by arbiter1 · · Score: 2
  4. Blame Microsoft by Russ1642 · · Score: 4, Funny

    People will just blame Windows for the sluggishness.

    1. Re:Blame Microsoft by epSos-de · · Score: 1

      No need. Seagate will come up with a design to leave out one empty row for every 10 rows of overlapping data. This way they can manage the amount of data that needs to be rewritten. This of course will happen in the next generation, after they see how their first design sucks.

    2. Re:Blame Microsoft by jones_supa · · Score: 1

      The sad truth is that these days I usually blame Linux for the sluggishness. :/ Well, not the kernel, but the desktop.

    3. Re:Blame Microsoft by tchdab1 · · Score: 1

      Queue the jokes for SOS (sh*t on a shingle).

    4. Re:Blame Microsoft by Anonymous Coward · · Score: 0

      If you're using Gnome, that is indeed usually to blame. And it's not Gnome as a whole either. It's GTK+. I don't know what they're doing to it. Last fast Gnome I seem to remember was version 2.6.8. It's been going slower and slower since then. I'm not using KDE - I just don't like the UX, but each time I fire it up it appears to be lightning fast.

      When it comes to GTK+, just running XfWM4 instead of compiz or metacity speeds the desktop by 2x or 3x (I'm just eyeballing it, I haven't actually measured it).

    5. Re:Blame Microsoft by rpstrong · · Score: 1

      No need, because their current generation essentially does that. Read the article.

    6. Re:Blame Microsoft by Anonymous Coward · · Score: 0

      To fix Linux sluggishness, install Windows dual-boot on it and use the Windows partition exclusively for a week. When you use the Linux partition again it will be really fast!

  5. I wonder if they could make 50tb drives today? by Anonymous Coward · · Score: 2, Interesting

    Sometimes I wonder if they already have the technology to make 50 or 100 tb drives and they are just trying to keep their profit margins up by incrementally increasing storage at a fixed rate every year.

    1. Re:I wonder if they could make 50tb drives today? by Sponge+Bath · · Score: 1

      ...they already have the technology to make 50 or 100 tb drives

      Stored in a secret Area 51 bunker staffed by Brent Spiner.

    2. Re:I wonder if they could make 50tb drives today? by MiniMike · · Score: 2

      They have the technology, but it's limited to write-only drives.

    3. Re:I wonder if they could make 50tb drives today? by King_TJ · · Score: 2

      Seriously, I don't think so.... In fact, from every indication, they're all really struggling to find increasingly creative ways to cram more magnetic data on a given amount of platter space, and reliability is probably suffering.

      I don't have proof, but MANY people I know who are in I.T. and work with large capacity drives every day will tell you it's their observation that SATA drives became less reliable when capacities went over the 1 to 1.5TB mark. The 2TB drives all started using the newer "perpendicular write" technologies, and I suspect the added complexity led to higher failure rates.

      Just as anecdotal evidence I've observed personally? When I built a FreeNAS media server last year, I used brand new 2TB drives in it. In 6 months' time or so, I had 2 of the 7 drives in it fail. I also experienced a drive failure with an external 2TB SATA drive in a Maxtor enclosure. My Mac Pro tower, however, also ran 24 hours/7 days because I had a small ftp server on it, among other things ... and it had a mix of 1TB and 1.5TB drives in it (all purchased at least 2-3 years ago). To this day, all of those drives are still running fine. My wife's "Time Machine" external backup drive on her iMac died late last year too, just outside the 1 year warranty period on it. What was in it? A Seagate 2TB drive.

    4. Re:I wonder if they could make 50tb drives today? by dbIII · · Score: 1

      I've lost a pile of 2TB Seagates recently as well, with little trouble from other brands other than those 1.5TB green WD drives that seemed to all die within a few months. Other WD drives seemed OK, but close to 100% mortality on around ten or twelve of that model.
      Meanwhile the only 1TB drives I've lost were getting a bit old anyway and had a pile of ECC errors on the way out as a bit of a warning.
      I'm impressed with BSD and ZFS - I'm getting surprisingly high performance out of even IDE drives on 32 bit "netburst" xeons on a couple of test rigs and impressive behaviour during drive failures of old and crappy disks. On current stuff with good disks and a lot of memory it flies.

    5. Re:I wonder if they could make 50tb drives today? by Anonymous Coward · · Score: 0

      Nice theory, except the switch to perpendicular recording was around 250GB.

    6. Re:I wonder if they could make 50tb drives today? by RicktheBrick · · Score: 1

      I really do not care about any more advancements in hard drive density. In fact I recently purchased a 128 gigabyte SSD and replaced a terabyte hard drive. I believe that for most people more storage just leads to more wasted storage. Storing a lot of video that is seldom if ever watched. It is the same as going to an all you can eat restaurant. It just encourages you to eat too much food that will go to your waist so I do not go there anymore. Buying a huge hard drive will just encourage people to steal more movies and music to fill them. Most of which will not be viewed or listen to more that once if that much. By the way the SSD makes my computer boot in about half the time so if one must have music or movies just buy them on a cd, dvd, or blu-ray.

    7. Re:I wonder if they could make 50tb drives today? by bhiestand · · Score: 1

      I don't use green drives in any serious capacity (seems best just to avoid the issue), but you should be able to make them work by turning off all the green functions.

      --
      SWM seeks new sig for a brief fling
    8. Re:I wonder if they could make 50tb drives today? by metaforest · · Score: 1

      Perpendicular writes began in the 5GB drive era.

    9. Re:I wonder if they could make 50tb drives today? by dbIII · · Score: 1

      It just seems that there was one 1.5TB green drive that had ridiculous failure rates. I didn't go out of my way to buy them but because they were cheap and put in portable drives lot of them ended up here - I think I only bought two but were asked to look at another 8 or so that had died. There was some sort of large "desktop" USB thing that had two of them to make up 3TB and that was popular for a while.
      I used some bare green disks for a while, mostly 2TB, in a machine used as an offsite data store but they were too slow to use for long.

  6. Not going back by Dunbal · · Score: 2

    I switched to SSD technology and I'm never going back. Yeah ok there are no 5TB drives yet. And 1TB is still insane. But 512GB is almost affordable, 256GB certainly is. If I need more storage, I'll just keep buying more. And eventually the price on the large drives will also come down. Sorry Seagate, the game is already over except for very specialized, very niche storage roles.

    --
    Seven puppies were harmed during the making of this post.
    1. Re: Not going back by mikael_j · · Score: 1

      Yeah, at this point I only use regular hard drives for backups and networked media storage. No point in spending lots of money on SSDs for that just yet.

      --
      Greylisting is to SMTP as NAT is to IPv4
    2. Re:Not going back by Anonymous Coward · · Score: 1

      1TB is down to $590, which is cheaper than stacking up smaller ones. Still mildly painful, but it's getting low enough where you can almost justify just skipping over the 512GB ($400) and 256GB ($200) models entirely.

    3. Re:Not going back by jedidiah · · Score: 3, Insightful

      Yeah. Buy storage in 256G chunks.

      That makes as much sense as someone getting giddy over how large of an array they can make out of 10 year old hard drives. It will be unnecessarily complex and resemble some sort of Rube Goldberg machine.

      Large drives are hardly a "niche" use case.

      On the other hand, there is a very wide gap between what expensive SSD can reasonably deliver and what much cheaper spinning rust can manage. Spinning rust can manage a wide range of use cases.

      It's SSD that represents the niche: small data for very casual users that don't do much of anything.

       

      --
      A Pirate and a Puritan look the same on a balance sheet.
    4. Re:Not going back by Dunbal · · Score: 1

      I don't think you've seen how thin SSD drives actually are. As for what it can manage, failure rates are down now and just about equivalent to platter hard drives. You do realize that those can fail too, right? And for the rest of "management" well it stores info, which is what I want it to do. And it does that and reads it very, very quickly. If you compare the price of an SSD to the price of a regular hard drive you're doing apples to oranges. Go ahead and compare them to one of these ultra-pimped high RPM hybrids, and then talk to me about price. The SSD is still faster and cheaper. But yeah, the 10 year old 7200 rpm hard drives are much cheaper. A motorcycle is also cheaper than a car.

      --
      Seven puppies were harmed during the making of this post.
    5. Re:Not going back by jedidiah · · Score: 1, Insightful

      I know how thin SSD drives are. I have some. Although I realize their limitations. I just don't swim in the kool-aid or act like some sort of tech fashionista.

      It's good that you mention drive failures because spinning rust gives you some warning. It makes it easier to prepare rather than just being surprised suddenly.

      The cost difference also makes it more likely that you have some degree of protection either from array redundancy or extra copies of the data.

      Not going out of your way to waste as much money as quickly as possible has some practical benefit.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    6. Re:Not going back by Kjella · · Score: 1

      Well if you're happy with 256GB storage total, but you can get a 128GB SSD + 2TB HDD for the same money. If streaming covers all your needs then good for you but heck my Steam directory full of 10GB+ games alone would give it breathing issues. I think they do damn well in pairs, just checked and I'm still looking at a 16:1 price advantage (250 GB SSD ~= 4 TB HDD). Personally I just love the ability to have near infinite space for a few bucks, you can be a digital hoarder and still have it fit a mid size cabinet. But hey, if streaming or download&delete works for you by all means don't.

      --
      Live today, because you never know what tomorrow brings
    7. Re:Not going back by LordLimecat · · Score: 3, Insightful

      512GB hits the use case for probably 95% of consumers (based anecdotally on backup sizes and harddrive capacities for ~3-400 friends, customers, family, etc).

    8. Re:Not going back by fast+turtle · · Score: 1

      Tell that to Harely Davidson then. Damn bikes start at 20k and simply go up for a new one and yes I can buy a new Chevy or Ford for less.

      --
      Mod me up/Mod me down: I wont frown as I've no crown
    9. Re:Not going back by ColdWetDog · · Score: 0

      Going by your UID, you're getting on the older side. You're gonna check out sooner or later - might as well get as much done as possible. Practical benefit might be weighted towards performance rather than price

      --
      Faster! Faster! Faster would be better!
    10. Re:Not going back by Dunbal · · Score: 1

      Well if you want to compare pricey "top of the line" bikes, you should compare them to pricey "top of the line" cars. Try buying a Mercedes 500 series for $20k...

      --
      Seven puppies were harmed during the making of this post.
    11. Re:Not going back by Anonymous Coward · · Score: 1

      >harley davidson
      >top of the line bikes

      maybe in time spent wrenching on them instead of riding them

    12. Re:Not going back by MikeBabcock · · Score: 1

      How do you store the last ten years' of photos you've taken, or your music collection?

      The first two days of my child's life is enough raw video data to seriously dent an SSD all on its own.

      I use an SSD for booting, but my primary filesystem is all spinning platters. With modern caching options (on Linux and Windows at least), you can get very near SSD speeds on frequently accessed files using a huge hard drive as your data store anyway.

      --
      - Michael T. Babcock (Yes, I blog)
    13. Re:Not going back by Trifthen · · Score: 1

      On the other hand, there is a very wide gap between what expensive SSD can reasonably deliver and what much cheaper spinning rust can manage. Spinning rust can manage a wide range of use cases.

      It's SSD that represents the niche: small data for very casual users that don't do much of anything.

      If this were even close to true, large corporations would not use NVRAM technologies to back their incredibly critical data stores. That "spinning rust" in a mid-sized 8-drive RAID-10 array can deliver roughly 2000 operations per second. One 2.4TB FusionIO drive for example? over 500,000. There's not even any comparison here. The size and cost of the SAN you'd have to buy to come even close to those numbers using traditional platters is on the order of multiple racks, compared to a single PCIe card.

      Hard drives weren't always large and inexpensive. In 1996, it was huge news when manufacturers could advertise prices less than $1/MB. Not GB, MB. 1GB drives used to cost $1000 less than 20 years ago. Current high-end Intel 840 pros cost about $220 for 256GB. They're clearly getting cheaper at a pretty fast rate. And that's with NVRAM, which is probably getting phased out in favor of ReRAM in the next 5 years. ReRAM is even faster, has higher density potential, and is cheaper to produce. It leapfrogs NVRAM by almost two orders of magnitude, to the point where it's basically as fast as RAM.

      No hard drive, RAID, or SAN could ever say that, no matter how much cache, how fancy of a RAID, or what interface it uses. We're entering an era where persistent storage will effectively be an afterthought. To see people still defending traditional hard drives in the face of that is odd to say the least.

      --
      Read: Rabbit Rue - Free serial nove
    14. Re:Not going back by Anonymous Coward · · Score: 0

      That makes as much sense as someone getting giddy over how large of an array they can make out of 10 year old hard drives.

      YES! Stripe them all and do 1.21GB/s, HaHAhA!

    15. Re:Not going back by dbIII · · Score: 1

      That makes as much sense as someone getting giddy over how large of an array they can make out of 10 year old hard drives

      Which actually does make sense if you want a freebsd zfs test rig and actually want a few disk failures to see how you can handle them instead of finding out the hard way on the important stuff. I get that your point is about daily use though.

    16. Re:Not going back by gmack · · Score: 1

      Whether a spinning rust drive gives you warning depends entirely on the failure mode. I've had more than one die on me with no warning whatsoever thanks to problems with the drives electronics.

    17. Re:Not going back by Waccoon · · Score: 1

      It's SSD that represents the niche: small data for very casual users that don't do much of anything.

      Or perhaps very serious users that just don't happen to have a collection of Blu-ray rips on their workstation.

      Lately, I've been seeing a lot of people use SSD arrays for their SQL databases.

    18. Re:Not going back by Terrasque · · Score: 1

      http://www.anandtech.com/show/4329/intel-z68-chipset-smart-response-technology-ssd-caching-review/2

      Intel SRT tech seem to bring a good compromise. Best of both worlds sort of.

      --
      It's The Golden Rule: "He who has the gold makes the rules."
    19. Re:Not going back by Anonymous Coward · · Score: 0

      If this were even close to true, large corporations would not use NVRAM technologies to back their incredibly critical data stores. That "spinning rust" in a mid-sized 8-drive RAID-10 array can deliver roughly 2000 operations per second. One 2.4TB FusionIO drive for example? over 500,000. There's not even any comparison here. The size and cost of the SAN you'd have to buy to come even close to those numbers using traditional platters is on the order of multiple racks, compared to a single PCIe card.

      I thought your information might be a little out of date, since I remembered hearing about those 500k IOPS PCIe card-drives a while back, so I did a bit of googling for current stats. It seems that back in March FusionIO managed to get one a 365GB ioDrive2 to pull 9.6 million IOPS using a custom filesystem and some other software tweaks. However, looking at their products for sale section, they're currently only advertising 1.3 million for their much larger (and probably still insanely expensive) 10.2TB ioDrive Octal, so your comparison vs. spinning rust is only potentially an order of magnitude more impressive than previously stated.

    20. Re:Not going back by Richy_T · · Score: 1

      Except I have a couple of sub-500GB hard drives that are soldiering on as drive after drive of 1TB+ falls by the wayside. It's actually kind-of annoying as I'd like a space upgrade but don't want to swap out that reliability. They're not even kept in a particularly healthy environment either (80-90F temperatures)

    21. Re:Not going back by david_thornley · · Score: 1

      SSDs are not niche anymore. Have you tried an SSD as a system disk (they're plenty big for that nowadays) and used spinning rust for the big drives you're not reading from constantly? Sweet.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  7. maintenance by Anonymous Coward · · Score: 1

    I can only imagine how long it would take to use a defrag program to degrag that drive. And dont get me started on using something like spin-rite to do a hard drive diagnosis where it needs to read and write to the heads many times trying to pull data off an iffy platter!

    1. Re:maintenance by Anonymous Coward · · Score: 0

      I can only imagine how long it would take to use a defrag program to degrag that drive. And dont get me started on using something like spin-rite to do a hard drive diagnosis where it needs to read and write to the heads many times trying to pull data off an iffy platter!

      This isn't the 90s.
      Why in the hell would you be using a file system so old it benefits from defragging?
      Or was this a subtle joke?

    2. Re:maintenance by X0563511 · · Score: 1

      You mean like everyone running Windows, as well as anything using an ext filesystem?

      From e2fsck:
                    -D Optimize directories in filesystem. This option causes e2fsck
                          to try to optimize all directories, either by reindexing them if
                          the filesystem supports directory indexing, or by sorting and
                          compressing directories for smaller directories, or for filesys-
                          tems using traditional linear directories.

                          Even without the -D option, e2fsck may sometimes optimize a few
                          directories --- for example, if directory indexing is enabled
                          and a directory is not indexed and would benefit from being
                          indexed, or if the index structures are corrupted and need to be
                          rebuilt. The -D option forces all directories in the filesystem
                          to be optimized. This can sometimes make them a little smaller
                          and slightly faster to search, but in practice, you should
                          rarely need to use this option.

                          The -D option will detect directory entries with duplicate names
                          in a single directory, which e2fsck normally does not enforce
                          for performance reasons.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    3. Re:maintenance by jedidiah · · Score: 0

      > You mean like everyone running Windows, as well as anything using an ext filesystem?

      You have no idea what you are talking about. Your attempt to cite information you clearly don't understand doesn't alter this.

      No one defrags drives under Linux.

      NTFS requires defrags? How lame.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    4. Re:maintenance by Shark · · Score: 1

      Technically on mechanical drives, ext4 benefits from defragging... So does btrfs.

      --
      Mind the frickin' laser...
    5. Re:maintenance by LordLimecat · · Score: 2

      http://askubuntu.com/questions/9306/do-i-need-to-defrag-ext-file-systems
      http://en.wikipedia.org/wiki/Ext3#Disadvantages

      There is no online ext3 defragmentation tool that works on the filesystem level.... While ext3 is more resistant to file fragmentation than the FAT filesystem, ext3 can get fragmented over time or for specific usage patterns, like slowly-writing large files.[23][24] Consequently, ext4, the successor to ext3, is planned to eventually include an online filesystem defragmentation

      All filesystems running on magnetic media require defragmentation. Those that "do not" are defragging. Fragmentation is a fact of life with any filesystem. And before you start up with the "well ext requires less", so does NTFS: comparisons between ext and "the Windows world" are invariably referring to FAT, not NTFS, which is by all accounts a strong competitor to the ext family.

      So a better remark might be "ext3 doesnt support online defrag? How unfortunate."

      You have no idea what you are talking about. Your attempt to cite information you clearly don't understand doesn't alter this.

      How appropriate for your post.

    6. Re:maintenance by sjames · · Score: 1

      Right there in the help it says you won't normally use -D. Besides, is there anything that hasn't updated to ext4 that would also likely have a 5TB drive?

    7. Re:maintenance by Anonymous Coward · · Score: 0

      Technically same thing on NAND based SSDs (opening a page takes a few us for MLC).

    8. Re:maintenance by Anonymous Coward · · Score: 0

      No one defrags drives under Linux.

      xfs_fsr - filesystem reorganizer for XFS

    9. Re:maintenance by fast+turtle · · Score: 1

      Check out the Win7 Tasks - Defrag is automatic and yes - NTFS requires defragmentation not only of the File system but the god damn index. BTW Don't allow an NTFS disk to exceed 50 percent full or you will suffer data loss/corruption - don't believe me? Check the MS Knowledge base and yes it still applies to Win8 since it's using NTFS.

      --
      Mod me up/Mod me down: I wont frown as I've no crown
    10. Re:maintenance by LordLimecat · · Score: 1

      TW Don't allow an NTFS disk to exceed 50 percent full or you will suffer data loss/corruption - don't believe me? Check the MS Knowledge base and yes it still applies to Win8 since it's using NTFS.

      Source or bull. The only space limitation on NTFS is that you are "supposed" to leave at least 15% of space for defrag-- though i suspect like the "swap=2xRAM" metric of old that it is only a rough guide and horribly outdated.

    11. Re:maintenance by LordLimecat · · Score: 1

      So do all filesystems operating on media with higher sequential throughput than random throughput.

      Fragmentation will occur on any filesystem which allows files to be modified without being re-written in full.

    12. Re:maintenance by mattack2 · · Score: 1

      All filesystems running on magnetic media require defragmentation.

      Why do they "require" defragmentation?

      It sounds to me like you're saying they require it *for performance reasons*. Not for technical reasons. As long as random access is as fast as you need it to be, who cares how fragmented things get?

    13. Re:maintenance by LordLimecat · · Score: 1

      They require fragmentation because when 2 10MB files are allocated, and then data is removed from the first to bring it down to 5MB, there is a 5MB hole in between the files. Over the course of time, there will be many small holes in your filesystem, and eventually you will need to write a file that is bigger than any single "hole". At that point, the data will be fragmented across several holes.

      This is simply a reality of using filesystems, and cannot be avoided without a precognitive, omnipotent filesystem. Anything you might do to alleviate this problem (reorganizing stuff on the fly) is essentially defragmenting.

    14. Re:maintenance by LordLimecat · · Score: 1

      To answer your second question, the "why" is that every magnetic media we have has seek times that are roughly 3 orders of magnitude slower than the timescales RAM and CPU work on, making every seek a massive performance hit.

      Until we completely eliminate those seek hits, defragmentation will be necessary, and at the moment SSDs are nowhere near the majority of data storage.

    15. Re:maintenance by mattack2 · · Score: 1

      Since you obviously know that a *file* can be fragmented, obviously you already know that a file doesn't have to be contiguously written.

      Thus, you don't need to defragment it. The directory structure knows that the 'file' is in blocks 1-5, 8, 14.

    16. Re:maintenance by rubycodez · · Score: 1

      but you are wrong, fragmentation can severly impact performance in the real world. Some people *do* defrag files under Linux when it becomes a problem

    17. Re:maintenance by mattack2 · · Score: 1

      Yes, as I originally said, FOR PERFORMANCE. Not for ACTUAL USAGE, IF THE RANDOM ACCESS TIME is within someone's needs.

    18. Re:maintenance by I'm+New+Around+Here · · Score: 1

      On a related note, I don't have to change the oil in my car, not for ACTUAL USAGE, since the SLUDGE BUILDUP happens over a long time.

      --
      If you think I voted for Trump because of this post, you're wrong. I voted for Dr. Jill Stein of the Green Party. Again.
    19. Re:maintenance by KingMotley · · Score: 1

      But not on a SSD.

    20. Re:maintenance by LordLimecat · · Score: 1

      Yes, and then instead of the magnetic head seeking to one track, and grabbing the entire file, it has to seek 3 times, and wait for 3 disk rotations (worst-case scenario), imposing a penalty of ~30ms before the CPU can get back to work on that data it was waiting for.

      You dont HAVE to defrag, but the excess seeks will destroy your performance. Defragging essentially tries to mitigate the very problem that SSDs solve (since they have essentially 0 seek time). Seek time accounts for 90% of the time your computer spends booting, logging in, etc, and fragmentation can double, triple, or do worse to that time.

    21. Re:maintenance by jones_supa · · Score: 1

      There is actually another recommendation which is to leave 12.5% free to prevent the MFT from becoming fragmented. NTFS reserves 12.5% of volume by default for exclusive use of the MFT. This space, known as the MFT zone, is not used to store data unless the remainder of the volume becomes full.[1]

    22. Re:maintenance by Sardaukar86 · · Score: 1

      BTW Don't allow an NTFS disk to exceed 50 percent full or you will suffer data loss/corruption - don't believe me? Check the MS Knowledge base

      Extraordinary claims require extraordinary evidence. Give us the actual knowledgebase article number (or a link to same) that we may judge for ourselves, rather than take your word for it.

      --
      ..Mullah or Pope, Preacher or Poet, who was it wrote: "Give any one species too much rope and they'll fuck it up"?
    23. Re:maintenance by jones_supa · · Score: 1

      BTW Don't allow an NTFS disk to exceed 50 percent full or you will suffer data loss/corruption - don't believe me? Check the MS Knowledge base and yes it still applies to Win8 since it's using NTFS.

      Ok, I don't believe you. I will check the Knowledge Base as you suggest. Now can you provide the KB article page in question?

    24. Re:maintenance by jones_supa · · Score: 1

      Technically same thing on NAND based SSDs (opening a page takes a few us for MLC).

      This is what I've been thinking too. Defragmentation is usually not recommended for SSDs, but as you say, one would think that reading full pages would actually provide a slight performance improvement. Then again, the contents of the SSD might be remapped to arbitrary places due to wear leveling, so the OS might not see the physical linear structure of the disk anyway. Thus the defragmentation would have to be done with some kind of cooperation between the OS and the disk, for which there exists no implementation.

    25. Re:maintenance by jones_supa · · Score: 1

      Technically on mechanical drives, ext4 benefits from defragging... So does btrfs.

      I don't think there is a file system which would be completely immune to fragmentation. The reason why ext4 is often touted to not fragment badly is because it tries to spread the files across the disk instead of storing them sequentially (like NTFS and many other file systems). I don't know what kind of strategy btrfs uses.

    26. Re:maintenance by Anonymous Coward · · Score: 0

      As far as ext4 is concerned, I will have moved to a new partition on a new drive before fragmentation becomes an issue; so for many cases, in the real world, ext4 never needs de-fragmenting. It's like the engine and oil are so good that the 'sludge build-up' in the engine is still minimal by the time the rest of the car falls apart. So you don't ever change the oil.

    27. Re:maintenance by X0563511 · · Score: 1

      "Don't normally" means that it's usually done correctly during write but not always. That it is even an option (and yes I've had to use it) means the filesystem does benefit from it. This has been around since ext2 and remains in ext4, so I don't understand what that has to do with it either.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    28. Re:maintenance by Anonymous Coward · · Score: 0

      Holy crap, you are grasping at straws. DUUUUUUHHHHHH!!!

      Of course you would need it for "performance reasons". Nobody in their right mind would argue you need it for "technical reasons", whatever that even means. When people say "this needs defragmenting", the implication IS FUCKING ALWAYS that it needs it to RESTORE PERFORMANCE. You are trying desperately to save face by being pedantic and failing. Just stop.

    29. Re:maintenance by sjames · · Score: 1

      I have never needed that option on any system. Perhaps I just got lucky?

      The newer versions of the filesystem do an even better job of not needing to be defragged than ext2.

    30. Re:maintenance by X0563511 · · Score: 1

      Either that or I got unlucky. But it's there, and has a beneficial use. My condition still stands.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    31. Re:maintenance by sjames · · Score: 1

      A performance degradation in an operation that only some people may need to perform infrequently isn't a killer.

      Especially since that defrags only the directories.

    32. Re:maintenance by mattack2 · · Score: 1

      Your car will eventually die if you don't change the oil. (even if you keep adding new oil, due to the sludge.)

      Your hard drive will NOT stop working (at least with some OSes) if you don't defragment it. (The UCSD Pascal disk format did require all files to be contiguous, so you had to Krunch the disk all the time, which defragmented it.. I actually thought it was nice at the time, since it made things really fast.. That is orthogonal to current filesystems requiring or not requiring defragmentation.)

    33. Re:maintenance by CTachyon · · Score: 1

      Since you obviously know that a *file* can be fragmented, obviously you already know that a file doesn't have to be contiguously written.

      Thus, you don't need to defragment it. The directory structure knows that the 'file' is in blocks 1-5, 8, 14.

      As other people pointed out, disk seeks are most assuredly something to avoid on spinning media. But even when seeks are free, as they are on SSD, fragmentation still sucks and you should avoid it like you owe it money. For one, some filesystems use run-length encoding for the list of blocks in a file. Basically, instead of recording "1, 2, 3, 4, 5, 8, 14", they notice the pattern and record "1-5, 8, 14" like you just did in your post. (The ext[234] family doesn't do this, but IIRC some of the post-ext2 up-and-comers use it.) RLE lets you inline more metadata directly in the inode without resorting to indirect blocks, which basically means you get your data with fewer round trips to the disk. (It might save you from needing to read a meta-meta-block to find the meta-blocks that tell you where the blocks are. Instead you can fit all the blocks in one meta-block and skip a round trip.) For two, even filesystems on SSD that don't do RLE still suffer under fragmentation. Unfragmented files make it easy for the kernel I/O scheduler to coalesce those sequential block reads into big, happy multi-block SATA reads when you're streaming through the file. As before that means fragmentation = more round trips to the disk, but it also means fragmentation = spamming the SATA controller with more commands and spamming the CPU with more interrupt handlers for the command completions. (In other words, copying a big fragmented file slows down everything else on the computer, moreso than copying a big un-fragmented file.)

      Disclaimer: I am not a filesystem designer, I just play one on Slashdot.

      --
      Range Voting: preference intensity matters
  8. Yes, all twelve agreed to go out of business by raymorris · · Score: 5, Insightful

    Yep, they've had it since 2004, when all twelve of the drive manufacturers agreed to just sit on it while Western Digital kicked their butt in the marketplace. Nine of them went out of business rather than reveal their secret.

    1. Re:Yes, all twelve agreed to go out of business by Flere+Imsaho · · Score: 1

      Citation? Last time I checked, the largest WD disk available is "only" 3 Tb.

      --
      It gripped her hand gently. 'Regret is for humans,' it said.
    2. Re:Yes, all twelve agreed to go out of business by The+Grim+Reefer · · Score: 1

      Citation? Last time I checked, the largest WD disk available is "only" 3 Tb.

      http://www.newegg.com/Product/Product.aspx?Item=N82E16822236599

    3. Re:Yes, all twelve agreed to go out of business by Conception · · Score: 2

      http://www.wdc.com/en/products/catalog/

      You must have checked last several months ago.

  9. I wonder what the retention reliability is like by msobkow · · Score: 1

    I have to seriously question the retention reliability of a device that requires re-writing multiple tracks at one time.

    The performance impact is obvious as well.

    I think I'll avoid these like the plague until they're proven to be as reliable as older technology.

    --
    I do not fail; I succeed at finding out what does not work.
    1. Re:I wonder what the retention reliability is like by Anonymous Coward · · Score: 0

      100% Agree.

  10. Rewriting multiple tracks everytime I add data? by SeaFox · · Score: 0

    DO NOT WANT

    1. Re:Rewriting multiple tracks everytime I add data? by Anonymous Coward · · Score: 1

      You do not have to re-write multiple tracks each time.

      Firmware adds the data at the end in an unwritten area and marks the old area "to be reclaimed" reclaiming can be done during downtime and is done safely.

      Reclaiming works by reading the data for the other tracks in the shingled block and appending those at the end. Then, once that is verified properly copied, you mark that whole old block as free.

      The only issue there is fragmentation. Need very smart firmware to do reclaiming without introducing fragmentation so reclaim probably best done by the OS. (ok, there is the other issue of overwrite not truly erasing data)

    2. Re:Rewriting multiple tracks everytime I add data? by rubycodez · · Score: 1

      bullshit on "done safely", instead of loss to a single file a power loss or unexpected interuption wil be devastating to the intergrity of an enormous amount of data.

    3. Re:Rewriting multiple tracks everytime I add data? by Anonymous Coward · · Score: 0

      Yes. No one ever thought of that... gotta love armchair engineers.

    4. Re:Rewriting multiple tracks everytime I add data? by fnj · · Score: 1

      Do not want and WILL NOT BUY EVAR.

      It's way, way, way too much of a crippling performance and reliability hit for a laughably miserably tiny capacity gain. 25%? Are you kidding? I'll buy two 4's to get 8. I'll never buy a 5 to replace a 4. Maybe, just possibly, if it gave a 300% capacity gain I might possibly consider it for data where speed and reliability does not matter at all. Hmm, come to think of it, I guess that covers a big fat ZERO percent of my needs. So, no. Just no.

    5. Re:Rewriting multiple tracks everytime I add data? by rubycodez · · Score: 1

      armchair? no, I do data center devops in the real world

  11. Does it (still) make sense ? by boorack · · Score: 2, Interesting

    Except for some corner cases ? Given that Samsung also learned how to stack their NAND flash and CrossBar technology is almost there ? Traditional disks are almost dead at this point. Relatively high price of SSDs is the only thing that keeps them alive and price is going down fast. 4TB 3.5" SSD drives are already available and 2GB 2.5" drives are certainly possible (if SSD controllers are capable of handling such capacities). Any significant breakthrough in sold state storage technology (vNAND, CrossBar, anyone ?) makes SSD advantages only bigger and there seems to be a lot of room for improvement in this pretty much like in HDD technologies 15 years ago. My bet is that SSDs will take over traditional HDDs in all aspects (including price) in less than 5 yars.

    1. Re:Does it (still) make sense ? by slaker · · Score: 2

      Spinning disks are only dead if you have no bulk storage needs, unless you think prices are going to fall through the floor out of the kindness of NAND Flash manufacturers' hearts.

      There's a single chassis in my closet that has 96TB of disks in it. That kind of density is utterly unthinkable on flash memory.

      --
      -- I wanna decide who lives and who dies - Crow T. Robot, MST3K
    2. Re:Does it (still) make sense ? by Anonymous Coward · · Score: 0

      "CrossBar technology is almost there"
      So were FeRAM, MRAM, PCRAM, ...

    3. Re:Does it (still) make sense ? by Anonymous Coward · · Score: 0

      My bet is that SSDs will take over traditional HDDs in all aspects (including price) in less than 5 yars.

      Please do show me where to source SSDs and related controllers and processing elements to run a storage node with 1 exabyte (or more), where 33% of the hardware devices can fail and not only do you not lose any data, but the system happily keeps serving data to the data center.

      Show me where to source these parts for under 20 million dollars, in either now or 5 years from now money.

      Then I will take such a "prediction" seriously.

      Not only would SSDs ramp that price up over a billion, I guess you expect us to plug them all into those non-existent controller devices as well.

    4. Re:Does it (still) make sense ? by Anonymous Coward · · Score: 0

      MRAM has started mass production and so has CrossBar. Eat your words.

    5. Re:Does it (still) make sense ? by LordLimecat · · Score: 2

      Traditional disks are STILL about 10x the capacity and 1/10th the price-per-capacity of SSDs, as they have been since they arrived. Price-per-GB for SSDs has come down, but so has price-per-GB of mechanical drives-- currently you can get a 3TB drive for ~$100, while a 256GB SSD costs around $200-- thats 8x the cost for the SSD.

    6. Re:Does it (still) make sense ? by lgw · · Score: 1

      There are several well-funded start up in the valley making pure-SSD enterprise arrays now, plus several making SSD-fronting-HDD arrays.

      Given that the cost of the physical disks in big box storage is a small fraction of the cost of the unit, SSD-based storage will only be more expensive because EMC/NetApp can get away with charging even more.

      --
      Socialism: a lie told by totalitarians and believed by fools.
    7. Re:Does it (still) make sense ? by Anonymous Coward · · Score: 0

      All of FeRAM, MRAM, PCRAM entered mass production at some point or other. The only one of the bunch that managed to scale to modern process sizes is PCRAM.
      CrossBar has a 1Mbit tech demonstrator done on a 150nm process, which is certainly a good sign but still "2-3 years" (read: half decade or more) from actual mass production.

    8. Re:Does it (still) make sense ? by Trifthen · · Score: 1

      8x the cost, but 100x the performance. There's a reason so many system builders are using an SSD for the boot/OS drive and critical applications, and a regular HD for long-term storage.

      That hybridization is the first step to totally deprecating hard drives, or relegating them to the same fate tape faced so many years ago.

      --
      Read: Rabbit Rue - Free serial nove
    9. Re:Does it (still) make sense ? by rolfwind · · Score: 1

      Traditional disks are STILL about 10x the capacity and 1/10th the price-per-capacity of SSDs, as they have been since they arrived.

      We don't have 10 years of history of SSDs, but we do have of flash which are obviously closely related. 10 years back:
      Slashdot comment system for Drupal

      Flash at around 128MB @$50.

      And HDD at around 160GB @150.

      Today it's flash around 128 @$55.

      And HDD at 3TB @$150.

      1024x increase in flash for the same price point. 18.75 increase in HDD capacity for the same price point.

      I decided to see the halfway point, in 2008:

      Flash at 16GB @ $55

      HDD at 1TB @ $140

      8x growth from flash, paltry 3x from HDD in 5 years.

      Both seem to be slowing but Flash seems like it going to be stronger and the winner eventually.

    10. Re:Does it (still) make sense ? by fnj · · Score: 1

      Reality check. Tape died because it stopped growing in capacity anywhere near fast enough to keep up with disks. Not because it was too slow. That in no way whatever bears on the disk situation now. When and if it ever does, and it just might (since this story makes it clear just how they are scraping the bottom of the barrel and not coming up with anything worthwhile for advancing disk tech), then at that time we can talk about disks dying. Disks are going to far outperform ssd's in GB/$ for a long time to come.

    11. Re:Does it (still) make sense ? by LordLimecat · · Score: 2

      Tape didnt die at all, its right where we left it (in the server room).

      Call me when HDDs come anywhere close to the price / capacity of an LTO5 cartridge (~$30 /~3TB), or their archival life, or their durability; or have anything resembling a modern tape library in terms of media management.

      I dont think tape is going anywhere in terms of archival storage, any time in the near future.

    12. Re:Does it (still) make sense ? by isorox · · Score: 1

      Tape didnt die at all, its right where we left it (in the server room).

      Call me when HDDs come anywhere close to the price / capacity of an LTO5 cartridge (~$30 /~3TB), or their archival life, or their durability; or have anything resembling a modern tape library in terms of media management.

      I dont think tape is going anywhere in terms of archival storage, any time in the near future.

      You're spending $15 for LTO5 tapes?

      You do realise that each tape is 1.5TB don't you.

    13. Re:Does it (still) make sense ? by LordLimecat · · Score: 1

      You do realize that in practice the quoted compression rates (2:1) are not that far off, dont you.

      You can in 90% of use cases fit more than 1.5TB of data on an LTO5 tape. its usually well above 2TB, and closer to 2.5TB.

    14. Re:Does it (still) make sense ? by isorox · · Score: 1

      You do realize that in practice the quoted compression rates (2:1) are not that far off, dont you.

      You can in 90% of use cases fit more than 1.5TB of data on an LTO5 tape. its usually well above 2TB, and closer to 2.5TB.

      Depends entirely what you're storing. My data (video) is already heavily compressed.

      Feel free to compare with drives with something like drivespace installed.

    15. Re:Does it (still) make sense ? by fnj · · Score: 1

      Bingo. Tape compression benefits some users but not most. If you are using that amount of storage on disk, it is usually incompressible video, audio, images, etc. That said, I had no idea LTO had come that far. Nobody I know has been using tape backup for some time now, so I haven't kept up with the tech over the last couple of years.

  12. How do I find out the number of platters? by Chemisor · · Score: 1

    A question: how can I find out the number of platters in a particular hard drive model? Seagate still lists areal density on its web site, but I was unable to find this information for WD. Naturally, Amazon and Newegg never tell you these things. So where can those of us who'd much rather have a single-platter drive find out which ones those are?

    1. Re:How do I find out the number of platters? by WuphonsReach · · Score: 1

      Well, for 2.5" drives, it depends on the "height" of the drive.

      2.5" drives seem to come in (3) sizes. 7mm, 9.5mm and 15mm.

      You're pretty much guaranteed that the 7mm drives are single-platter. There just isn't enough room in there for a 2nd platter along with the requisite spacing.

      Harder to say for the 9.5mm units, but they're probably a mix of single and double platter.

      The 15mm units are going to be almost all double (or triple?) platter.

      Power usage is also a hint. The more platters, the more power the drive consumes to keep those platters spinning. The older 3.5" drives with 4 or 5 platters in them were real power hogs.

      --
      Wolde you bothe eate your cake, and have your cake?
    2. Re:How do I find out the number of platters? by fnj · · Score: 1

      You're probably right about 7mm. HGST has a 1.5TB 3 platter 9.5mm. Samsung has or at least used to have a 500GB 3 platter 9.5mm. You left out 12.5mm; not sure about the platter count there. WD Passport 2TB's have 4 platters in 15mm.

  13. Another mess by gweihir · · Score: 1

    For some workloads these things will create nothing but problems. And all that for a 20% density increase? Sounds quite stupid to me.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    1. Re:Another mess by slaker · · Score: 1

      The current "Green" drives from WD and Seagate already create nothing but problems for certain workloads, but they're extremely appealing for one-off modest-density needs that are probably appropriate to most consumer applications.

      --
      -- I wanna decide who lives and who dies - Crow T. Robot, MST3K
  14. What? NO cartoon? by Anonymous Coward · · Score: 0

    Last time they indroduced new technology for increasing areal density we got a cool cartoon ....
    http://www.youtube.com/watch?v=xb_PyKuI7II

  15. All for the low low price of... by Anonymous Coward · · Score: 0

    All for the low low price of losing your files even harder than before.
    THANKS SEAGATE. Get fuuuucked.

    Friends don't let friends buy Seagate hard drives. Ever.
    Worst drives ever. Never had any brand fail as hard as they do. I have drives hitting 15 years old and still work fine, Seagate drives, every one of them, failed in 2.
    OH BUT SURE, CHEAP DRIVES, AWESOME. Never again. Never again.

    1. Re:All for the low low price of... by damnbunni · · Score: 1

      I have had drives from every manufacturer but one fail in warranty or just out of it, and I've had drives from all manufacturers last for years and years without issues.

      All the hard drive companies have made some good drives and some bad ones.

      (The one that never died prematurely on me was Micropolis. I had their server-grade drives.)

    2. Re:All for the low low price of... by Anonymous Coward · · Score: 0

      Anecdotal. I only had 1 drive fail me, and that was long ago (I think there was Elder's scrolls I or II on it, when it was new) And I think I bought at least one hard drive a year, and lot of them seagate, and I'm pretty sure I use them more than 2 years (currently 2x 2TB (seagate and WD), a 1TB (samsung) and a 400GB (seagate) are plugged), so my conclusion is that nowadays hard drive never ever fail. Right ?

    3. Re:All for the low low price of... by slaker · · Score: 2

      I buy several hundred drives a year and I've consistently had more problems with all non-Enterprise Western Digital product lines than with I had with Seagate, Hitachi or Samsung models. By rough order of preference, I found WD "Blue" drives least reliable, followed by WD Green, followed by Seagate Eco models, followed by WD Black. The most trouble free drives over the last five years or so? Samsung's F-series and Hitachi DeskStars. Goddammitsomuch.

      --
      -- I wanna decide who lives and who dies - Crow T. Robot, MST3K
    4. Re:All for the low low price of... by fnj · · Score: 1

      Never had a Micropolis SCSI 5.25" or 3.5" fail either. They were built to last forever. OTOH, I distinctly remember paying in the neighborhood of $2000 for 300's and then again for 1000's. That's MB, not GB, BTW.

    5. Re:All for the low low price of... by jones_supa · · Score: 1

      I guess there was some significant trend of failures with Maxtor disks. People said that service departments could see statistically higher returns of Maxtor brand. I never saw the numbers though. I personally had one 40GB IDE Maxtor disk and it was rock solid, one of my best 3.5" HDDs.

  16. If you value your data by letherial · · Score: 0

    Dont buy drives that have alot of space. Cramming these bits in make the HDD work harder and hotter, therefore they break quicker.

    Example, my new 1TB lasted 1 year and half, my 500GB has last about 7 years now....

    Seagate idea sounds retarded from the top down.

    1. Re:If you value your data by jedidiah · · Score: 1

      I have a 1.5TB drive that's been in service for nearly 5 years.

      I usually retire drives not because of failures or disk errors but due to capacity. I've seen drives from 500G up to 4TB and hammered drives of all sizes.

      Capacity doesn't really impact longevity.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    2. Re:If you value your data by fustakrakich · · Score: 1

      I usually retire drives (to the storage room) when they become full. By then they're obsolete anyway. Anybody know the shelf life of a hard drive? Should I run them like the air conditioner every so often?

      --
      “He’s not deformed, he’s just drunk!”
    3. Re:If you value your data by fnj · · Score: 1

      I can't match your duration individually, but I have a huge failure-free aggregate duration of 2 and 3TB drives.

      I have a total of 22 Samsung HD204UI 2TB 5400rpm (the last 4 were actually Seagate rebrands, but same design). Power-on hours 7574, 8090, 8098, 8592, 8609, 8690, 8691, 9330, 10,041, 10,105, 11,612, 11,612, 11,676, 11,676, 16,730, 17,270, 17276, 17,769, 17,769, 18663, 18663, 19650.

      Also 7 Hitachi/Toshiba (another buyout) 3TB 7200rpm. POH 2133, 2761, 2766, 2925, 3533, 3598, the 7th one is not online to check at the moment, but not because of failure.

      None of the 29 have any reassigned or failed sectors or any other indication of any problem to date, including SMART readouts. All of them have operated 24x7 for multiple periods of multiple months at a time. Purchases were spread over the last 7 years if memory serves.

      OTOH I just recently had a 1TB WD current production RE4 Enterprise drive fail catastrophically after something like only 1000 hours.

    4. Re:If you value your data by fnj · · Score: 1

      I have had car air conditioners sit for periods of up to a YEAR without being turned on, and never had one fail yet. I had one car for 18 years and never once even started the engine from december through april of every year. The car including the AC still worked fine until rear ended and totaled in the 18th year. Another car sat from 1999 to this year in the driveway. Finally somebody bought it, and he says the AC still works fine. So much for that old wives' tale.

      I don't think hard drives degrade in storage. I've had them sit for multiple years and then put them back into service without any problem. I have some SCSIs that haven't been run at all since the 90s that I might try just for fun and to see if those old files include anything good.

    5. Re:If you value your data by Blaskowicz · · Score: 1

      I heard the AC thing is about mushrooms growing in it, which could somehow contaminate you or whatever, so you had to run the AC once in a while (even in winter) just to vent the air out.
      About HDDs there's a saying the bearing fluid can solidify, after about a decade. So maybe you need to spin archival HDDs once every three years or whatever abritrary time you choose.

    6. Re:If you value your data by fnj · · Score: 1

      If you don't want crap growing in there, always turn off the AC well before you're going to shut the car off, and leave the blower running until only warm air comes out. Just shutting the car off with the AC on, or one second after turning the AC off, is gonna make it smell like hell the next time you start the car due to stuff growing in the condensation.

      Interesting story about oil solidifying or congealing. I'm not buying it until I observe it happen.

  17. No way in hell by Cyfun · · Score: 1

    Given Seagate's track record with forays into fancy new hard disk technologies, let me be the first to say NO WAY IN HELL AM I GOING TO TRY THIS... until at least a second or third gen has the bugs worked out.

    I was fool enough to try their terabyte drives with their nifty vertically-oriented bit techniques. Went through six brand new hard drives in one month. SIX! Two drives RMAed three times. Finally told Seagate that I'm not going to be their guinea pig anymore, and that I'm going to shelve the drives and to call me when they iron the bugs out. That was over 2 years ago and I haven't heard a peep.

    --
    In Soviet Russia, dot slashes YOU!
    1. Re:No way in hell by Cyfun · · Score: 1

      Also, "track record," no pun intended. xD

      --
      In Soviet Russia, dot slashes YOU!
  18. Shipping? by 8tim8 · · Score: 1

    >Seagate has begun shipping hard drives based on a new technology dubbed Shingled Magnetic Recording....We should see the first examples of SMR next year, when Seagate intends to introduce a 5TB drive with 1.25TB per platter.

    These two things don't match.

  19. Poor compromise for only small capacity increase by JoeyRox · · Score: 5, Insightful

    The read-modify-write penalty for overwriting existing data in-place is huge (even with attempts to minimize it with smart block mapping) and not worth the very minor increase in areal density. It's a bad sign that the storage industry was forced to adopt this because it means better encoding technologies are further off in the future than originally anticipated. Brick wall.

  20. First things First by PopeRatzo · · Score: 1

    I'm glad to see that unlike some other well-known technical blogs, Slashdot has pushed aside new revelations about our Police State to pass along important product roll-out press releases from the biggest tech companies.

    --
    You are welcome on my lawn.
  21. Backporting the Tech by Anonymous Coward · · Score: 0

    In reply to all the "do not want" and "not until it's proven" comments, I'm just worried about them backporting the technology to existing (smaller capacity) drives to reduce the number of different fabrication techniques in use before fully exploring it's use in the field. I might be a limited early adopter on this technology but I'm not comfortable switching to it outright.

  22. Re:Poor compromise for only small capacity increas by erice · · Score: 1

    The read-modify-write penalty for overwriting existing data in-place is huge (even with attempts to minimize it with smart block mapping) and not worth the very minor increase in areal density. It's a bad sign that the storage industry was forced to adopt this because it means better encoding technologies are further off in the future than originally anticipated. Brick wall.

    If it means that rotating media no longer has a write performance advantage over flash, then it is a very poor compromise indeed.

  23. Re:Poor compromise for only small capacity increas by Rockoon · · Score: 1

    If it means that rotating media no longer has a write performance advantage over flash, then it is a very poor compromise indeed.

    What is this, 2008?

    Rotating media hasnt been competitive in write performance for quite awhile now.

    --
    "His name was James Damore."
  24. The summary doesn't mention by guruevi · · Score: 1

    But if you edit a single point in the first layers of the hard drive, you have to re-write your entire hard drive down? What happens when the power goes out before you're done writing? Does it rewrite entire tracks or just the magnetic domains that are compromised? How does it even know certain tracks have valid data or will it require a proprietary driver to make it work?

    --
    Custom electronics and digital signage for your business: www.evcircuits.com
    1. Re:The summary doesn't mention by Bengie · · Score: 1

      Just use a COW FS and set your cluster size to that of whatever these "shingle groups" are. :-)

      Or ZFS

    2. Re:The summary doesn't mention by Anonymous Coward · · Score: 0

      1. No. The current implementations does 3-track rings, so worst case it has to rewrite 2 tracks.
      2. It finishes writing.
      3. Err, what?
      4. TRIM.

  25. Wait, I'm not sure I want this... by Virtucon · · Score: 1

    I may not want this because I see TV commercials all the time that say that I can get Shingles already if I've had the Chicken Pox. Supposedly there's a med that I can use to get rid of it or prevent it.

    --
    Harrison's Postulate - "For every action there is an equal and opposite criticism"
  26. 5 1/4 HD's by 7bit · · Score: 2

    This is all well and good, but couldn't just one manufacturer afford to set aside one measly manufacturing line for making 5 1/4 inch Hard Drives again?

    Here me out. Now that they are up to 1TB per platter with current tech on 3.5 inch drives just imagine what they could fit into a 5 1/4 inch drive now!!

    I know I wouldn't be the only one willing to shell out bux for one of those, providing they used all that space intelligently: With Data Spaces that large it would pretty much be a requirement to include built in internal Mirroring RAID of some sort between the platters, or at least provide the option, for data integrity and protection and longevity of the unit.

    I've been salivating over that dream for years now.

    1. Re:5 1/4 HD's by mattack2 · · Score: 1

      Here me out. Now that they are up to 1TB per platter with current tech on 3.5 inch drives just imagine what they could fit into a 5 1/4 inch drive now!!

      Umm, around 9.1 TB? ((Simply did 5.25" drive area / 3.5" drive area) * 4 TB)

    2. Re:5 1/4 HD's by lgw · · Score: 3, Informative

      There was once a "bigfoot" brand of HDDs that did just that. It was a disaster. It's unlikely anyone will try that again. You can just put 2 3.5" drive in about the same volume in your case, so why not do that?

      --
      Socialism: a lie told by totalitarians and believed by fools.
    3. Re:5 1/4 HD's by Anonymous Coward · · Score: 5, Informative

      As I understand it, one of the big reasons for moving away from 5.25" toward 3.5" and smaller is because of the need for faster and faster seek and read/write times. They had already made the bus path from head to CPU pretty fast, after that, the low hanging fruit for further gains was to simply make the disk(s) spin faster. After all, you can't possibly send bits on the wire faster than they spin past the read head. Problem is, spinning the larger 5.25" platters faster a) sucks back a lot more power than their smaller brethren. b) more power means more heat==shorter MTBF c) increased vibration increases read/write errors. (a problem exacerbated by ever-smaller magnetic domains)

      Another reason of course is that the smaller package just makes so much sense at the end user level as well. Smaller portable consumer devices, more drives per rack etc

      Finally; selling 5.25" drives in a world of 3.5" and smaller has been tried. "Quantum Bigfoot"

    4. Re:5 1/4 HD's by I'm+New+Around+Here · · Score: 2

      One of the Compaq mid-tower lines used those drives. Quantum Bigfoot. I worked at Computer City at the time, and every time one of those towers came in for service, it was for a bad drive. It got to the point where we would see a customer carrying one up to the counter and we would tell him/her what the problem was before they even set it down.

      The really sad part was that for the first few months, we had to replace the defective drive with the same type because that's what the warranty dictated. After those customer came back in with a second loss of data, we convinced the manager to inform Compaq we would be switching to a different drive as replacement. Nothing gets results like a screaming repeat customer to the service counter.

      I always wondered if the problem was that the size of the platters just made them too unstable, or if the manufacturing process had flaws.

      --
      If you think I voted for Trump because of this post, you're wrong. I voted for Dr. Jill Stein of the Green Party. Again.
    5. Re:5 1/4 HD's by Anonymous Coward · · Score: 0

      Here me out. Now that they are up to 1TB per platter with current tech on 3.5 inch drives just imagine what they could fit into a 5 1/4 inch drive now!!

      Umm, around 9.1 TB? ((Simply did 5.25" drive area / 3.5" drive area) * 4 TB)

      Keep in mind that this is someone who used the wrong spelling of "hear." It was a bit much to expect him to be able to do simple math.

    6. Re:5 1/4 HD's by Khyber · · Score: 2

      That's why we say fuck magnetic media and cram SSD tech into that 5.25 form factor.

      And make it a hot-swap bay.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    7. Re:5 1/4 HD's by Joce640k · · Score: 1

      Here me out.

      Wear you out?

      --
      No sig today...
    8. Re:5 1/4 HD's by 7bit · · Score: 1

      Here me out. Now that they are up to 1TB per platter with current tech on 3.5 inch drives just imagine what they could fit into a 5 1/4 inch drive now!!

      Umm, around 9.1 TB? ((Simply did 5.25" drive area / 3.5" drive area) * 4 TB)

      Nice. That plus however many more platters you could fit into it considering the 5.25 bay is deeper than a 3.5 inch HD.

      Also, thanks for not making an issue of my misspelling one word. I'd been up since the previous day working and am also not feeling well, so I'm not going to feel bad about one obvious misspelling. ;)

    9. Re:5 1/4 HD's by 7bit · · Score: 1

      Keep in mind that this is someone who used the wrong spelling of "hear." It was a bit much to expect him to be able to do simple math.

      LOL! And I'll keep in mind Mr. Coward that it was too much for you to notice the obvious fact that his equation missed the greater depth of 5.25 inch bays, meaning the figure is incorrect since it doesn't account for enough platters. :P It's fun making fun of people instead of actually being constructive isn't it?

    10. Re:5 1/4 HD's by 7bit · · Score: 2

      Here me out.

      Wear you out?

      Well, that depends. Send me a pic. ;) (Yes, I know I misspelled "Hear". :P)

    11. Re:5 1/4 HD's by znark · · Score: 1

      One of the Compaq mid-tower lines used those drives. Quantum Bigfoot. I worked at Computer City at the time, and every time one of those towers came in for service, it was for a bad drive. [...] I always wondered if the problem was that the size of the platters just made them too unstable, or if the manufacturing process had flaws.

      Quantum BigFoots (some early models) had a known data corruption problem which could be prevented (altogether, or from getting worse) by applying a firmware uprage from the revision A01.02 to A01.03, or later. Alas, a later version of the firmware cannot fix a drive which already has corrupted areas on its platter: it can only prevent further damage.

    12. Re:5 1/4 HD's by Anonymous Coward · · Score: 0

      Here me out.

      Non-native speaker, or poor education?

    13. Re:5 1/4 HD's by tlhIngan · · Score: 1

      This is all well and good, but couldn't just one manufacturer afford to set aside one measly manufacturing line for making 5 1/4 inch Hard Drives again?

      Here me out. Now that they are up to 1TB per platter with current tech on 3.5 inch drives just imagine what they could fit into a 5 1/4 inch drive now!!

      The problem is not volume - modern hard drives are shedding platters when they can add more platters fairly easily (most 1TB drives are now single platter, and there's space for 3-4 platters like time from yore).

      The problem is how fast do you want your data? Going back to 5 1/4" drives mean you need to slow down the rotational velocity because of heat concerns (most of the heat a hard drive generates is friction, and internal stresses (remember how "52x" CD-ROM drives would sometimes shatter the disc? Same thing happens for hard drives - you'd need thicker, stronger platters and that means more rotational weight). It's why 10K hard drives use 2" or smaller platters (basically platters you would put in a 2.5" hard drive) and have extensive heatsinking.

      Going from the large 5 1/4" to 3 1/2" formfactors also enabled us to go from 3600 RPM to 4200, 5400, and 7200 RPM easily.

      That's why we say fuck magnetic media and cram SSD tech into that 5.25 form factor.

      You can, but the primary driver is the cost of the flash media - most SSDs have plenty of space for additional flash chips (especially at 128GB/256GB) - it's just the cost of populating it up is prohibitive. Even in the 2.5" form factor, most of the volume is air.

      The added volume of a 5 1/4" enclosure would just mean you enable $50,000 SSDs that can store 100+TB. If space was a problem, you wouldn't find "thin" 5/7mm SSDs common - you'd see them using a full 9.5mm height (most SSDs are empty air).

      Adding lower cost lower density chips doesn't give you much either - there are sweet spots in pricing and smaller chips can be more expensive due to lower volume production compared to higher density ones. Plus you'd need a controller able to handle those extra chips - modern day SSDs use 16+ channel controllers to be able to hit 16 chips simultaneously - you could add extra control lines and gang up the chips (the flash is designed to share one controller amongst several chips - it's how most flash is arranged these days in that each package has several dies). Problem is that you then create the potential where it's possible to severely cut SSD performance if you end up doing a series of accesses that end up not using the controllers in parallel (which is how SSDs get their speed).

    14. Re:5 1/4 HD's by bhiestand · · Score: 1

      Maybe I got one with fixed firmware, but I absolutely loved my 4.3 GB. I used it for a few years before giving it to a family member for a linux server. It saw almost 10 years of continuous operation without fail.

      I didn't even know problems with Bigfoot were a thing until I read your post...

      --
      SWM seeks new sig for a brief fling
    15. Re:5 1/4 HD's by toddestan · · Score: 1

      I don't think speed would be an issue, as I would use the drive as a secondary for mass storage of (mostly) media files, and have a faster primary drive as the boot drive that holds all my programs. Nowadays, with many people doing just that with a large 3.5" HDD and a smaller SSD, I would think the market for such a beast would be even greater.

    16. Re:5 1/4 HD's by bingoUV · · Score: 1

      You can put 2 3.5" drives in a 5.25" slot by breaking at least one hdd. So only one works. There is also the problem of cooling if you stuff hardware too close to each other.

      That's why cooler master sells a 4 in 3 module ( http://www.coolermaster.com/product/Detail/case/case-accessories/4-in-3-device-module.html ). Makes sense, even though it might appear they could have fit one more hard drive sideways in the same space if they removed the fan. Maybe more. But not a good idea. Because small amounts of heat add up to high temperature in absence of cooling.

      Hard drives spaced comfortably don't need dedicated cooling, typically.

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
  27. I'll pass for now. by Anonymous Coward · · Score: 0

    Might as well call it what it is, the Seagate Random Number Generator v1.0.

  28. Re:Poor compromise for only small capacity increas by Bengie · · Score: 1

    You mean like the bargain-bin SSDs that have almost 500MB/s of write performance.

  29. Power failure by Anonymous Coward · · Score: 1

    What happens if you suddenly lose power?

    1. Re:Power failure by Bengie · · Score: 1

      That's undefined behavior. Don't let it happen.

  30. Re:Poor compromise for only small capacity increas by Anonymous Coward · · Score: 0

    yes, 500MB/s write performance when you're writing a large string of 0s.

    Not all makers give you correct write speeds on the SSDs. Figure anything that claims over 400 is really about half of the claim.

  31. because they are ALL hiding their 50TB, AC says by raymorris · · Score: 1

    4TB, I believe. AC's conspiracy theory is that all the drive companies have had 50TB drives they've been hiding. Since most of them have been driven out of the hard drive business, I guess they were so committed to the conspiracy that they'd rather fold than get rich selling huge drives.

    Such is the logic of the left-wing nutjob conspiracy theorists. Damn the NSA for making them right about something. Even a broken clock is right twice a day.

    1. Re:because they are ALL hiding their 50TB, AC says by Anonymous Coward · · Score: 0

      Don't blame this nuttery on us liberals. Clearly the guy is insane. But, Oil companies having the technology to make a car go on pure water? Let me tell you about that...

    2. Re:because they are ALL hiding their 50TB, AC says by gagol · · Score: 1

      Mine does, nevermind the huge batteries in the trailer for electrolysis...

      --
      Tomorrow is another day...
    3. Re:because they are ALL hiding their 50TB, AC says by Anonymous Coward · · Score: 0

      Not sure why the "left-wing" part has to be in there.

  32. Re:Poor compromise for only small capacity increas by Anonymous Coward · · Score: 0

    ... until they run out of pre-erased blocks and drop an order of magnitude.

  33. Both size and manufacturing by dutchwhizzman · · Score: 3

    They made perfectly good 5.25" Hard Drives for quite a few years before they went with the 3.5" and now the 2.5" format. The size of the platters isn't really the problem at the lower data densities that drives had back then. When you move to higher densities and "smaller bits" on the media, the bigger platters tend to vary in exact placement a bit more, both due to the distance they could have from the spindle and the basic fact that almost all solid materials expand as they get warmer. This means that you can't get spindle speeds as high with big drives, or you have to invest in a lot of technology and materials to keep the whole thing stable. That would make the drives too expensive, resulting in a price/performance trade-off that put the bigfoots at the wrong side of the curve. Also, because you can't counter all of the effects completely, data density would still be lower on the bigger platters than on the small ones. You could by some really crappy hard drives in the era of the bigfoots, but their capacity got superseded by reliable 3.5" drives in less than 12 months at the same price point, so Quantum figured it was no use investing in the product line pretty fast after they introduced them.

    --
    I was promised a flying car. Where is my flying car?
    1. Re:Both size and manufacturing by metaforest · · Score: 1

      Bit/domain sizes are considerably smaller than the thermal distortion + the mechanical distortion of the platter, and stylus. They have been since the late 80's (hint if it has a voice-coil stylus, it is dynamically positioning, earlier drives used stepper motors, and could not correct for distortions, so tracks had to be rather wide, even when the bitrates were considerably higher).

      It doesn't matter (much) because positioning of the stylus is done using a closed loop system that dynamically detects where the head is relative to the desired track. Since the thermal and mechanical distortions happen over fairly long intervals (seconds to minutes) keeping lock is fairly easy. There are issues: The closed-loop servo data is written to the platters during final testing, and for almost all drive types( now) is NOT rewritable. In the early days a lot of SCSI drives were capable of rewriting their servo data. Very few if any IDE and later drives could do this. Initially it was because IDE drive manufactures didn't want to write and test the firmware for this function. Later is became infeasible due to advances in servo system implementations that used specialized waveforms that the onboard controller, for cost and implementation reasons could not perform. Special signals are provided by the test/verification harness to generate the servo data, and the drive-controller passes this on to the write amplifier. At this time unit specific tuning params (because every drive is mechanically unique) are encoded and stored on the drive and in the controller.

      Once that servo data is corrupted, tracks and sometimes entire sections of the drive cannot be read or written ever again, because there are some practical limits imposed on the closed-loop system's feedback loop and its ability to acquire and maintain servo-lock during seeks.

      One easy way for tracking data to become corrupted is noise in the power supply which can cause and early or late write into a physical data block. If that write stomps on the sync region, then that block and possibly the next block will become unreadable. If it hits the track sync region it may cause the entire track to be inaccessible. Well designed drives have a lot of safety monitoring to prevent writes during potentially risky operating conditions, but none of that is perfect. These losses are far more common than head crashes, which can also corrupt the servo data.

      There is a hell of a lot going on in these drives. At times I am astounded that they work as well as they do. Platter size is more of a mfg. cost and marketing issue than a technical issue, and has been for a long time.

  34. Heat-assisted magnetic recording by jones_supa · · Score: 1

    So I guess HAMR is still in the labs.

    1. Re:Heat-assisted magnetic recording by TeknoHog · · Score: 2

      So I guess HAMR is still in the labs.

      Stop - HAMR time. Isn't this basically what was used in Minidisc?

      --
      Escher was the first MC and Giger invented the HR department.
  35. think outside the box by twisteddk · · Score: 1

    You are ofcourse correct in that current methods of manufacturing is geared towards miniturization. But think outside the box for a minute, or rather, think INSIDE the box. Given the size available in a 5 1/4", you can easily fit say, 6-8 2,5" drives. Give a little room for some NAND chips and a raidcontroller, and you can actually have a pretty decent piece of storage tech available in a single 5 1/4" unit.

    IMO, I think the reason for NOT doing this is the fact that the market for this type of technology is too small. Desktop sales are at an all time low, and tablets are all flash memory. External drives are usually 3,5", and laptops exclusively 2,5". High end servers and businesses are using SAN, which makes your identifiable market small servers and high end home PCs. The first is dying due to virtualization, and the second is probably not large enough to warrant a new development.

    As your last paragraph pretty much points out, the technology just doesnt have sufficient lifespan to warrant production.

    And given that same knowledge, that size will increase regardless of this new SMR technology, I predict this technology wont live long.....

    --
    --- To err is human... Am I more human than most ?
  36. Re:Poor compromise for only small capacity increas by Bengie · · Score: 1

    Many can now sustain 400MB/s+ for several GB, even when near capacity and in a used state, and with no compression.

  37. That's the stupident thing Seagate has done! by Anonymous Coward · · Score: 0

    Unless this is only a test and Seagate plans to create 100TB drives with this technology, it's completely worthless to be used as a normal hard drive. It sounds like you can only use it to back up data since the rest of the tracks have to be rewritten after a write operation is done. That would be fine for backup if the capacity was HUGE. But for barely being larger than the 4TB traditional HDD, this invention is just stupid!

  38. Thinking this is for servers, etc. by Anonymous Coward · · Score: 0

    I'm seeing Netflix not caring about write performance much on their movie servers, they only need to write the data once, and then reading a few hundred thousand times. Likewise, other databases where data is never overwritten, simply appended to (Facebook, gmail, etc.).

    For home users, the only thing I can think of is if they are made into a hybrid drive. The flash write cache might well overwhelm the spinning write speed penalty. You will end up using more Watts, since there will be more spinning, but the noticeable performance for normal use cases could be kept close to the SSD level. Heavy duty writes will overwhelm the cache, but then they might write to whole 'shingle sectors' or whatever they are called and not incur the penalty, thus keeping it two HDD levels.

    Obviously, this isn't the most obvious way of making drives bigger, but sometimes you have to just do what you can.

  39. because "evil business people hiding the good stuf by raymorris · · Score: 1

    Because "those evil business people are hiding the good stuff" is a left-wing belief. Not necessarily wing I guess, did you notice in the campaign Obama motivated the center-left by saying "corporations" every sixth word.

    Right wing nutjobs believe entirely different nonsense.