5 ms·
I have to imagine that by making Storage Pods 1.0 through 6.0, maybe they "encouraged" Dell (and other manufacturers) that this particular 60+ hard drive server
by dragontamer 5y ago
I have to imagine that by making Storage Pods 1.0 through 6.0, maybe they "encouraged" Dell (and other manufacturers) that this particular 60+ hard drive server was a good idea.
And now that multiple "storage pod-like" systems exist in the marketplace (not just Dell, but also Supermicro) selling 60-bay or 90-bay 3.5" Hard drive storage servers in 4U rack form factors, there's not much reason to build their own?
At least, that's my assumption. After all, if the server chassis is a commodity now (and it absolutely is), no point making custom small runs to make a hypothetical Storage Pod 7. Economies of scale is too big a benefit (worst case scenario: its now Dell's or Supermicro's problem rather than Backblaze's).
EDIT: I admit that I don't really work in IT, I'm just a programmer. So I don't really know how popular 4U / ~60 HDD servers were before Backblaze Storage Pod 1.0
- walrus01 5y ago3U and 4U x86 whitebox servers designed for any standard 12"x13" motherboard, where the entire front panel was hotswap 3.5" HDD bays were already a thing many, many years before backblaze existed. What wasn't really a thing was servers with hotswap HDD trays on both ends (like the supermicros) and things that were designed with vertical hard drives dropped down from a top-opening lid to achieve even higher density.
- briffle 5y agoThe Sun X4500 "thumper" server had 48 drives, if I remember correctly, and came out in 2006ish. It had hot-swap SATA disks (up to 512GB disks initially!) and was actually pretty cool and forward thinking https://web.archive.org/web/20061128164442/http://www.sun.com/servers/x64/x4500/index.xml https://web.archive.org/web/20061128164442/http://www.sun.co...
- zrail 5y agoIIRC the company I was at at the time had a set of thumpers for something. Maybe a SAN? They were incredibly cool for the time.
- dekhn 5y agoI remember when I worked in a company that was a netapp shop, and in 2007, they sent one of the ZFS developers and andy bechtolsheim to sell us thumper and ZFS. The developer and I had a spirited discussion of the relative merits of having volume management built into the filesystem. At the time I advised my company to skip the storage servers (which were overdesigned IMHO, but were unquestionably stout hardware) but that ZFS was an interesting filesystem to explore.
- mattst88 5y agoHah! That was the system my small university IT department bought to act as a storage server. Actually they bought 2, with one to act as a backup. Unfortunately for them, no one knew how to administrate Solaris, so they... installed Windows. No idea if they actually succeeded in doing anything useful with the systems.
- midasuni 5y agoBought three with 1TB drives and ZFS. Wasn’t cheap. Hardware was great, but no linux/zfs support meant we didn’t stick with it. A couple of years later we had standardised on supermicros with a similar density and ran linux on them. Sun lost a fair amount of money from us (7 figures) by choosing not to embrace linux.
- notyourday 5y agoThat's not the backblaze design. The backblaze design is that the drives are individually hot-swappable without a tray. 60 commodity SATA drives that can be removed and serviced individually while a 4U server continues to operate normally is pretty amazing.
- walrus01 5y agothat's what I said, the backblaze design is: > things that were designed with vertical hard drives dropped down from a top-opening lid to achieve even higher density. the backblaze storage pod system and some 3rd party derived designs have the SATA/power ports on PCBs facing upwards, mounted at bottom interior of rack chassis, and 3.5" HDDs mounted vertically down into the system.
- pram 5y agoThey existed for other applications, like NetApp and the ZFS Appliance. Long, long before 2009.
- bluedino 5y agoYou'd think they could build a ARM-powered, credit card sized controller for them with a disk breakout card and network IO. PC motherboard and full-sized cards seem like overkill.
- dragontamer 5y agoThey're running a fair bit of math (probably Reed Solomon matrix multiplications for error correction) over all the data accesses. Given the bandwidth of 60+ hard drives (150MB/s per hard drive x 60 == 9GB/s in/out), I'm pretty sure you need a decent CPU just to handle the PCIe traffic. At least PCIe 3.0 x16, just for the hard drives. And then another x16 for network connections (multiple PHY for Fiber in/out that can handle that 9GB/s to a variety of switches). We're looking at PCIe 3.0 x32 just for HDDs and Networking. Throw down a NVMe-cache or other stuff and I'm not seeing any kind of small system working out here. --------- Then the math comes in: matrix multiplications over every bit of data to verify checksums and reed-solomon error correction starts to get expensive. Maybe if you had an FPGA or some kind of specialist DSP (lol GPUs maybe, since they're good at matrix multiplication), you can handle the bandwidth. But it seems nontrivial to me. Server CPU seems to be a cheap and simple answer: get the large number of PCIe I/O lanes plus a beefy CPU to handle the calculations. Maybe a cheap CPU with many I/O lanes going to a GPU / FPGA / ASIC for the error checking math, but... specialized chips cost money. I don't think a cheap low-power CPU would be powerful enough to perform real-time error correction calculations over 9GBps of data. -------- We can leave Backblaze's workload and think about typical SAN or NAS workloads too. More I/O is needed if you add NVMe storage to cache hard drive reads/writes, tons of RAM is needed if you plan to dedup.
- dangerboysteve 5y agoThe company which manufactures the metal cases created a spinoff company called 45Drives which sells commercially supported pods.
- notyourday 5y agoThey are fantastic.
- deleted 5y ago[deleted]