<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Il 14/07/19 19:35, Gianni Milo ha
scritto:<br>
</div>
<blockquote type="cite"
cite="mid:CACzVk9W_YdzDJuGzaarY-cnvzbeaVq=1CnY6M_53pF99sOykpw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I
successfully create a VM with disk managed by linstor-proxmox
and I <br>
</blockquote>
</div>
<div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
see the vm-100-disk-1 syncing... in sync on two nodes!</blockquote>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
</div>
<div>
<div dir="auto">What about the 3rd node? Is that not syncing or
you have configured it as a Diskless node?</div>
<div dir="auto">Have you set the redundancy number to 3 in
storage.cfg ?</div>
</div>
</blockquote>
<p>I use to set redundancy 2 on my cluster, so a third node is not
used for a single volume<br>
</p>
<blockquote type="cite"
cite="mid:CACzVk9W_YdzDJuGzaarY-cnvzbeaVq=1CnY6M_53pF99sOykpw@mail.gmail.com">
<div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">But I get an
error when I start the VM<br>
(it starts withoud drbd disk)</blockquote>
<div dir="auto"><br>
</div>
<div dir="auto">Have you tried starting it on one of Diskfull
nodes?</div>
</div>
</blockquote>
<p>Do you mean diskless node?</p>
<p>Interesting, just tried but same results, see logs later<br>
</p>
<blockquote type="cite"
cite="mid:CACzVk9W_YdzDJuGzaarY-cnvzbeaVq=1CnY6M_53pF99sOykpw@mail.gmail.com">
<div>
<div dir="auto"><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">before
pasting logs, another strange thing is that if I broswe the <br>
content of drbd storage, from proxmox, I can't see the VM disk
but I get <br>
the status and the %usage</blockquote>
<div dir="auto"><br>
</div>
</div>
<div>
<div dir="auto">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.</div>
</div>
</blockquote>
<p>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<br>
</p>
<br>
<blockquote type="cite"
cite="mid:CACzVk9W_YdzDJuGzaarY-cnvzbeaVq=1CnY6M_53pF99sOykpw@mail.gmail.com">
<div>
<div dir="auto">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?).</div>
</div>
</blockquote>
<p>drbdtop is normal:</p>
<p>│Resource: vm-100-disk-1: (Overall danger score: 0)<br>
│ Local
Disc(Secondary): <br>
│ volume 0 (/dev/drbd1001): UpToDate(normal disk state)<br>
│
<br>
│ Connection to p6t2(Secondary): Connected(connected to p6t2)<br>
│ volume
0:
<br>
│ UpToDate(normal disk state) <br>
</p>
<p>I did also try to use a drbd volume from host and it is working
well, I can write, the Primary promotion was automatic<br>
</p>
<p>I think there are some communication problem with the proxmox
storage plugin but I'm not sure, of course.</p>
<p>Anyway thank you for your reply!</p>
<p><br>
</p>
<p>Here the logs of the VM start on a diskless node<br>
</p>
<p>SUCCESS:<br>
Description:<br>
New resource 'vm-101-disk-1' on node 'p6t2' registered.<br>
Details:<br>
Resource 'vm-101-disk-1' on node 'p6t2' UUID is:
ba138d06-9584-48ff-9662-cf2ca0e15044<br>
SUCCESS:<br>
Description:<br>
Volume with number '0' on resource 'vm-101-disk-1' on node
'p6t2' successfully registered<br>
Details:<br>
Volume UUID is: f995230b-d95c-4745-bb6f-db974991a3f1<br>
SUCCESS:<br>
Created resource 'vm-101-disk-1' on 'p6t2'<br>
SUCCESS:<br>
Added peer(s) 'p6t2' to resource 'vm-101-disk-1' on 'p6t3'<br>
SUCCESS:<br>
Added peer(s) 'p6t2' to resource 'vm-101-disk-1' on 'p6t1'<br>
SUCCESS:<br>
Description:<br>
Resource 'vm-101-disk-1' on 'p6t2' ready<br>
Details:<br>
Node(s): 'p6t2', Resource: 'vm-101-disk-1'<br>
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<br>
Use of uninitialized value in join or string at
/usr/share/perl5/PVE/Storage/Custom/LINSTORPlugin.pm line 152.<br>
<br>
NOTICE<br>
Intentionally removing diskless assignment (vm-101-disk-1) on
(p6t2).<br>
It will be re-created when the resource is actually used on this
node.<br>
SUCCESS:<br>
Description:<br>
Node: p6t2, Resource: vm-101-disk-1 marked for deletion.<br>
Details:<br>
Node: p6t2, Resource: vm-101-disk-1 UUID is:
ba138d06-9584-48ff-9662-cf2ca0e15044<br>
SUCCESS:<br>
Deleted 'vm-101-disk-1' on 'p6t2'<br>
SUCCESS:<br>
Notified 'p6t3' that 'vm-101-disk-1' is being deleted on
'p6t2'<br>
SUCCESS:<br>
Notified 'p6t1' that 'vm-101-disk-1' is being deleted on
'p6t2'<br>
SUCCESS:<br>
Description:<br>
Node: p6t2, Resource: vm-101-disk-1 deletion complete.<br>
Details:<br>
Node: p6t2, Resource: vm-101-disk-1 UUID was:
ba138d06-9584-48ff-9662-cf2ca0e15044<br>
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<br>
</p>
<p><br>
</p>
</body>
</html>