Results 1 to 2 of 2

Thread: Backup Problems - unable to detect lvm volume group

  1. #1
    Join Date
    Jul 2011
    Posts
    32

    Default Backup Problems - unable to detect lvm volume group

    After upgrading to proxmox 2.0 rc1 we have the following problem:

    103: Mär 10 23:08:39 INFO: Starting Backup of VM 103 (qemu) 103: Mär 10 23:08:39 INFO: status = running 103: Mär 10 23:08:40 INFO: mode failure - unable to detect lvm volume group 103: Mär 10 23:08:40 INFO: trying 'suspend' mode instead 103: Mär 10 23:08:40 INFO: backup mode: suspend 103: Mär 10 23:08:40 INFO: ionice priority: 7 103: Mär 10 23:08:40 INFO: suspend vm
    root@proxmox1:~# pveversion -v
    pve-manager: 2.0-35 (pve-manager/2.0/d07f49c3)
    running kernel: 2.6.32-7-pve
    proxmox-ve-2.6.32: 2.0-60
    pve-kernel-2.6.32-7-pve: 2.6.32-60
    lvm2: 2.02.88-2pve1
    clvm: 2.02.88-2pve1
    corosync-pve: 1.4.1-1
    openais-pve: 1.1.4-2
    libqb: 0.10.1-2
    redhat-cluster-pve: 3.1.8-3
    resource-agents-pve: 3.9.2-3
    fence-agents-pve: 3.1.7-1
    pve-cluster: 1.0-23
    qemu-server: 2.0-20
    pve-firmware: 1.0-15
    libpve-common-perl: 1.0-15
    libpve-access-control: 1.0-16
    libpve-storage-perl: 2.0-12
    vncterm: 1.0-2
    vzctl: 3.0.30-2pve1
    vzprocps: 2.0.11-2
    vzquota: 3.0.12-3
    pve-qemu-kvm: 1.0-4
    ksm-control-daemon: 1.1-1

    root@proxmox1:~# less /etc/pve/qemu-server/103.conf
    bootdisk: ide0
    cores: 4
    ide0: san_disk0_lun0:vm-103-disk-2
    ide1: san_disk0_lun0:vm-103-disk-1
    ide3: none,media=cdrom
    memory: 8096
    name: system-prod
    net0: rtl8139=82:5B:96:701:85,bridge=vmbr0
    net1: rtl8139=F2:C1:CB01:1B,bridge=vmbr1
    onboot: 1
    ostype: win7
    sockets: 1

    root@proxmox1:~# less /etc/pve/storage.cfg
    iscsi: san_disk0
    portal 192.168.100.3
    target iqn.2011-10.com.company:san.disk.0
    content none

    lvm: san_disk0_lun0
    vgname san_disk0
    base san_disk0:0.0.0.scsi-149455400000000005c2eadd81f00841f3f89a12b19965ee7
    shared
    content images

    dir: local
    path /var/lib/vz
    content images,iso,vztmpl,rootdir

    dir: backup
    path /mnt/san/nfs/backup/proxmox/
    content backup

    root@proxmox1:~# pvdisplay
    --- Physical volume ---
    PV Name /dev/disk/by-id/dm-name-149455400000000005c2eadd81f00841f3f89a12b19965ee7
    VG Name san_disk0
    PV Size 400,00 GiB / not usable 4,00 MiB
    Allocatable yes
    PE Size 4,00 MiB
    Total PE 102399
    Free PE 41830
    Allocated PE 60569
    PV UUID Xkej3e-oKct-IMCy-MRi1-5uU2-OgF1-csSoAS
    .....

    root@proxmox1:~# vgdisplay
    --- Volume group ---
    VG Name san_disk0
    System ID
    Format lvm2
    Metadata Areas 1
    Metadata Sequence No 603
    VG Access read/write
    VG Status resizable
    MAX LV 0
    Cur LV 12
    Open LV 12
    Max PV 0
    Cur PV 1
    Act PV 1
    VG Size 400,00 GiB
    PE Size 4,00 MiB
    Total PE 102399
    Alloc PE / Size 60569 / 236,60 GiB
    Free PE / Size 41830 / 163,40 GiB
    VG UUID GCY4cg-7wev-Q2Ee-7o09-pj0k-PNZp-ZGjex2
    ....

    root@proxmox1:~# vgdisplay
    ....
    --- Logical volume ---
    LV Name /dev/san_disk0/vm-103-disk-2
    VG Name san_disk0
    LV UUID NHN0ah-fz04-cYxT-awta-AgZO-surM-jOaf1U
    LV Write Access read/write
    LV Status available
    # open 1
    LV Size 28,00 GiB
    Current LE 7168
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Block device 253:7

    --- Logical volume ---
    LV Name /dev/san_disk0/vm-103-disk-1
    VG Name san_disk0
    LV UUID iq1lPk-N0G7-jXGV-g0SJ-iJDo-svA4-m0R00u
    LV Write Access read/write
    LV Status available
    # open 1
    LV Size 12,00 GiB
    Current LE 3072
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Block device 253:6
    ....

    I don't understand why it is not working.
    Perhaps, somebody can give me a hint.

    Thanks and regards,
    Oer

  2. #2
    Join Date
    Jul 2011
    Posts
    32

    Default Re: Backup Problems - unable to detect lvm volume group

    Ok I fond the solution.

    http://pve.proxmox.com/pipermail/pve...ry/003341.html

    Its a problem with the locale settings.
    Perhaps it is a proxmox bug.

    Regards,
    Erik

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •