I will once I do my build. My plan is to do a minimal build, test various configurations over a period of weeks or months, adding components after I've established a baseline. I plan to try both Proxmox/KVM and FreeBSD/Bhyve. But the more I can figure out in advance about how to configure them...
Nope, not a database, lots of large text, csv, and media files. Multiple similar versions of them too. Which is why I want to use deduplication and big blocks.
Hmmm.. or maybe maybe I could use a different linux filesystem (maybe even ZFS) that uses larger blocks. I really want to use large blocks for this (64kb would be ideal). And I thought ntfs was 4kb by default too.
Ah ok, that is a good thing to be mindful of. Is there anything that would stop me from using the same block size on everything?
Oh, wait I see. Ext4 has a max of 4kb and Windows, 64kb. With 4kb blocks deduplication doesn't make much sense for me.
It looks to me like there is no way to have...
Thanks!
I thought about having Dropbox on the host and then unison syncing the files with guests, but doesn't that just add one more layer of reading/writing data and create a third copy of the data?
I'm not specifically married to Dropbox, but I like having my files synced across multiple...
@LnxBil : Because it is not recommended to put Dropbox on a network drive (although some people do, and instructions for it can be found).
@guletz: I was just doing some more reading about deduplication, and according my my calculations 2GB RAM should be enough to cover dedup on 800 GB data...
Ok, since my Dropbox is over 500GB and it changes very frequently, that's probably not a good idea. File-level deduplication sounds great, but can it be done across zvols with different file system types (in my case, NTFS and Ext4)?
I am planning to use several virtual machines that will all use the same Dropbox account, and I want to use the deduplication abilities of ZFS to minimize wasted disk space. I also want the drobox data to be on a separate physical device from the OSs so that they do not take up read/write...
And what about copying files between VMs? Do these need to be cached in the host? I ask because VirtrualBox makes huge temp files on my C drive when I try to copy from a VM to a different third drive.
Yes, that is my plan. Depending on how many VDEVs they end up having, I might split it further, because the fact that loss of a single VDEV kills the pool scares me and I'd like to compartmentalize the risk.
Thanks for the reply! I think I was misunderstanding where the snapshots are located. My plan is to have at least two separate pools though. I'll probably ask a question about snapshot storage at some point, but that's for another day.
How much of an effect does the speed of the boot device have on performance of KVM and ZFS under Proxmox? My hunch is that once KVM and ZFS are started, they shouldn't need to access the drive they are installed on very often (except for ZFS writing snapshots), at least as long as I have...
I like that idea a lot. The two gamers, one tower setup from the earlier video looks like what I want, except for instead of two gamers, I have a work desk and a play desk. I currently use unRaid for my home media server, and I do really like it. However, the idea of using a ZFS pool to store...
Hmmm.. Virtualbox doesnt have the greatest performance though, I'd really like to be as close to "bare metal" as possible. I want some form of Linux as my host, but I'd rather not have any GUI in the host OS in order to save resources. I also don't want Linux audio to touch my sound. I want no...
Hi all, this is my first post here, and I hope it's OK that I'm posting a generic request for advice instead of posting a specific problem. I'm not a Proxmox user yet, but it does sound like a good solution for my purposes based on what I have read so far.
With AMD's Zen around the corner, I am...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.