mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-01-09 14:35:25 +00:00
de1e0ae0e3
When the qemu or libxl driver is configured to use lockd and file_lockspace_dir is set, virtlockd emits an error when libvirtd is retarted May 25 15:44:31 virt81 virtlockd[7723]: Requested operation is not valid: Lockspace for path /data/libvirtd/lockspace already exists There is really no need to fail when the lockspace already exists, paricularly since the user is expected to create the lockspace specified in file_lockspace_dir. Failure to do so will prevent starting any domains virsh start test error: Failed to start domain 'test' error: Unable to open/create resource /data/libvirtd/lockspace/de22c4bf931e7c48b49e8ca64b477d44e78a51543e534df488b05ccd08ec5caa: No such file or directory Also, virLockManagerLockDaemonSetupLockspace already has logic to ignore the error. Since callers are not interested in the error, change virtlockd to not report or return an error when the specified lockspace already exists. Signed-off-by: Jim Fehlig <jfehlig@suse.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com> |
||
|---|---|---|
| .. | ||
| domain_lock.c | ||
| domain_lock.h | ||
| libvirt_lockd.aug | ||
| libvirt_sanlock.aug | ||
| lock_daemon_config.c | ||
| lock_daemon_config.h | ||
| lock_daemon_dispatch.c | ||
| lock_daemon_dispatch.h | ||
| lock_daemon.c | ||
| lock_daemon.h | ||
| lock_driver_lockd.c | ||
| lock_driver_lockd.h | ||
| lock_driver_nop.c | ||
| lock_driver_nop.h | ||
| lock_driver_sanlock.c | ||
| lock_driver.h | ||
| lock_manager.c | ||
| lock_manager.h | ||
| lock_protocol.x | ||
| lockd.conf | ||
| meson.build | ||
| sanlock_helper.c | ||
| sanlock.conf | ||
| test_libvirt_lockd.aug.in | ||
| test_libvirt_sanlock.aug.in | ||
| test_virtlockd.aug.in | ||
| virtlockd-admin.socket.in | ||
| virtlockd.aug | ||
| virtlockd.conf | ||
| virtlockd.init.in | ||
| virtlockd.service.in | ||
| virtlockd.socket.in | ||
| virtlockd.sysconf | ||