From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] 'asymmetrix storage' and migration...
Date: Thu, 15 Jul 2021 14:56:50 +0200 [thread overview]
Message-ID: <1626353683.posa6ve2a8.astroid@nora.none> (raw)
In-Reply-To: <20210715124856.GC3399@sv.lnf.it>
On July 15, 2021 2:48 pm, Marco Gaiarin wrote:
>
> I'm a bit puzzled.
>
>
> A little 'ZFS' cluster, with two asymmetrical nodes; second node is
> there only, just in case, to run some little VMs (PBX, firewall, ...).
>
> First node have a second RAIDZ volume called 'rpool-data', that does
> not exist on second node; eg, storage.conf is:
>
> dir: local
> path /var/lib/vz
> content iso,vztmpl,backup
>
> zfspool: local-zfs
> pool rpool/data
> content images,rootdir
> sparse 1
>
> zfspool: rpool-data
> pool rpool-data
> content images,rootdir
> mountpoint /rpool-data
> sparse 1
>
> Clearly on node 2 'rpool-data' have a question mark.
yes, because you didn't tell PVE that this storage is only available on
node 1
> [...]
> Why migration does not work, even if there's no disks in 'rpool-data'?
because PVE can't know that this storage is not supposed to be checked
if you don't tell it ;)
> Thre's some way to 'fake' an 'rpool-data' on the second node, only to
> have PVE not to complain?
you just need to set the list of nodes where the storage 'rpool-data'
exists in storage.cfg (via the GUI/API/pvesm).
next prev parent reply other threads:[~2021-07-15 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 12:48 Marco Gaiarin
2021-07-15 12:55 ` Aaron Lauterer
2021-07-15 12:56 ` Fabian Grünbichler [this message]
2021-07-15 13:23 ` Marco Gaiarin
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=1626353683.posa6ve2a8.astroid@nora.none \
--to=f.gruenbichler@proxmox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox