Can you just yank out a 2TB drive and put in a 3TB drive (and continue one by one as the system tells you it's safe to do so) when they become available to increase your storage without downtime on those? You can on a Drobo - without resorting to any command line or configuration - just watching blinkenlights.

Obviously how? I only count 6 - though I guess if we assume the bottom of the rack(which we can't see) is identical to the one next to it, we could guess that there might be another pod under there....

Unless they changed something since they published their howto - your BZZT has it's facts wrong....

Backblaze pods use 45 drives in each pod.

Each pod is made up of 3 Raid-6 volumes.

Each Raid-6 volume is made up of 15 drives (13 drives + 2 parity)

There are two parity disks for every 13 data disks. That's higher than you might want to go in a normal enterprise setting, but as they also handle redundancy between pods, it's an acceptable tradeoff in their case that I'm sure they've calcluated out quite well given drive sizes and rebuild times and all that......

Watch the video - it's not.

Without reformatting - you can pull out the smallest drive (well really, any drive in most cases, but replacing the smallest makes the most sense) and drop in a bigger one. Then you wait for it to automatically rebuild /migrate data to obtain redundancy again - and then you can swap out the next drive to grow your system. The only catch is the initial format - the drobo fakes out the block device size to the maximum size you ever expect to use, at the expense of boot time (for the drobo).

The drobo seems to do block-level raid - each allocation block (or whatever they happen to call it) can have it's own raid level and mirrored to a block on another block on another drive - independely, so you can migrate and raid between different sized drives with a minimum of wasted space. (It will only waste what it can't mirror somehow)

If you drop in a 1TB drive and a 500GB drive, it will give you 500GB of space. If you swap the 500GB drive with a 2TB drive, it will show you 1TB of space. If you then drop in a second 3TB in a spare slot, it will show you 3TB of space after it finishes shuffling things around - watch the demo video - it's actually quite clever and different.

Regaular old raid arrays just don't resize like that.
ZFS can with some manipulations.......

That's why you have a hotspare & an external spare to pop in when you get a drive failure - and the monitoring to back it up and fire off alarms when a drive fails - because in Raid5, as soon as one drive fails, you are exposed (and with TB SATA drives, rebuild times are long.). Raid6 is a better option - same footprint as Raid5 with a hotspare and you have some elbow room for rebuild times because you have double redundancy.

Also remember that drives bought at the same time tend to fail at the same time.

The bottom line though is - make sure you have backups of your important data - raid is not backup no matter how you slice it.

Coraid has sata over ethernet gizmos..... that's not really new. I think they are relatively cheap as well - that's their market niche.

As to having it available to all your computers - while technically true - this is potentially dangerous - your common filesystems (ntfs, ext3, fat,e tc, HFS+, ZFS, etc) are not cluster filesystems - they are designed for a single machine to mount at a time. What's worse is some won't recognize if you DO manage to mount the same filesystem to two machines, and you'll end up corrupting data before you realize what's happened.

If you want access to the same data from multiple computers - you want something that exports a network filesystem - NFS, CIFS, AFS, or whatever (or all of the above I guess....).

I'll second that - while I don't use a drobo - it's on the purchase list.

I'm highly technically competent - I use an opensolaris fileserver with ZFS and some terabyte drives - and sure, I can expand it and do all kinds of cool things - but in the end, I could get the same features I get there (the ones I actually use) out of a drobo, with less hassle.

With my fileserver I have to know a bunch of stuff about how to manipulate it to expand it... with a Drobo, you have to watch some blinkenlights and just pop in bigger drives when you need to grow. It locks dives when you shouldn't remove them, and is dead simple to use. From all my research, it's unparalleled in the ease of use department for joe average.

Yes - exactly. The "Return unopened goods at any time" is a marketing tool (and a good one for the consumer) - but not something they are required to do by law. That policy has aboslutely nothing to do with the "fit for purposes sold" legal end of things - and the two are often mixed up at big box stores when people return broken things.

The store would be free to say "all sales are final" and not accept returns (other than broken items) - they do that in many stores here where I live - but they also unpack and test most electronic stuff before you leave the store to avoid dealing with broken returns, which could be fraudulent (and really saves everyone time and money in the long run)

Indeed complicated... but if I buy a box with software in it in the store, and you, the sales guy, tell me it will do X, and it really WONT do X, no EULA should protect you - the software vendor is probably fine - but if the store selling the box of software LIED about it's capabilities to make the sale - that's fraudulent, and illegal in most places. In Canada, for instance, you'd have to accept a return and give a FULL refund if the product was not fit for the purposes sold.

It's free... no money exchanged hands.. no purchase, no right to any damages.

There might be a convoluted case in there somewhere - but it's nothing like the parent article - which is basically standard fit-for-purposes-sold law being applied. Selling something that dosn't do what you say it does is fraud.

If you didn't sell it you have no problems - this is just the same old, very good piece of consumer law that says you can't fraudulently sell goods. You can't LIE about what the thing does. You can't sell me an old plasma TV and tell me it's HD if it's not HD. .. that's fraud. You can't sell me a toaster that doesn't toast bread - that's fraudulent. Things need to be fit for the purposes sold. THis is to keep salesmen honest - because the flip-side of hte coin is that all sales are generallly final (in-store policies generally accept returns these days everywhere, but that's not because they were required by law, that's marketing strategy).

I have the right to sell you a toaster and I didn't lie to you about it's capabilities before the sale, and as long as it actually works when you unbox it, our business is generally done. I can count my sale as profit and don't have to accept any kind of return from you.

When google wants them to stop, they'll be hearing from lawyers........ not just finding that google changed their page layout.

Right - which is perfectly acceptable.

Before they can have their way with it, yes - but they can use it internally - just as I can make derived works from GPL code and use them however I want, myself or in my company. What I can't do is distribute it, sell it, etc... but if I base my employers in-house time-tracking system on some GPL code - the company is under no usage restriction whatsoever, and is under no obligation to share those changes with anyone else.

If they do want to distribute the stuff outside their organisation, they'll have to do so under the terms of the GPL - other than that scenario, they can do whatever they want internally.