Created attachment 1206224 [details] Output of grep ' backup ' on vdsm log in debug mode Description of problem: Vdsm uses --config 'backup { ... }' options for read only lvm commands that do not need this option. This works since the commands ignore this option, but add noise to vdsm log and make it harder to debug. Example commands with unneeded backup options: - vgs - vgck See backup.log. There may be more commands with this issue. Version-Release number of selected component (if applicable): All How reproducible: Always Steps to Reproduce: 1. Look in vdsm logs in DEBUG mode for lvm commands run by vdsm. Actual results: backup option used in read only commands Expected results: backup option used only in commands that may create a backup
Zdenek, do we have a list of commands that needs this option, or we should just use this on commands that mention the backup options in the manual? $ man lvchange | grep backup tionPolicy] [-A|--autobackup {y|n}] [--cachepolicy policy] [--cachesettings key=value] [--commandprofile ProfileName] [-C|--contiguous {y|n}] [-d|--debug] [--degraded] [--deltag
There are more question to ask first: 1. Would there there be a plan to use this without locking_type=4 ? 2. There would be no point to configure backups on 'hosts' when executed command should be purely read-only (locking_type=4).
Removing old need infos.
Closing old bugs, reopen if still needed.