thnx Justin for an accurate example figure on this! (58hours rebuild time on 16 2TBHD with one HD failing, not two I suppose that was) again I would emphasize to go for maximum (affordable) brick security (raid6/raidz2 or better) and gluster to expand the available space and/or replication on a high level (i.e. replicate the whole dataset to a second side of server, either for redundancy or access speed) There are different aspects that make up the rebuild time of a failed raid: - raid level - disk speed - controller performance - active read/write usage of the system tests (because the above mentioned aspects are difficult to bring into a simple math formula) and considering a proper SLA surely helps. though a "hi boss, all data lost" isn't really an option, is it? build stronger to last longer. have a good one ;-) Bernhard On 02.01.2014, at 18:06, Justin Dossey <jbd@xxxxxxxxxxxxx> wrote: to completing rebuilds faster at the cost of performance. One data point from me: my last 16-2T-SATA RAID-6 rebuild took about 58 hours to complete. > _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
