Adding a second disk for LVM pve-data

dewmsolo

New Member
I have a fresh install of 4.3 on a server with 2 hard disks (sda=1tb and sdb=3tb). I performed the install with just one hard disk (sda) in the server. Once everything was running, I added a second (sdb) hard drive to the server.

I now would like sdb1 to be the only location for VMs. In other words I don't just want to extend pve-data. I want to make it so I can just rsync sdb1.

I do have another 3tb on the way. The idea being to mirror the current sdb on the new sdc when it gets it. Either through a daily rsync or if possible without damaging the data on sdb make them a mirror raid.

I have been following this: http://pve.proxmox.com/wiki/Extending_Local_Container_Storage
Although it is not what I want to do. I don't want to extend pve-data. I want to make sure it exclusively uses sdb.

Here's the output of a few commands that might help you understand my situation and what I am trying to do.

lsblk:
Code:
root@proxmox:/dev/pve# lsblk
NAME               MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                  8:0    0 931.5G  0 disk
├─sda1               8:1    0  1007K  0 part
├─sda2               8:2    0   127M  0 part /boot/efi
└─sda3               8:3    0 931.4G  0 part
  ├─pve-root       251:0    0    96G  0 lvm  /
  ├─pve-swap       251:1    0     8G  0 lvm  [SWAP]
  ├─pve-data_tmeta 251:2    0   104M  0 lvm 
  │ └─pve-data     251:4    0 811.4G  0 lvm 
  └─pve-data_tdata 251:3    0 811.4G  0 lvm 
    └─pve-data     251:4    0 811.4G  0 lvm 
sdb                  8:16   0   2.7T  0 disk
└─sdb1               8:17   0   2.7T  0 part
sr0                 11:0    1  1024M  0 rom

pvdisplay:
Code:
root@proxmox:/dev/pve# pvdisplay
  --- Physical volume ---
  PV Name               /dev/sda3
  VG Name               pve
  PV Size               931.39 GiB / not usable 1.69 MiB
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              238435
  Free PE               4043
  Allocated PE          234392
  PV UUID               7ATzgK-Paf3-zG3e-Bdv8-8A4v-k01T-y6i2iZ
   
  --- Physical volume ---
  PV Name               /dev/sdb1
  VG Name               pve
  PV Size               2.73 TiB / not usable 3.44 MiB
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              715396
  Free PE               715396
  Allocated PE          0
  PV UUID               aQRbdG-wCwW-3qNw-jtKs-xsWL-X1u4-KcWYqV

vgdisplay:
Code:
root@proxmox:/dev/pve# vgdisplay
  --- Volume group ---
  VG Name               pve
  System ID             
  Format                lvm2
  Metadata Areas        2
  Metadata Sequence No  8
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                3
  Open LV               2
  Max PV                0
  Cur PV                2
  Act PV                2
  VG Size               3.64 TiB
  PE Size               4.00 MiB
  Total PE              953831
  Alloc PE / Size       234392 / 915.59 GiB
  Free  PE / Size       719439 / 2.74 TiB
  VG UUID               3BfGps-cQGF-ZWAt-u4uU-uMmz-vpxo-oPNQiu

lvdisplay:
Code:
root@proxmox:/dev/pve# lvdisplay
  --- Logical volume ---
  LV Path                /dev/pve/swap
  LV Name                swap
  VG Name                pve
  LV UUID                4TPauJ-28Jk-1DdR-H0lF-0HAh-DQlg-ppp7v0
  LV Write Access        read/write
  LV Creation host, time proxmox, 2016-10-17 09:23:16 -0400
  LV Status              available
  # open                 2
  LV Size                8.00 GiB
  Current LE             2048
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           251:1
   
  --- Logical volume ---
  LV Path                /dev/pve/root
  LV Name                root
  VG Name                pve
  LV UUID                yFTC3k-SB1h-SVBp-Kfdd-LqdN-w8lO-MUyg9z
  LV Write Access        read/write
  LV Creation host, time proxmox, 2016-10-17 09:23:16 -0400
  LV Status              available
  # open                 1
  LV Size                96.00 GiB
  Current LE             24576
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           251:0
   
  --- Logical volume ---
  LV Name                data
  VG Name                pve
  LV UUID                VvGIEK-aFzS-RmE2-AOJl-aII8-NYbw-h30Q4B
  LV Write Access        read/write
  LV Creation host, time proxmox, 2016-10-17 09:23:17 -0400
  LV Pool metadata       data_tmeta
  LV Pool data           data_tdata
  LV Status              available
  # open                 0
  LV Size                811.39 GiB
  Allocated pool data    0.00%
  Allocated metadata     0.42%
  Current LE             207716
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           251:4
 
You could add sdc (the new drive) to the system and create a software raid1 mirror on sdc. When you create the mirror just specify the second disk is missing. The raid device (ie md0) will come active on sdc alone. You can then add the raid device to LVM as a new volume group. Once added to LVM you can migrate the data such that it only lives on the raid device. You can then remove sdb from LVM. Now that sdb is free from LVM, you can add it as the second drive to raid1 device for failover.
 
You could add sdc (the new drive) to the system and create a software raid1 mirror on sdc. When you create the mirror just specify the second disk is missing. The raid device (ie md0) will come active on sdc alone. You can then add the raid device to LVM as a new volume group. Once added to LVM you can migrate the data such that it only lives on the raid device. You can then remove sdb from LVM. Now that sdb is free from LVM, you can add it as the second drive to raid1 device for failover.
This is a great info...thanks a million. Now I know that I'll end up being able to do what I want.

Now can anyone point me in the right direction to remove the currently allocated space to pve-data and how I can only allocate to it the space on sdb1.

At this point I am considering making a new volume group just for it...but then it wouldn't be pve-data....and I am not quite sure how proxmox would respond or how to configure it.
 
This is a great info...thanks a million. Now I know that I'll end up being able to do what I want.

Now can anyone point me in the right direction to remove the currently allocated space to pve-data and how I can only allocate to it the space on sdb1.

At this point I am considering making a new volume group just for it...but then it wouldn't be pve-data....and I am not quite sure how proxmox would respond or how to configure it.

If you wait until your new drive comes in this is really easy. Once the new LVM is created, you can just add it via the Data Center storage GUI.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!