I know that it is very early to discuss this toppic but the thing is, I can't imagine why nobody has implemented such a feature...
I think most of you are knowing FlexRAID. It's really cool but it has some limitations in dependability. A fact is that a snapshot RAID won't be able to rebuild all data if there were file changes since the last snapshot
For my understanding Liquesce stands between the NTFS presentation of the pysical drives and the windows kernel presentation as one disk. This should be exactly the point where a checksum generation would make sence. Let me describe why...
1.) It is the point where you know which files are landing on which disk.
2.) It recognizes every filechange (if the physical disks are hidden) so the parity could be generated live.
This is how RAIDZ of zfs`basicly works and from the theoretical point of view you only need the largest disk for parity to have a complete one disk fault tollerance. The problem with RAIDZ is, that it isn't possible to add or remove disks easily from the
pool. You always have to backup the data and rebuild the RAIDZ.
If only one disk would be used for parity it should be easy to rebuild the parity if a disk is added or removed. And again... Liquesce should recognize if something has changed.
The nowerdays multicore cpus should have no problem with the parity calculation and I'm not sure but I think a data communication is already done over the cpu in Liquesce so instead of writing to one disk it would be writing on two disks (data and parity).
So why not add a checksum to an additional drive? (it sounds so easy ;) ) It would be a super flexible pseudo RAID :-D
By the way... I think there are some products which are doing what I discribed but they are only NAS implementations like drobo and others. Why not learning windows the same features?