not able to delete storage list

[dinster]

in my Storage list, i have 2 Storage Name ie. 1) local and 2) LVM1. i wanted to delete LVM1.

so i click down arrow on beside LVM1 and click delete.

and i got this msg.. see attached.

 

[pixelplumber]

Hi dinster,

Did you create your extra logical volume in the existing pve volume group?

I had the same error a few weeks ago after I'd customised the LVM layout and did that.

(starts about 5 posts down)
http://www.proxmox.com/forum/showthread.php?p=14367#post14367

If you create new logical volumes in the existing pve volume group used by proxmox, then when you try to delete your logical volume it will fail with error code 5.

As far as i understand it proxmox tries to deactivate the whole volume group to remove that logical volume (the vgchange -aln command) but it can't do this as the /dev/pve/root LV is mounted to / and is locked (as its in use), hence the error.

I got around that by setting up a separate VG on a different RAID controller for storage volumes (virtual disks/backups etc).

Hope that helps.

 

[dietmar]

in my Storage list, i have 2 Storage Name ie. 1) local and 2) LVM1. i wanted to delete LVM1.

so i click down arrow on beside LVM1 and click delete.

and i got this msg.. see attached.

Please can you post your storage configuration (/etc/pve/storage.cfg).

 

[dinster]

Please can you post your storage configuration (/etc/pve/storage.cfg).

hi sir..

here u go..

proxmox01:~# cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content images,iso,vztmpl,rootdir

dir: data
path /home/data
shared
content images

 

[dietmar]

hi sir..

here u go..

proxmox01:~# cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content images,iso,vztmpl,rootdir

dir: data
path /home/data
shared
content images

And where is that 'LVM1' storage?

 

[dinster]

And where is that 'LVM1' storage?

that's the problem. it's not listed under storage.cfg but on the web browser it's still there. i think that what makes the error popup.

 

[dietmar]

that's the problem. it's not listed under storage.cfg but on the web browser it's still there. i think that what makes the error popup.

What if you reboot that server, or try:

# /etc/init.d/pvedaemon restart
# /etc/init.d/apache2 restart

does that help?