[PVE-User] pve-user Digest, Vol 162, Issue 12

Christoph Weber Christoph.Weber at xpecto.com
Wed Sep 15 16:03:04 CEST 2021


> Message: 1
> Date: Wed, 15 Sep 2021 10:15:08 +0200
> From: Marco Gaiarin <gaio at sv.lnf.it>
> To: pve-user at pve.proxmox.com
> Subject: [PVE-User] storage migration failed: error with cfs lock
> 	'storage-nfs-scratch': unable to create image: got lock timeout -
> 	aborting command
> Message-ID: <20210915081508.GC3261 at sv.lnf.it>


> We have correctly move some smaller disks (200GB), but if we try to move a
> 'big' disk, we got:
> 
> 	Sep 14 22:48:18 pveod1 pvedaemon[31552]: <root at pam> starting
> task UPID:pveod1:00007BE2:A90E5224:61410A92:qmmove:100:root at pam:
> 	Sep 14 22:49:18 pveod1 pvedaemon[31552]: <root at pam> end task
> UPID:pveod1:00007BE2:A90E5224:61410A92:qmmove:100:root at pam:
> storage migration failed: error with cfs lock 'storage-nfs-scratch': unable to
> create image: got lock timeout - aborting command

I think this thread might be relevant

  https://forum.proxmox.com/threads/error-with-cfs-lock-unable-to-create-image-got-lock-timeout-aborting-command.65786/

Quote:
>>> we have a hard timeout of 60s for any operation obtaining a cluster lock, which includes volume allocation on shared storages.
...
>>> your storage is simply too slow when allocating bigger images it seems. you need to manually allocate them, for example using qemu-img create or convert.





More information about the pve-user mailing list