On 05/10/2010 03:13 PM, Jeff Garzik wrote:
If I understand the vinzvault project correctly, it will be used to
provide block-level storage to a node, somewhat similar to Amazon's
Elastic Block Storage (EBS).
For that case, each block device will likely have only a single writer:
the kernel/FUSE to which vinzvault is providing storage.
Not only a single writer, then, but no sharing (even for read) between
that writer and anyone else. That certainly does make things simpler.
Is there any plan to implement an overlay/COW scheme as part of
vinzvault so that nodes can share a base object read-only and store
private changes in a per-instance object, or will we rely on the block
layer for that?