public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Randy Bush <randy@psg.com>
Cc: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] zfs raidz2 expansion
Date: Fri, 23 May 2025 10:50:24 +0200	[thread overview]
Message-ID: <e8c83c5c-0923-4ced-8c5d-bd371afdf926@proxmox.com> (raw)
In-Reply-To: <m2ecwgjr34.wl-randy@psg.com>

On  2025-05-22  23:03, Randy Bush wrote:
>>> so, can i specify a second pool to be replication target, as i
>>> suggested in
>>>>> as we do full replication, we could just create a new pool for
>>>>> replocation and call it a day.
>>>
>>> i do not see an attribute for relocation pool in storage.cfg
> 
>> Where does the quote here come from? Did I miss an email in this thread?
> 
> all the above are from my keyboard on this thread

ah sorry. I was too blind yesterday to see that in your first email.

There is no option to replicate a full ZFS pool to another.

So, you have a current pool with one raidz2 VDEV made up of 4x 2TB disks.

What kind of pool layout/sitation do you want to have in the end?

Because if you have another set of 4x 2TB disks, you can just expand the 
pool with another raidz2 VDEV, without expanding the current VDEV you have.

Right now, `zpool status` will show you something like:

pool
   raidz2-0
     disk0
     disk1
     disk2
     disk3

If you add another VDEV, the pool could have the following layout:

pool
   raidz2-0
     disk0
     disk1
     disk2
     disk3
   raidz2-1
     disk4
     disk5
     disk6
     disk7

If you want to create a new pool, then things will be a bit more 
complicated, as you would need to create a new storage config for it as 
well, Move-Disk all the disks over to it. If you have a cluster and use 
the VM replication feature, that new pool must be present on the other 
nodes as well and you will have to remove the replication jobs before 
you move the disks to the new pool and then re-create them once all VM 
disks are on the new pool.



_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user


  reply	other threads:[~2025-05-23  8:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20  1:24 Randy Bush
2025-05-20  7:05 ` Aaron Lauterer
2025-05-20 17:21   ` Randy Bush
2025-05-22 13:23     ` Aaron Lauterer
2025-05-22 21:03       ` Randy Bush
2025-05-23  8:50         ` Aaron Lauterer [this message]
2025-05-23 18:17           ` Randy Bush
2025-05-26  7:38             ` Aaron Lauterer

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=e8c83c5c-0923-4ced-8c5d-bd371afdf926@proxmox.com \
    --to=a.lauterer@proxmox.com \
    --cc=pve-user@lists.proxmox.com \
    --cc=randy@psg.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal