What was really amusing was when I had a Mac LC II. It had an 80MB hard drive, and I later purchased a ZIP drive to accompany it. So, I had a 80MB hard drive, and 100MB floppies.
My Mac SE shipped with a 30MB drive in it. When it died, I replaced it with a 200M drive, which has proven to be more than I'll ever need for that SE.
When that drive dies (which might be a long time, since I don't turn that computer on that much anymore), my plan is to use one of my SCSI Zip-250 drives as its boot device. As long as I remember to eject the media at shutdown, it should last a very long time. (Yes, I know all about click-of-death. It never hit me, and I've been using Zip drives for a long time. I still use a SCSI Zip-100 drive to boot my Kurzweil synthesizer, since it's much much faster than using its built-in floppy drive.
It's kind of crazy when you think about it. When I first got my computer back in 1995, it had Windows 95 on it, and had a 4GB hard drive. The salesman at Sears told me "4GB is all you will EVER need!"
And back in 1995, that was all you needed. And FWIW, I never came close to filling the 2GB drive that my old Win95 PC used.
Backblaze used Seagate consumer grade external backup drives for their data centers and pulled them out of the external case. These drives are not designed for data center applications. They used enterprise grade drives from hitachi and WD. It was a really unfair study. All the Seagate drives where also over a year out of their documented life span of 6 years.
Actually, most of their drives are consumer-grade. They use very few Enterprise drives. The economics of their particular usage pattern is such that it is cheaper to replace dead drives than to pay more for a bit more reliability. See also
http://www.theregister.co.uk/2014/02/17/backblaze_how_not_to_evaluate_disk_reliability/
The study is fine, but you have to realize that their usage pattern - massive arrays of file storage running 24/7, with drives failing and being replaced all the time - is very different from what an individual will have on his personal systems.
Seagate used to offer 5 year warranties to consumers. Now they offer only 1 and 2 year warranties. ... On a personal note, every single seagate drive I have ever owned has died or shown near death (below 30% on SMART health data) within the first 12 months of ownership.
It really depends on the model.
My experience has been that no consumer-grade drive is very reliable these days. The older ones (that are now over 7 years old) seem to be working great, but the newer ones all seem to fail after 2-3 years. On the other hand, enterprise-class drives do seem to last longer, and the warranties bear that out.
For example the
Seagate NAS still advertizes a 1M hour MTBF and has a 3-year warranty. Their
Enterprise Capacity drives are advertising 1.4M hour MTBF and 5 year warranty.
They cost more than the cheaper Desktop models, but not a whole lot more. FWIW, these are what I buy when I build new systems or assemble an external drive.
Now the NAS manufacturers need to remove the artificial volume size limit they place on arrays. Currently, you can't have a single volume larger than 16TB on any of the name brand NAS's (Synology, QNAP, Drobo, etc.), even though any modern OS supports volumes in the exabyte range.
That's going to depend greatly on the file system you format the volume with. According to
Wikipedia, ext3 goes up to 32TB, ext4 goes up to 1EB (as of version 1.42). XFS goes up to 8EB on IRIX, but the Linux implementation tops out a 64TB. ZFS goes up to a whopping 256ZB. Macintosh Extended (HFS+) goes up to 8EB. NTFS has a theoretical limit of 16EB, but current implementations top out at 256TB.
I would assume that any NAS's limit is going to be based on their choice of file system and its drivers. If you want to roll your own network server by putting hard drives in a computer and running server software, your limits will be based entirely on the capabilities of your RAID hardware/software and the file system you use to format the volumes.
True, you're going to hit the ext4 volume size limit of 16TB. Since it uses a 32-bit processor as well, any other file system would be limited to the same limits.
A 32-bit processor doesn't force you to use a 32-bit block number. The C language has had standard support for 64-bit integers since 1999 (e.g. the "long long" type and <stdint.h>'s uint64_t typedef.) It would be pretty bad (and lazy) for a modern implementation to use a type like "int" or "long" for block numbers, which may be different sizes on different CPU architectures.
I would estimate never. We've had 1 TB hard drives for a few years now and I haven't heard anyone complain about running out of space on them. Further, as we accelerate into the cloud, individuals requirements for storage space is going to continue going down. ...
For personal use, perhaps, but there are other applications. For instance, where I work, doing software development, a full build of our product is about 3GB, and it can balloon to about 75GB if full debugging information is generated. Every developer typically works with 3-4 builds at once, and some people have dozens. So we're looking at between 12 and 300GB per user on our file servers. And then couple that with the fact that deleted files don't immediately free up their storage thanks to NetApp's
Snapshot hourly-backup software. It doesn't take a lot of users in this environment to require tens of TB of storage for everybody to work comfortably.
Now in contrast, my home server (a Mac mini) containing files for the three members of my family consumes about 350GB for everything, including the OS, applications, two large music collections (to sync to our iPods) and a few VirtualBox hard drive images. I predict that the 1.5TB I've got (two 750G hard drives) will probably be enough to last until the drives die (or we decide to upgrade the computer.) I use larger drives for backup (two 2TB drives for cloning the server, and a 3TB drive for Time Machine) but that's because they store a history of revisions of files, not just the latest ones we use every day. Again, I think they won't fill up before we end up having to replace them due to age or failure.