all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-user@lists.proxmox.com, Bryan Fields <Bryan@bryanfields.net>
Subject: Re: [PVE-User] Shared ZFS storage that supports LXC's
Date: Tue, 31 Oct 2023 10:20:33 +0100	[thread overview]
Message-ID: <b9c5eb38-10cf-41eb-801d-dd1e801a7b61@proxmox.com> (raw)
In-Reply-To: <8bbed148-012b-cd0f-cf44-49f4e891464d@bryanfields.net>

Hi,

Am 29.10.23 um 11:16 schrieb Bryan Fields:
> I do  get a warning in proxmox when moving a VM into it or making a
> snapshot:
> Warning: volblocksize (8192) is much less than the minimum allocation
> unit (32768), which wastes at least 75% of space. To reduce wasted space,
> use a larger volblocksize (32768 is recommended), fewer dRAID data disks
> per group, or smaller sector size (ashift).
> 
> I can't find exactly what this is referring to or how to fix it.  Does
> anyone have insight into this message?
> 

You can set the default blocksize in the storage configuration in
Proxmox VE, either in the UI (Block Size option) or via 'pvesm set <your
storage ID> --blocksize 32K'. Note that this will only apply to newly
allocated or moved volumes and not change existing ones.

> With the LXC's I've found they don't support this backend storage.  (and
> it's not mentioned in the docs) I assume this is do to them needing a
> filesystem, not a block device.  My option here would be to run NFS for
> shared storage, but this loses the ability to do snapshots (a must
> have).  LVM would work, but it's not able to be shared.
> 

It is documented via the content types (only 'images' for ZFS over
iSCSI, but not 'rootdir'):

https://pve.proxmox.com/pve-docs/chapter-pvesm.html#_common_storage_propertieshttps://pve.proxmox.com/pve-docs/chapter-pvesm.html#storage_zfs

From a quick glance, the only storage type that fits your needs, i.e.
snapshots, shared and support for 'rootdir' content type is Ceph/RBD.
Everything else requires workarounds and won't be fully integrated.

Best Regards,
Fiona




      reply	other threads:[~2023-10-31  9:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-29 10:16 Bryan Fields
2023-10-31  9:20 ` Fiona Ebner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b9c5eb38-10cf-41eb-801d-dd1e801a7b61@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=Bryan@bryanfields.net \
    --cc=pve-user@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal