[tahoe-dev] [tahoe-lafs] #913: Support running a storage node per drive easily

tahoe-lafs trac at allmydata.org
Tue Jan 19 02:54:54 UTC 2010

#913: Support running a storage node per drive easily
 Reporter:  davidsarah   |           Owner:  nobody   
     Type:  enhancement  |          Status:  new      
 Priority:  major        |       Milestone:  undecided
Component:  unknown      |         Version:  1.5.0    
 Keywords:  usability    |   Launchpad_bug:           

Comment(by qwasty):

 Zooko: Don't forget to automate all that, or it will be inaccessible to
 people like me who are not sysadmins.

 Also, would it be better to fill all nodes to the same percentage of
 capacity? For example, smaller drives are probably older and less
 reliable. If you have enough data to spread out evenly amongst all the
 drives by filling them all to exactly 90% capacity, that would mean that
 comparatively less data would be stored on smaller, presumably older and
 less reliable drives.

 It would also have the effect of nearly guaranteeing that the larger, and
 presumably newer and more reliable drives would have enough excess
 capacity to host the data regenerated from a failure of one of the smaller

 So, instead of reporting absolute capacities, which can become meaningless
 relative to the massive new drives in the pool, maybe it would be better
 to report percent remaining capacity? For example, does it really matter
 if there's 2 MB left on an old 16 MB flash drive, if there's 2 TB left on
 a modern drive? That 2 MB is a lot for that flash drive, but not for the
 modern drive. If they report percentages instead, you can tell which
 drives are pulling their own weight.

 From there, I assume Tahoe already makes sure that significant losses can
 be regenerated with the erasure coding methods that Tahoe uses.

Ticket URL: <http://allmydata.org/trac/tahoe/ticket/913#comment:8>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid

More information about the tahoe-dev mailing list