Hi John,
to add a technical reason: SAS and SATA have a different sector format.
With SAS drives the sectors are formatted with 520 Bytes, leaving 8 sectors with 64 'Extra-Bytes' for stuff like checksums used e.g. for media scrubbing (data verification). SATA drives are formatted with 512 Bytes/sector (or 4K/s) and use a different protection scheme. Can't combine the two in a RG or even in an aggregate, therefore no SAS/SATA-Pool aggregate possible.
Anyway, you'll get more IOPS/$ with flash, so I don't see a SAS/SATA combination in the future. Also the SSDs take random load off of the disks, so putting them on SAS instead of SSDs doesn't eliminate the rotational/head latency and would get you only a relatively minor improvement. If you'll ask me, in a few years it'll probably be SSD/SATA disks (best capacity/$ & best IOPS/$) with SAS disks being squashed out in between them.
Sebastian
On 3/11/2014 4:28 PM, Michael Bergman wrote:
John Stoffel wrote:
Now I'm entertaining the silly idea of just using a mix of SAS and SATA drives in a flash pool instead. Get *some* of the advantages, but lots cheaper pricing. Esp using those big fat slow 4Tb drives in the dual drive sleds. Front them with a bunch of SAS disks and it should do quite nicely.
Not so nicely I think...
God knows there shouldn't be any technical reason this can't work, it's just a matter of moving blocks from one raidgroup in an aggregate to another.
Well, the problem is basically that if you put spinning disks in that/those RGs which are FlashPool, they will get thrashed so badly it will just make them melt and latency will go through the roof anyway There's no point, just run the system with the FAS box and som FlashCahce in it, as much as you can afford -- it will work better
/M _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters