News for hackers. Stuff that matters.
[deleted]
Re:Sun engineer responds to the Backblaze "Petabytes on a bu... by jacquesm on Thursday September 03, 2009 @03:17PM (#803261)
> Given the reliability info he cites, the fact that backblaze is still in business must mean their usage-to-storage ratio is small.

No, it probably means that they get their reliability at a different level, such as simply storing the data on a number of machines. Systems like glusterfs make this completely transparant.

Re:Sun engineer responds to the Backblaze "Petabytes on a bu... by abyssknight on Thursday September 03, 2009 @03:38PM (#803327)
Gluster is broken. Hadoop is pretty proven, but I haven't heard of single, non-academic Gluster deployment that worked. From personal experience I can honestly say that software cost us several customers, and caused a support nightmare for a good month before we bought a SAN instead.
Re:Sun engineer responds to the Backblaze "Petabytes on a bu... by jacquesm on Thursday September 03, 2009 @04:03PM (#803391)
> Gluster is broken

Agreed, but I do know a few situations where it is being used, the 'stack' has been undressed to the minimum and tested to the hilt before deployment.

Still, I would not risk my company on it. I've been a big fan of their architecture from pretty much day 1, but so far they seem to be feature oriented and not stability oriented.

Re:Sun engineer responds to the Backblaze "Petabytes on a bu... by bbgm on Thursday September 03, 2009 @07:42PM (#803853)
At least a couple of pharma companies actively use Gluster. Haven't used it myself, but have heard some stories (not positive) about the stability
Re:Sun engineer responds to the Backblaze "Petabytes on a bu... by notaddicted on Thursday September 03, 2009 @03:39PM (#803329)
( ahhh I deleted my post before I saw the response )

From the numbers he cited I got the impression that the drives they are using would fail 3+ times more often than enterprise drives (lower MTTF + speced at low temps). The cost of replacing the drives (even if they are 1/2 the price) would make the system uneconomical.

Also: because of their case design (non-hot-swappable) the cost of human replacement is higher too.

Thus they must have a low usage rate to have a low failure rate for their system to make business sense.

Re:Sun engineer responds to the Backblaze "Petabytes on a bu... by jacquesm on Thursday September 03, 2009 @03:53PM (#803367)
I think their use case is sufficiently a-typical to get away with this.

They're primarily write-only, only when a customer retrieves their data does stuff get read.

If they spin down the drives when the volume is not being accessed the mttf for a single drive goes up a lot, possibly beyond the point where it matters.

Re:Sun engineer responds to the Backblaze "Petabytes on a bu... by mattmcknight on Thursday September 03, 2009 @05:58PM (#803659)
That made me think of MAID (and COPAN), which is decent approach.

http://www.copansystems.com/

Re:Sun engineer responds to the Backblaze "Petabytes on a bu... by jrg on Friday September 04, 2009 @06:09AM (#804571)
Floor loading (and rack size) is a problem with their 'very big box of disks'.

That, and the fact that the company seems to be struggling to get sales.

Re:Sun engineer responds to the Backblaze "Petabytes on a bu... by rbanffy on Thursday September 03, 2009 @06:23PM (#803705)
Given proper redundancy and a adequately read/write unbalance, it's safe to power-down drives during read-heavy cycles and only power them up when you have some redundant data to write.

But you will have to manage the cycles for redundancy, lifetime and power savings. The software to do it must be really clever.

Re:Sun engineer responds to the Backblaze "Petabytes on a bu... by duskwuff on Saturday September 05, 2009 @12:49AM (#806214)
Or even to power down the entire pod if the data on it is quiescent. If you managed the fill and aging properly, this wouldn't even be hard to do -- as a backup service, they're write-heavy, which gives them a lot of flexibility that other applications don't have.