Force display of disk size in hardware tab of a VM!

C

christophe

Renowned Member
Mar 31, 2011
202
10
83
Hi all,

IIRC, disk size was displayed in PVE 1.x, on front of each disk.

PVE 2.x (2.2 included) does not display the size anymore, requiring to browse each disk in the storage view : not very convenient...

A way to force size display :
- edit your disk, check "no backup" : an option "size=" is now displayed!
- edit again, uncheck (if needed) "no backup" : "size=" is still there : good!

Can we hope a permanent display of disks size here?

Thanks for this great product!

Christophe.
 
Last edited:
GREAT, thank you!

But on a five nodes cluster (HP ProLiant DL380 G7 ) + SAN (HP P2000 G3 iSCSI), when first launched :

root@px1:/var/log/pve/tasks# qm rescan
iscsiadm: Could not get dev for 1. Possible sysfs incompatibility.


command '/usr/bin/iscsiadm --mode session -r 1 -R' failed: exit code 1
iscsiadm: Could not get dev for 2. Possible sysfs incompatibility.


command '/usr/bin/iscsiadm --mode session -r 2 -R' failed: exit code 1
iscsiadm: Could not get dev for 3. Possible sysfs incompatibility.


command '/usr/bin/iscsiadm --mode session -r 3 -R' failed: exit code 1
iscsiadm: Could not get dev for 4. Possible sysfs incompatibility.


command '/usr/bin/iscsiadm --mode session -r 4 -R' failed: exit code 1
iscsiadm: Could not get dev for 5. Possible sysfs incompatibility.


command '/usr/bin/iscsiadm --mode session -r 5 -R' failed: exit code 1
iscsiadm: Could not get dev for 6. Possible sysfs incompatibility.


command '/usr/bin/iscsiadm --mode session -r 6 -R' failed: exit code 1
iscsiadm: Could not get dev for 7. Possible sysfs incompatibility.


command '/usr/bin/iscsiadm --mode session -r 7 -R' failed: exit code 1
iscsiadm: Could not get dev for 8. Possible sysfs incompatibility.


command '/usr/bin/iscsiadm --mode session -r 8 -R' failed: exit code 1
root@px1:/var/log/pve/tasks#

Then, ran qm rescan on all other nodes : no error.
Then again on first node : no error!!!

It's a production cluster...
Any idea?

Christophe.
 
root@px1:~# pveversion -v
pve-manager: 2.2-26 (pve-manager/2.2/c1614c8c)
running kernel: 2.6.32-16-pve
proxmox-ve-2.6.32: 2.2-80
pve-kernel-2.6.32-16-pve: 2.6.32-80
pve-kernel-2.6.32-14-pve: 2.6.32-74
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-1
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-28
qemu-server: 2.0-64
pve-firmware: 1.0-21
libpve-common-perl: 1.0-37
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-34
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.2-7
ksm-control-daemon: 1.1-1

Christophe.
 
You must log in or register to reply here.
Top Bottom