What Stoiko said.
Just be mindful that it will add another mirrored pair but wont balance so if your pool is already half full it will mostly only use the new pair until they all are at the same amount of free space. So, if it's speed you're looking for it wont necessarily help
@jim.bond.9862 I wasn't trying to offend, just making sure the correct info was out there.
Separate pool is a good idea as it allows you to move the storage to another host easily.
Pretty sure Jim is wrong. You can add VDEVs of any size and they will be incorporated into the pool. eg. 2x 500GB mirrors and you add 2x 2tb mirrors does indeed equal 2.5tb.
Access is where it gets weird, ZFS normally does round robin for access but obviously the smallest one is going to fill...
Udo is suggesting running it in a VM not a container which is what LXC is. AFAIK it's difficult to get docker to run properly inside of an unprivileged container.
First, you haven't actually said what sort of caching you're going for, read or write.
Browsing/searching a media library isn't a...
I run it with a less privileged account not as root but the main reason is that I want to leverage ZFS for my bind mounts. I haven't investigated doing it from within a VM then iscsi to a volume but i think that's a little ugly.
Hey
When you say lxc with docker what do you mean? docker running under an lxc container? they aren't the same thing.
What is the OS formatted as? If it's ZFS then proxmox only supports using the full disk, ie. you wont be able to use part of it to speed up your pool. I highly advise ZFS for...
So you just want to have the VM use each disk as an individual filesystem rather than having an image?
Well that's easy then, simply passthrough the raw disks to the VM and manage it all there. The VM will have normal access to them so you can partition/combine them through mergerFS...
I'm not totally sure what you're trying to do so I'm gonna take two stabs at figuring it out. It's obviously unsupported though.
1. In the storage tab in the GUI simply add the partition/pool you want as a directory. Set the content to whatever you want it to be eg. disk image, iso etc. Then...
Go to the nodes disks page and initialise the old xen disks. Then you will be able to set them up as you see fit eg. ZFS mirror for the 4tb disks
Or do it all from the command line with sgdisk or something like that
Problem is you can't clone an arbitrary snapshot. You can only clone the current snapshot. You'd need to rollback to the snapshot you want to then clone it in your latter scenario.
No problem. Perhaps you could run something like duplicati to backup your VMs to a local SMB share on the host. I know it's not a proper snapshot.
It's a shame that you don't seem to be able to create a clone of a VM by picking a specific snapshot. Presumably possible on ZFS.
The benefit for...
You noticed ~60MB/s difference in SMB across kernel versions? Something is terribly misconfigured if that's the case. Perhaps driver issues?
Also, if he is copying to the VMs virtual disk then it still may be caching policies.
I have never had a problem in flooding gigabit usually between 105...
You would have to do it within the VM rather than on the host.
As mentioned above, VMs get a zvol which is a virtual block device created from a file. It's not a normal filesystem. Snapshots of the zvol are there for rollback purposes and aren't directly browseable.
Virtio drivers work great for windows 10 for me. I usually use SCSI virtio disks so make sure you have the virtio drivers iso available at install.
I haven't run dozens of windows 10 images so I'm not sure about how well KSM works but it will work that same way across all KVM based solutions...
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.