Hello Donny,
I also am familiar with ZFS and am not familiar with VDO at all. I took a
quick look at VDO, but it's something to look into. It sounds like VDO is
more of a layer above RAID, whereas I'm looking for something to implement
the RAID. Apart from all of the other features provided by
Hello Darrell,
I can report back that after making all of the config changes you noted,
deployment completed and hosted engine is up and running! Hyperconverged
Ovirt 4.2 on ZFS! Thank you sir!
On Thu, Nov 15, 2018 at 6:09 PM Darrell Budic
wrote:
> I did this in the past and didn’t have any
Well, personally I know ZFS and I don’t know VDO. Going to have to check it out
now that I know it exists, sounds interesting to have it at the dm layer. I
don’t use it exclusively either, but have been finding it useful for
compression.
What is your source for the statement that COW
Why not just use the built in stuff like VDO. What benefits does ZFS bring
for the use case?
For most vm based workloads ZFS is the opposite of ideal over the lifecycle
of a VM. COW filesystems have downsides over time.
On Thu, Nov 15, 2018 at 6:09 PM Darrell Budic
wrote:
> I did this in the
I did this in the past and didn’t have any trouble with gluster/ZFS, but 4.2.x
probably does more validation.
I recommend these settings on your zfs volumes, I set mine at the root(v0 here)
and let them inherit:
required:
v0xattr sa local
v0acltype
5 matches
Mail list logo
