--- Begin Message ---
No, this dataset not added as “dir” - it’s mounted as ZFS filesystem inside
container so it’s not a file. And about proxmox provided zfs backend - I
understand that it’s better to just use existing option, but there is use cases
where existing mechanism isn’t usable - for example when you need to mount
dataset inside container only, to make files on it visible only inside
container.
Best regards,
Konstantin
> 10 мая 2023 г., в 12:52, Roland <devz...@web.de> написал(а):
>
> what about adding zfs datasets as a general type of storage?
>
> currently, you need to create a dataset manually and add that as type
> "dir" to proxmox, to be able to use file backed instead of zvol backed VMs
>
> that feels ugly.
>
>> Am 10.05.23 um 02:08 schrieb Konstantin Filippov:
>> As we know, ProxMox have only three possible "categories" of mount points:
>> ProxMox storage provider supplied, block device and bind mount. I've
>> prepared a little patch for pve-container package which adds a fourth
>> "category" named "zfs" - so with this patch it's possible to add such ZFS
>> dataset into container config in a form "mpN: <ZFS pool name>/<dataset
>> path>,<mount path>". This new type can be useful in some cases - for
>> instance when we need to mount ZFS dataset in the container but need to keep
>> this dataset not mounted on the host.
>>
>> Konstantin Filippov (1):
>> Adding new mount point type named 'zfs' to let configure a ZFS dataset
>> as mount point for LXC container
>>
>> src/PVE/LXC.pm | 4 ++++
>> src/PVE/LXC/Config.pm | 3 ++-
>> 2 files changed, 6 insertions(+), 1 deletion(-)
>>
--- End Message ---
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
