cfs-lock 'file-vzdump_cron' error: got lock request timeout (500)

[promoxer]

I'm trying to change the storage of my backup job and not sure how to translate this error into corrective action.

 

[Moayad]

Hi,

Can you please clarify how you attempted to change the storage for your backup job?

 

[promoxer]

1. Select the backup job by clicking on it
2. Click on `Edit`
3. Click on Storage dropdown to change it
4. Error shows up when I click `OK`

Error not showing after I reboot PVE

 

[Moayad]

Could you please share your storage config? `cat /etc/pve/storage.cfg`

 

[promoxer]

```
dir: usb-nvme
path /mnt/usb-nvme
content backup
prune-backups keep-all=1
shared 0
```

There are others, but this was the one that gave that error.

 

[Moayad]

Thank you!

Could you please also provide us with the output of the following commands:

cat /etc/pve/jobs.cfg
pvesh get /cluster/backup
cat /etc/vzdump.conf

 

[promoxer]

```
root@pve:/scripts# cat /etc/vzdump.conf
# vzdump default settings

#tmpdir: DIR
#dumpdir: DIR
#storage: STORAGE_ID
#mode: snapshot|suspend|stop
#bwlimit: KBPS
#performance: [max-workers=N][,pbs-entries-max=N]
#ionice: PRI
#lockwait: MINUTES
#stopwait: MINUTES
#stdexcludes: BOOLEAN
#mailto: ADDRESSLIST
#prune-backups: keep-INTERVAL=N[,...]
#script: FILENAME
#exclude-path: PATHLIST
#pigz: N
#notes-template: {{guestname}}
root@pve:/scripts# pvesh get /cluster/backup
┌──────────────────────┐
│ id │
╞══════════════════════╡
│ backup-3d1923e9-1e58 │
└──────────────────────┘
root@pve:/scripts# cat /etc/pve/jobs.cfg
vzdump: backup-3d1923e9-1e58
schedule 02:15
compress zstd
enabled 1
mailnotification always
mailto pve@example.com
mode snapshot
node pve
notes-template {{guestname}}
prune-backups keep-last=1
storage local
vmid 101,103,102

root@pve:/scripts#
```

 

[Moayad]

Hi,

Thank you for the output!

Could you please run the `journalctl -f` in the terminal and then provide us with the output when you changed the storage on the backup?

 

[promoxer]

Hi Moayad,

The issue is no longer reproducible. Does `journalctl -f` still help?

 

[Moayad]

No, will not help if the issue no longer reproduced. You can provide us with the syslog next time if the issue happened again and the `pveversion -v`.

 

[promoxer]

Hi Moayad,

Please state the full set of commands I need to run before and after trying to change the storage.

 

[Moayad]

Before you change the storage, issue the following command, after you get the error you can `Ctrl+C` on the below command and attach the syslog to this thread.

journalctl -f > /tmp/$(hostname)-syslog.txt

 

[promoxer]

ok will do thanks