News for hackers. Stuff that matters.
Re:Backblaze hard drive reliability stats for Q3 2016 by mahyarm on Tuesday November 15, 2016 @03:27PM (#12961893)
How about the stupid idea of making a minimum block size be a multiple of the number of platters to write to. The block is divided evenly amongst all platters and are always at the same parallel track/sector. That way you can multiply the read/write speeds to be a function of the number of platters.

Instead of 50-100MB/s, you can get 4-8x the speed in large linear transfers, which helps get dead racks back up faster and would work quite well in backblaze's backup model.

Your block sizes will be huge, but I think in backblaze's case that doesn't really matter so much.

Re:Backblaze hard drive reliability stats for Q3 2016 by eye2sky on Tuesday November 15, 2016 @05:11PM (#12962769)
You cannot read from multiple platters in parallel. When you are aligned to read from a certain track on a certain side of a platter, you are not necessarily aligned on all platters. This head mechanism is not accurate enough for that.
Re:Backblaze hard drive reliability stats for Q3 2016 by rzzzt on Wednesday November 16, 2016 @01:36AM (#12964986)
Google's paper on datacenter hard drives addresses this point -- it's easier to do this and other tricks with a set of disks than attempting it within the confines of a single drive.

https://news.ycombinator.com/item?id=11172876