virtualization:proxmox:resizepvedata
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| virtualization:proxmox:resizepvedata [2026/04/08 11:29] – old revision restored (2026/04/06 11:38) 185.115.109.210 | virtualization:proxmox:resizepvedata [2026/04/08 14:50] (current) – old revision restored (2026/01/12 06:37) 123.20.77.92 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Resizing PVE Data ====== | ====== Resizing PVE Data ====== | ||
| - | whoever | + | Whoever |
| Any of the above three solutions would make this entry obsolete for the most part. Alas that is not the reality that we suffer. | Any of the above three solutions would make this entry obsolete for the most part. Alas that is not the reality that we suffer. | ||
| - | resizing pve/root is something best done on when pve/data is completely empty. so I try and do this during the initial setup of a new ProxMox host. | + | resizing pve/root is something best done when pve/data is completely empty. so I try and do this during the initial setup of a new ProxMox host. |
| Just follow the below steps and adjust the lvresize and lvcreate for the sizes you need. In the below example I am adjusting a 4TB Raid 10 to allow for 1TB for pve/root and the rest to pve/data. | Just follow the below steps and adjust the lvresize and lvcreate for the sizes you need. In the below example I am adjusting a 4TB Raid 10 to allow for 1TB for pve/root and the rest to pve/data. | ||
virtualization/proxmox/resizepvedata.1775647779.txt.gz · Last modified: by 185.115.109.210 · Currently locked by: 216.73.216.53
