LVM + mounted LV into dir or Directory ext4?

[kriznik]

Hello I'm wondering about what's better solution (or what are main differencies) between:

1. creating LVMThin + LV mount into the dir
2. create Directory, ext4 (UI)

?

my usecase is;
proxmox installed on HW raid1 SSD's (1TB)
datastorage HW HDD raid10 (40TB)

so in proxmox I have sda and sdb, sda contains host + local-lvm as by default
I want to have sdb mainly as datastorage, which I will share via smb via lxc. As well I want to have it as nfs from host - eg. I want to have it mounted in the folder somewhere so I can export dir for nfs.

Maybe I dont fully understand difference of Directory vs. LVMThin. From UI LVMthin cannot be mounted as dir, but I can do it from shell indeed.
Are those similar/same?

 

[Daukil]

Up this question. My usecase is a bit different (thinclient)

• 1x small 16GB SSD with only local for my PVE host only
• 1x 4TB SSD for (shared) data of/for LXC’s and (only/mainly) LXC rootfs disks

Now I have the same two options basically as OP:


1. Make 2 partitions: One LVM-Thin for disk images of the CT‘s + 1 partition as directory (xfs/ext4) and directly bind mount that dir to any lxc

2. Make a thinpool with one vg and (at least) 2 lv‘s: x number of lv‘s for each ct-rootfs (as in the first method) and additionally z numbers of lv‘s for data storage: „/media“ „/photos“ etc. with xfs/ext4 as file system on that manually created lv‘s and then bind mount those lv‘s to the PVE host to be able to share that host directory on each lxc.

What is „better“/most commonly used and why is it.

Would be great to find a definite answer as Google is not helping much after searching for a long time.

 

[Impact]

Why not ZFS? It can do all of that and the storage is shared among all things. I also find management a lot simpler and you save space due to compression, etc.