Proxmox lxc samba server11/24/2023 in some ways you can think of it like strip size for raid. You need to read up on zfs recordsize, what it is, and when you change it. Same when you create /foo/media/tv and foo/media/music as they will both inherit their properties from /foo/media So whatever zfs settings (compression, recordsize, etc) you have for /foo/media will be inherited to. 'zfs create /foo/media/movies' will create the dataset within media. music under media you have a few choices. So if you create /foo/media, but decide you want. You can also create datasets within datasets just like folders or even symbolic links. The more you put in it, the bigger it gets. When you create it it takes essentially takes no space. My understanding is (and hopefully someone will let us know if this is correct or not.) datasets are essentially ballooning virtual disk in a way that are just symbolically linked. When you create the pool/dataset foo/bar, proxmox defaults to mounting to pool to /foo and the datasets linked under that. This statement right here tells me you need to read up some more on what zfs. My problem is to not create another filesystem over the zfs, but I do not think that this is the case here anyway. The lxc/VM doesn't need to know zfs is involved and even if it did it wouldn't even care. The lxc/VM will just see a folder where it can put stuff really. Mount points essentially are just symbolic mounts that are place in the VM/lxc config file as ’mp#:/proxmox/foo,/mnt/bar’ or thereabouts. And the lxc will “see” the mount points as zfs, correct? And then mount the numerous paths in there. Then I create a lxc container of choice (some Linux). How many data sets you create is up to you, what you're end goal is, and your hardware. You'll create the pool and data sets in proxmox. So I do create my structure in the zfs of the Proxmox(different datasets as per media type, etc). Is it really that easy?: zfs create raidz1/media/musicĬhown -R my_very_secure_user:my_very_secure_user raidz1/media/music Create some structure (not fully found below). I am thinking of making something like that. My question is: is using the pve host for samba server (and nfs) a good idea? Any drawbacks? Or I should consider it as an old school samba server and live my life with one VM less :) I have plenty of storage where I can move the data and re-create the raidz1 with some better structure - so this is not a problem. So I have been reading that I can use the pve host itself to do the job - remove a layer that way. It is not a complicated share at all - just one big drive for samba share & couple of nfs shares. I am passing it to a open media vault VM. The raidz1 is used 99% for media storage - for the PlexVM. And I do have 3 disks in raidz1 for storage. Also, I have a ZFS mirror of 2 SSDs for the VMs & the containers OS. The pve itself is installed on a hardware mirror disks.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |