Install a new LVM volume as extra storage

check-ict

Well-Known Member
Apr 19, 2011
102
18
58
Hello,

I have a 2x4 RAID10 setup (8 disks total). I installed Proxmox on the first RAID set, but now I want to add the second RAID set as extra storage for virtual machines.

I fdisk the disk and create a LVM partition.
Then I do this:
pvcreate /dev/sdb1
vgcreate data2 /dev/sdb1
lvcreate -L 1850G -n data2 data2
mkfs.ext4 /dev/mapper/data2-data2
mount /dev/mapper/data2-data2 /mnt/data2

Then I go to the web interface and create a directory "/mnt/data2" for virtual machines.

When I do back-ups, I get the following error:
101: Jun 23 17:23:02 INFO: Starting Backup of VM 101 (qemu)
101: Jun 23 17:23:02 INFO: running
101: Jun 23 17:23:02 INFO: status = running
101: Jun 23 17:23:02 INFO: mode failure - unable to detect lvm volume group
101: Jun 23 17:23:02 INFO: trying 'suspend' mode instead
101: Jun 23 17:23:02 INFO: backup mode: suspend
101: Jun 23 17:23:02 INFO: ionice priority: 7
101: Jun 23 17:23:02 INFO: suspend vm
101: Jun 23 17:23:03 INFO: creating archive '/mnt/backup1/vzdump-qemu-101-2011_06_23-17_23_02.tar'
101: Jun 23 17:23:03 INFO: adding '/mnt/backup1/vzdump-qemu-101-2011_06_23-17_23_02.tmp/qemu-server.conf' to archive ('qemu-server.conf')
101: Jun 23 17:23:03 INFO: adding '/mnt/data2/images/101/vm-101-disk-1.raw' to archive ('vm-disk-virtio1.raw')
101: Jun 23 17:24:38 INFO: Total bytes written: 740951552 (7.43 MiB/s)
101: Jun 23 17:24:38 INFO: archive file size: 706MB
101: Jun 23 17:24:38 INFO: delete old backup '/mnt/backup1/vzdump-qemu-101-2011_06_23-17_17_01.tar'
101: Jun 23 17:24:38 INFO: resume vm
101: Jun 23 17:24:38 INFO: vm is online again after 96 seconds
101: Jun 23 17:24:38 INFO: Finished Backup of VM 101 (00:01:36)


pvdisplay:
--- Physical volume ---
PV Name /dev/sdb1
VG Name data2
PV Size 1.82 TB / not usable 3.28 MB
Allocatable yes
PE Size (KByte) 4096
Total PE 476670
Free PE 3070
Allocated PE 473600
PV UUID bWHgsu-Wtex-rxH0-IZOL-k5us-mDWE-YIO8eD

--- Physical volume ---
PV Name /dev/sda2
VG Name pve
PV Size 1.82 TB / not usable 3.28 MB
Allocatable yes
PE Size (KByte) 4096
Total PE 476542
Free PE 1022
Allocated PE 475520
PV UUID N2VPOY-zMAz-Ar2a-cV7U-E0AD-4dhF-w3xlpx

pveversion:
pve-manager: 1.8-18 (pve-manager/1.8/6070)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.8-33
pve-kernel-2.6.32-4-pve: 2.6.32-33
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.27-1pve1
vzdump: 1.2-13
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.1-1
ksm-control-daemon: 1.0-6

pveperf:
CPU BOGOMIPS: 32002.74
REGEX/SECOND: 667865
HD SIZE: 94.49 GB (/dev/mapper/pve-root)
BUFFERED READS: 429.98 MB/sec
AVERAGE SEEK TIME: 8.79 ms
FSYNCS/SECOND: 1894.49
DNS EXT: 78.70 ms
DNS INT: 30.43 ms (24x7hosting.nl)
 
Does it work if your use ext3 instead of ext4?

BTW, you can also use LVM directly (without and file system).
 
Thanks for the quick answer.

Ext3 solved the problem! I will continue using ext3 now.


101: Jun 23 17:59:01 INFO: Starting Backup of VM 101 (qemu) 101: Jun 23 17:59:02 INFO: running 101: Jun 23 17:59:02 INFO: status = running 101: Jun 23 17:59:02 INFO: backup mode: snapshot 101: Jun 23 17:59:02 INFO: ionice priority: 7 101: Jun 23 17:59:02 INFO: Logical volume "vzsnap-proxmox02-0" created
 

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!