Date: Tue, 5 Dec 2017 07:37:01 -0800 (PST) From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> To: Dustin Wenz <dustinwenz@ebureau.com> Cc: Paul Vixie <paul@redbarn.org>, FreeBSD virtualization <freebsd-virtualization@freebsd.org> Subject: Re: Storage overhead on zvols Message-ID: <201712051537.vB5Fb1dv052052@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <32BA4687-AB70-4370-A9BA-EF4F66BF69A6@ebureau.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I'm not using ZFS in my VMs for data integrity (the host already provides that); it's mainly for the easy creation and management of filesystems, and the ability to do snapshots for rollback and replication. Some of my deployments have hundreds of filesystems in an organized hierarchy, with delegated permissions and automated snapshots, send/recvs, and clones for various operations. I architect things in such a way that I have 1 VM used as a NAS that runs zfs and allows all that nice functionality then all the other VM's run with ufs + nfs mounts. And can actually run a VM with no local disk over iPxe netbooting. I find this very flexible and minimally impacting. Though it does make a single point of failure, that could be cured with some redundancy. -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201712051537.vB5Fb1dv052052>