Il 14/07/19 19:35, Gianni Milo ha scritto:
I successfully create a VM with disk managed by linstor-proxmox and I
see the vm-100-disk-1 syncing... in sync on two nodes!
What about the 3rd node? Is that not syncing or you have configured it
as a Diskless node?
Have you set the redundancy number to 3 in storage.cfg ?
I use to set redundancy 2 on my cluster, so a third node is not used
for a single volume
But I get an error when I start the VM
(it starts withoud drbd disk)
Have you tried starting it on one of Diskfull nodes?
Do you mean diskless node?
Interesting, just tried but same results, see logs later
before pasting logs, another strange thing is that if I broswe the
content of drbd storage, from proxmox, I can't see the VM disk but
I get
the status and the %usage
I think this is broken on PVE5 as well. I cannot browse the content of
the drbd storage in the webgui but I can see the total amount and the
space used in the summary tab. This used to work in the past but I'm
unsure at which stage it got broken.
I run a similar 3-nodes production cluster with PVE 5.4-3 and linstor
0.9.5-1 and 0.9.2-1 witch shows the storage content
Here. It complains that the drbd volume is not in a writeable state
for some reason (read only?).Confirm its status with drbdtop and make
the necessary actions to switch it in the correct (writeable) state
(Primary?).
drbdtop is normal:
│Resource: vm-100-disk-1: (Overall danger score: 0)
│ Local Disc(Secondary):
│ volume 0 (/dev/drbd1001): UpToDate(normal disk state)
│
│ Connection to p6t2(Secondary): Connected(connected to p6t2)
│ volume 0:
│ UpToDate(normal disk state)
I did also try to use a drbd volume from host and it is working well, I
can write, the Primary promotion was automatic
I think there are some communication problem with the proxmox storage
plugin but I'm not sure, of course.
Anyway thank you for your reply!
Here the logs of the VM start on a diskless node
SUCCESS:
Description:
New resource 'vm-101-disk-1' on node 'p6t2' registered.
Details:
Resource 'vm-101-disk-1' on node 'p6t2' UUID is:
ba138d06-9584-48ff-9662-cf2ca0e15044
SUCCESS:
Description:
Volume with number '0' on resource 'vm-101-disk-1' on node 'p6t2'
successfully registered
Details:
Volume UUID is: f995230b-d95c-4745-bb6f-db974991a3f1
SUCCESS:
Created resource 'vm-101-disk-1' on 'p6t2'
SUCCESS:
Added peer(s) 'p6t2' to resource 'vm-101-disk-1' on 'p6t3'
SUCCESS:
Added peer(s) 'p6t2' to resource 'vm-101-disk-1' on 'p6t1'
SUCCESS:
Description:
Resource 'vm-101-disk-1' on 'p6t2' ready
Details:
Node(s): 'p6t2', Resource: 'vm-101-disk-1'
kvm: -drive
file=/dev/drbd/by-res/vm-101-disk-1/0,if=none,id=drive-scsi0,discard=on,format=raw,cache=none,aio=native,detect-zeroes=unmap:
The device is not writable: Permission denied
Use of uninitialized value in join or string at
/usr/share/perl5/PVE/Storage/Custom/LINSTORPlugin.pm line 152.
NOTICE
Intentionally removing diskless assignment (vm-101-disk-1) on (p6t2).
It will be re-created when the resource is actually used on this node.
SUCCESS:
Description:
Node: p6t2, Resource: vm-101-disk-1 marked for deletion.
Details:
Node: p6t2, Resource: vm-101-disk-1 UUID is:
ba138d06-9584-48ff-9662-cf2ca0e15044
SUCCESS:
Deleted 'vm-101-disk-1' on 'p6t2'
SUCCESS:
Notified 'p6t3' that 'vm-101-disk-1' is being deleted on 'p6t2'
SUCCESS:
Notified 'p6t1' that 'vm-101-disk-1' is being deleted on 'p6t2'
SUCCESS:
Description:
Node: p6t2, Resource: vm-101-disk-1 deletion complete.
Details:
Node: p6t2, Resource: vm-101-disk-1 UUID was:
ba138d06-9584-48ff-9662-cf2ca0e15044
TASK ERROR: start failed: command '/usr/bin/kvm -id 101 -name prova2
-chardev 'socket,id=qmp,path=/var/run/qemu-server/101.qmp,server,nowait'
-mon 'chardev=qmp,mode=control' -chardev
'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' -mon
'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/101.pid
-daemonize -smbios 'type=1,uuid=f01631be-8d16-4eb6-acb8-d91957317262'
-smp '2,sockets=1,cores=2,maxcpus=2' -nodefaults -boot
'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg'
-vnc unix:/var/run/qemu-server/101.vnc,password -cpu qemu64 -m 512
-device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1e' -device
'pci-bridge,id=pci.2,chassis_nr=2,bus=pci.0,addr=0x1f' -device
'vmgenid,guid=e2a1888f-adcb-42d3-98e7-b05b03277236' -device
'piix3-usb-uhci,id=uhci,bus=pci.0,addr=0x1.0x2' -device
'usb-tablet,id=tablet,bus=uhci.0,port=1' -device
'VGA,id=vga,bus=pci.0,addr=0x2' -device
'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' -iscsi
'initiator-name=iqn.1993-08.org.debian:01:9504984c045' -drive
'if=none,id=drive-ide2,media=cdrom,aio=threads' -device
'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=200' -device
'virtio-scsi-pci,id=scsihw0,bus=pci.0,addr=0x5' -drive
'file=/dev/drbd/by-res/vm-101-disk-1/0,if=none,id=drive-scsi0,discard=on,format=raw,cache=none,aio=native,detect-zeroes=unmap'
-device
'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,bootindex=100'
-netdev
'type=tap,id=net0,ifname=tap101i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on'
-device
'virtio-net-pci,mac=BA:BF:04:AE:9E:3B,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=300'
-machine 'accel=tcg,type=pc'' failed: exit code 1
_______________________________________________
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
[email protected]
http://lists.linbit.com/mailman/listinfo/drbd-user
