[SOLVED] moving disk got stuck from nfs to rbd

[Knuuut]

Hi,

while moving a disk on a running VM on pve 5.4, it got stuck reproduceable when moving from nfs to rbd. This is NOT the case when moving the disk vice versa.
If I move the disk from a shutdown VM it works.

create full clone of drive scsi2 (bkp-1901:111/vm-111-disk-1.raw)
drive mirror is starting for drive-scsi2
drive-scsi2: transferred: 0 bytes remaining: 17179869184 bytes total: 17179869184 bytes progression: 0.00 % busy: 1 ready: 0
drive-scsi2: transferred: 34603008 bytes remaining: 17145266176 bytes total: 17179869184 bytes progression: 0.20 % busy: 1 ready: 0
drive-scsi2: transferred: 79691776 bytes remaining: 17100177408 bytes total: 17179869184 bytes progression: 0.46 % busy: 1 ready: 0
drive-scsi2: transferred: 134217728 bytes remaining: 17045651456 bytes total: 17179869184 bytes progression: 0.78 % busy: 1 ready: 0
drive-scsi2: transferred: 185597952 bytes remaining: 16994271232 bytes total: 17179869184 bytes progression: 1.08 % busy: 1 ready: 0
drive-scsi2: transferred: 229638144 bytes remaining: 16950231040 bytes total: 17179869184 bytes progression: 1.34 % busy: 1 ready: 0
drive-scsi2: transferred: 279969792 bytes remaining: 16900030464 bytes total: 17180000256 bytes progression: 1.63 % busy: 1 ready: 0
drive-scsi2: transferred: 343932928 bytes remaining: 16836067328 bytes total: 17180000256 bytes progression: 2.00 % busy: 1 ready: 0
drive-scsi2: transferred: 394264576 bytes remaining: 16786063360 bytes total: 17180327936 bytes progression: 2.29 % busy: 1 ready: 0
drive-scsi2: transferred: 448790528 bytes remaining: 16731996160 bytes total: 17180786688 bytes progression: 2.61 % busy: 1 ready: 0
drive-scsi2: transferred: 493879296 bytes remaining: 16687300608 bytes total: 17181179904 bytes progression: 2.87 % busy: 1 ready: 0
drive-scsi2: transferred: 546308096 bytes remaining: 16635002880 bytes total: 17181310976 bytes progression: 3.18 % busy: 1 ready: 0
drive-scsi2: transferred: 612368384 bytes remaining: 16569204736 bytes total: 17181573120 bytes progression: 3.56 % busy: 1 ready: 0
drive-scsi2: transferred: 662700032 bytes remaining: 16521560064 bytes total: 17184260096 bytes progression: 3.86 % busy: 1 ready: 0
drive-scsi2: transferred: 716177408 bytes remaining: 16468082688 bytes total: 17184260096 bytes progression: 4.17 % busy: 1 ready: 0
drive-scsi2: transferred: 2218786816 bytes remaining: 14902558720 bytes total: 17121345536 bytes progression: 12.96 % busy: 1 ready: 0
drive-scsi2: transferred: 2236612608 bytes remaining: 14885781504 bytes total: 17122394112 bytes progression: 13.06 % busy: 1 ready: 0
drive-scsi2: transferred: 2236612608 bytes remaining: 14885781504 bytes total: 17122394112 bytes progression: 13.06 % busy: 1 ready: 0
drive-scsi2: transferred: 2236612608 bytes remaining: 14885781504 bytes total: 17122394112 bytes progression: 13.06 % busy: 1 ready: 0
drive-scsi2: transferred: 2236612608 bytes remaining: 14885781504 bytes total: 17122394112 bytes progression: 13.06 % busy: 1 ready: 0
drive-scsi2: transferred: 2236612608 bytes remaining: 14885781504 bytes total: 17122394112 bytes progression: 13.06 % busy: 1 ready: 0
drive-scsi2: transferred: 2236612608 bytes remaining: 14885781504 bytes total: 17122394112 bytes progression: 13.06 % busy: 1 ready: 0
drive-scsi2: transferred: 2236612608 bytes remaining: 14885781504 bytes total: 17122394112 bytes progression: 13.06 % busy: 1 ready: 0
drive-scsi2: transferred: 2236612608 bytes remaining: 14885781504 bytes total: 17122394112 bytes progression: 13.06 % busy: 1 ready: 0
drive-scsi2: transferred: 2236612608 bytes remaining: 14885781504 bytes total: 17122394112 bytes progression: 13.06 % busy: 1 ready: 0
drive-scsi2: transferred: 2236612608 bytes remaining: 14885781504 bytes total: 17122394112 bytes progression: 13.06 % busy: 1 ready: 0
drive-scsi2: transferred: 2236612608 bytes remaining: 14885781504 bytes total: 17122394112 bytes progression: 13.06 % busy: 1 ready: 0
drive-scsi2: transferred: 2236612608 bytes remaining: 14885781504 bytes total: 17122394112 bytes progression: 13.06 % busy: 1 ready: 0
drive-scsi2: transferred: 2236612608 bytes remaining: 14885781504 bytes total: 17122394112 bytes progression: 13.06 % busy: 1 ready: 0
drive-scsi2: transferred: 2236612608 bytes remaining: 14885781504 bytes total: 17122394112 bytes progression: 13.06 % busy: 1 ready: 0
drive-scsi2: transferred: 2236612608 bytes remaining: 14885781504 bytes total: 17122394112 bytes progression: 13.06 % busy: 1 ready: 0
drive-scsi2: transferred: 2236612608 bytes remaining: 14885781504 bytes total: 17122394112 bytes progression: 13.06 % busy: 1 ready: 0

Any ideas?

Thanks Knuuut

 

[Knuuut]

Nobody?

The only way to get rid of it is to cancel the block job, kill the VM and move the disk offline.

Again, this is reproduceable.

This looks like a bug in qemu...?

Cheers Knuuut

 

[Knuuut]

I've solved this issue by myself. You have to take care about the nfs version while setting up the storage in Proxmox gui. If you take the default settings, Proxmox will do a nfs mount on version 4 while this is a nfs 3 server. Setting this explicit to version 3 will do the trick.

Cheers Knuuut