From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] storage migration failed: error with cfs lock 'storage-nfs-scratch': unable to create image: got lock timeout - aborting command
Date: Wed, 15 Sep 2021 15:21:56 +0200 [thread overview]
Message-ID: <1631711991.442ebhjlx2.astroid@nora.none> (raw)
In-Reply-To: <20210915081508.GC3261@sv.lnf.it>
On September 15, 2021 10:15 am, Marco Gaiarin wrote:
>
> We are trying to move some VMs disks from a cluster (PVE 5, storage LVM
> thin), to a storage of type NFS (a PVE 6 server, debian buster standard
> NFS server), usin QCOW as destination file/image format.
>
> 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@pam> starting task UPID:pveod1:00007BE2:A90E5224:61410A92:qmmove:100:root@pam:
> Sep 14 22:49:18 pveod1 pvedaemon[31552]: <root@pam> end task UPID:pveod1:00007BE2:A90E5224:61410A92:qmmove:100:root@pam: storage migration failed: error with cfs lock 'storage-nfs-scratch': unable to create image: got lock timeout - aborting command
>
> Only this log row appear, no kernel/nfs errors in nfs server or source
> machine.
>
>
> I've tried to google for this error, or for 'nfs lock timeout' but
> nothing relevant (to me) appear.
>
> Someone have some feedback? Thanks.
this is an issue with certain shared-storage operations in PVE - they have to
happen under a pmxcfs-lock, which has a hard timeout. if the operation
takes too long, the lock will run into the timeout, and the operation
fail.
there has been some recent development to improve the situation:
https://lists.proxmox.com/pipermail/pve-devel/2021-September/049879.html
but it hasn't been finalized yet.
next prev parent reply other threads:[~2021-09-15 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 8:15 Marco Gaiarin
[not found] ` <mailman.90.1631705429.440.pve-user@lists.proxmox.com>
2021-09-15 13:12 ` Marco Gaiarin
2021-09-15 13:21 ` Fabian Grünbichler [this message]
2021-09-15 14:47 ` Marco Gaiarin
2021-09-16 7:26 ` Fabian Grünbichler
2021-09-16 7:46 ` Marco Gaiarin
[not found] <mailman.5.1631700001.9824.pve-user@lists.proxmox.com>
2021-09-15 14:03 ` [PVE-User] pve-user Digest, Vol 162, Issue 12 Christoph Weber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1631711991.442ebhjlx2.astroid@nora.none \
--to=f.gruenbichler@proxmox.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.