Script 'mail_helper' called by obssrc Hello community, here is the log from the commit of package lvm2 for openSUSE:Factory checked in at 2025-12-30 12:00:54 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/lvm2 (Old) and /work/SRC/openSUSE:Factory/.lvm2.new.1928 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "lvm2" Tue Dec 30 12:00:54 2025 rev:178 rq:1324706 version:2.03.38 Changes: -------- --- /work/SRC/openSUSE:Factory/lvm2/lvm2.changes 2025-12-25 19:57:22.858587669 +0100 +++ /work/SRC/openSUSE:Factory/.lvm2.new.1928/lvm2.changes 2025-12-30 12:01:06.586397382 +0100 @@ -1,0 +2,25 @@ +Mon Dec 29 07:29:17 UTC 2025 - Glass Su <[email protected]> + +- update lvm.conf: sync up with upstream v2_03_38 (bsc#1255680) + - Remove unused config options: + - allocation/vdo_use_metadata_hints + - allocation/vdo_write_policy + - allocation/vdo_check_point_frequency + - New config options + + config/validate_metadata + + devices/devicesfile_backup_limit + + devices/{device_ids_refresh, device_ids_refresh_checks} + + allocation/pvmove_max_segment_size_mb + + global/sanlock_align_size + + global/{thin_restore_executable, thin_restore_options, cache_restore_executable, cache_restore_options} + + global/lvresize_fs_helper_executable + - Update comments of config options + - global/vdo_disabled_features + - devices/scan_lvs + - log/report_command_log + - log/command_log_selection + - global/system_id_source + - report/headings + - Typo fixes + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ lvm.conf ++++++ --- /var/tmp/diff_new_pack.oWEWNG/_old 2025-12-30 12:01:07.734444526 +0100 +++ /var/tmp/diff_new_pack.oWEWNG/_new 2025-12-30 12:01:07.742444854 +0100 @@ -36,6 +36,19 @@ # This configuration option has an automatic default value. # checks = 1 + # Configuration option config/validate_metadata. + # Allows selecting the level of validation after metadata transformation. + # Validation takes extra CPU time to verify internal consistency. + # Accepted values: + # full + # Do a full metadata validation before disk write. + # none + # Skip any checks (unrecommended, slightly faster). + # + # This configuration option is advanced. + # This configuration option has an automatic default value. + # validate_metadata = "full" + # Configuration option config/abort_on_errors. # Abort the LVM process if a configuration mismatch is found. # This configuration option has an automatic default value. @@ -137,6 +150,16 @@ # This configuration option has an automatic default value. # devicesfile = "system.devices" + # Configuration option devices/devicesfile_backup_limit. + # The max number of backup files to keep in /etc/lvm/devices/backup. + # LVM creates a backup of the devices file each time a new + # version is created, or each time a modification is detected. + # When the max number of backups is reached, the oldest are + # removed to remain at the limit. Set to 0 to disable backups. + # Only the system devices file is backed up. + # This configuration option has an automatic default value. + # devicesfile_backup_limit = 50 + # Configuration option devices/search_for_devnames. # Look outside of the devices file for missing devname entries. # A devname entry is used for a device that does not have a stable @@ -153,6 +176,32 @@ # This configuration option has an automatic default value. # search_for_devnames = "auto" + # Configuration option devices/device_ids_refresh. + # Find PVs on new devices and update the device IDs in the devices file. + # If PVs are restored or moved to a new system with new devices, but + # an old system.devices remains with old device IDs, then search for + # the PVIDs on new devices and update the device IDs in system.devices. + # See device_ids_refresh_check for conditions that trigger the refresh. + # Set to 1 to enable a single automatic refresh attempt when a trigger + # condition is detected. Set to 0 to disable automatic refresh. + # Set to a value between 10 and 600 (in seconds) to enable an extended + # refresh period during which missing PVs will be located using the PVID, + # and the system.devices device ID updated if the PV is found on a new device. + # An extended refresh period may be useful if devices require refresh, + # but are attached to the system some time the initial refresh. + # This configuration option has an automatic default value. + # device_ids_refresh = 10 + + # Configuration option devices/device_ids_refresh_checks. + # Conditions that trigger device_ids_refresh to locate PVIDs on new devices. + # product_uuid: refresh if /sys/devices/virtual/dmi/id/product_uuid does not + # match the value saved in system.devices. + # hostname: refresh if hostname does not match the value saved in system.devices. + # (hostname is used if product_uuid is not available.) + # Remove values from this list to prevent lvm from using them. + # This configuration option has an automatic default value. + # device_ids_refresh_checks = [ "product_uuid", "hostname" ] + # Configuration option devices/filter. # Limit the block devices that are used by LVM commands. # This is a list of regular expressions used to accept or reject block @@ -166,7 +215,7 @@ # device is rejected. Unmatching path names do not affect the accept # or reject decision. If no path names for a device match a pattern, # then the device is accepted. Be careful mixing 'a' and 'r' patterns, - # as the combination might produce unexpected results (test changes.) + # as the combination might produce unexpected results (test changes). # Run vgscan after changing the filter to regenerate the cache. # # Example @@ -211,22 +260,17 @@ # Configuration option devices/sysfs_scan. # Restrict device scanning to block devices appearing in sysfs. # This is a quick way of filtering out block devices that are not - # present on the system. sysfs must be part of the kernel and mounted.) + # present on the system. sysfs must be part of the kernel and mounted). # This configuration option has an automatic default value. # sysfs_scan = 1 # Configuration option devices/scan_lvs. - # Scan LVM LVs for layered PVs, allowing LVs to be used as PVs. - # When 1, LVM will detect PVs layered on LVs, and caution must be - # taken to avoid a host accessing a layered VG that may not belong - # to it, e.g. from a guest image. This generally requires excluding - # the LVs with device filters. Also, when this setting is enabled, - # every LVM command will scan every active LV on the system (unless - # filtered), which can cause performance problems on systems with - # many active LVs. When this setting is 0, LVM will not detect or - # use PVs that exist on LVs, and will not allow a PV to be created on - # an LV. The LVs are ignored using a built in device filter that - # identifies and excludes LVs. + # Allow LVM LVs to be used as PVs. When enabled, LVM commands will + # scan active LVs to look for other PVs. Caution is required to + # avoid using PVs that belong to guest images stored on LVs. + # When enabled, the LVs scanned should be restricted using the + # devices file or the filter. This option does not enable autoactivation + # of layered VGs, which requires editing LVM udev rules (see LVM_PVSCAN_ON_LVS). # This configuration option has an automatic default value. # scan_lvs = 0 @@ -305,7 +349,7 @@ # penalty, e.g. MD chunk size. optimal_io_size is the device's # preferred unit of receiving I/O, e.g. MD stripe width. # minimum_io_size is used if optimal_io_size is undefined (0). - # If md_chunk_alignment is enabled, that detects the optimal_io_size. + # If md_chunk_alignment is enabled, it will detect the optimal_io_size. # default_data_alignment and md_chunk_alignment will be overridden # if they are not aligned with the value detected for this setting. # This setting is overridden by data_alignment and the --dataalignment @@ -466,7 +510,7 @@ # is not claimed incorrectly by other tools because of old signatures # from previous use. The number of signatures that LVM can detect # depends on the detection code that is selected (see - # use_blkid_wiping.) Wiping each detected signature must be confirmed. + # use_blkid_wiping). Wiping each detected signature must be confirmed. # When this setting is disabled, signatures on new LVs are not detected # or erased unless the --wipesignatures option is used directly. # This configuration option has an automatic default value. @@ -498,7 +542,7 @@ # Accepted values: # 0 Automatically detected best available format # 1 Original format - # 2 Improved 2nd. generation format + # 2 Improved second-generation format # # This configuration option has an automatic default value. # cache_metadata_format = 0 @@ -544,19 +588,30 @@ # Configuration option allocation/cache_pool_max_chunks. # The maximum number of chunks in a cache pool. - # For cache target v1.9 the recommended maximumm is 1000000 chunks. + # For cache target v1.9 the recommended maximum is 1000000 chunks. # Using cache pool with more chunks may degrade cache performance. # This configuration option does not have a default value defined. + # Configuration option allocation/pvmove_max_segment_size_mb. + # Maximum size in MiB of segments to mirror at once during pvmove. + # When pvmove needs to move large segments, it will split them into + # smaller chunks of this size, mirror each chunk, and update metadata + # between chunks. This prevents mirroring excessively large amounts + # of data at once. A value of 0 (default) means no limit - the entire + # segment will be mirrored at once. Setting this to e.g. 10240 will + # limit each mirroring operation to 10GiB chunks. + # This configuration option has an automatic default value. + # pvmove_max_segment_size_mb = 0 + # Configuration option allocation/thin_pool_metadata_require_separate_pvs. # Thin pool metadata and data will always use different PVs. # This configuration option has an automatic default value. # thin_pool_metadata_require_separate_pvs = 0 # Configuration option allocation/thin_pool_crop_metadata. - # Older version of lvm2 cropped pool's metadata size to 15.81 GiB. - # This is slightly less then the actual maximum 15.88 GiB. - # For compatibility with older version and use of cropped size set to 1. + # Older versions of lvm2 cropped pool's metadata size to 15.81 GiB. + # This is slightly less than the actual maximum 15.88 GiB. + # For compatibility with older versions and to use the cropped size, set to 1. # This configuration option has an automatic default value. # thin_pool_crop_metadata = 0 @@ -628,13 +683,6 @@ # This configuration option has an automatic default value. # vdo_use_deduplication = 1 - # Configuration option allocation/vdo_use_metadata_hints. - # Enables or disables whether VDO volume should tag its latency-critical - # writes with the REQ_SYNC flag. Some device mapper targets such as dm-raid5 - # process writes with this flag at a higher priority. - # This configuration option has an automatic default value. - # vdo_use_metadata_hints = 1 - # Configuration option allocation/vdo_minimum_io_size. # The minimum IO size for VDO volume to accept, in bytes. # Valid values are 512 or 4096. The recommended value is 4096. @@ -657,11 +705,6 @@ # This configuration option has an automatic default value. # vdo_block_map_period = 16380 - # Configuration option allocation/vdo_check_point_frequency. - # The default check point frequency for VDO volume. - # This configuration option has an automatic default value. - # vdo_check_point_frequency = 0 - # Configuration option allocation/vdo_use_sparse_index. # Enables sparse indexing for VDO volume. # This configuration option has an automatic default value. @@ -738,19 +781,6 @@ # This configuration option has an automatic default value. # vdo_physical_threads = 1 - # Configuration option allocation/vdo_write_policy. - # Specifies the write policy: - # auto - VDO will check the storage device and determine whether it supports flushes. - # If it does, VDO will run in async mode, otherwise it will run in sync mode. - # sync - Writes are acknowledged only after data is stably written. - # This policy is not supported if the underlying storage is not also synchronous. - # async - Writes are acknowledged after data has been cached for writing to stable storage. - # Data which has not been flushed is not guaranteed to persist in this mode. - # async-unsafe - Writes are handled like 'async' but there is no guarantee of the atomicity async provides. - # This mode should only be used for better performance when atomicity is not required. - # This configuration option has an automatic default value. - # vdo_write_policy = "auto" - # Configuration option allocation/vdo_max_discard. # Specified the maximum size of discard bio accepted, in 4096 byte blocks. # I/O requests to a VDO volume are normally split into 4096-byte blocks, @@ -764,7 +794,7 @@ # vdo_max_discard = 1 # Configuration option allocation/vdo_pool_header_size. - # Specified the emptry header size in KiB at the front and end of vdo pool device. + # Specified the empty header size in KiB at the front and end of vdo pool device. # This configuration option has an automatic default value. # vdo_pool_header_size = 512 } @@ -788,6 +818,9 @@ # to define fields to display and sort fields for the log report. # You can also use log/command_log_selection to define selection # criteria used each time the log is reported. + # Note that if report/output_format (or --reportformat command line + # option) is set to json or json_std, then log/report_command_log=1 + # is default. # This configuration option has an automatic default value. # report_command_log = 0 @@ -817,8 +850,9 @@ # define selection criteria for log report on command line directly # using <lvm command> --configreport log -S <selection criteria> # which has precedence over log/command_log_selection setting. - # For more information about selection criteria in general, see - # lvm(8) man page. + # To make all the command log lines visible, use "all" value + # for the command log selection. For more information about selection + # criteria in general, see lvmreport(7) man page. # This configuration option has an automatic default value. # command_log_selection = "!(log_type=status && message=success)" @@ -892,7 +926,7 @@ # Configuration option log/activation. # Log messages during activation. - # Don't use this in low memory situations (can deadlock). + # Do not use this in low memory situations (can deadlock). # This configuration option has an automatic default value. # activation = 0 @@ -1068,7 +1102,7 @@ # Additionally, read-only commands that encounter metadata in need of # repair will still be allowed to proceed exactly as if the repair had # been performed (except for the unchanged vg_seqno). Inappropriate - # use could mess up your system, so seek advice first! + # use could corrupt your system, so seek advice first! # This configuration option has an automatic default value. # metadata_read_only = 0 @@ -1199,10 +1233,20 @@ # This configuration option has an automatic default value. # sanlock_lv_extend = 256 + # Configuration option global/sanlock_align_size. + # The sanlock lease size in MiB to use on disks with a 4K sector size. + # Possible values are 1,2,4,8. The default is 8, which supports up to + # 2000 hosts (and max host_id 2000). Smaller values support smaller + # numbers of max hosts (and max host_ids): 250, 500, 1000, 2000 for + # lease sizes 1,2,4,8. Disks with 512 byte sectors always use 1MiB + # leases and support 2000 hosts, and are not affected by this setting. + # This configuration option has an automatic default value. + # sanlock_align_size = 8 + # Configuration option global/lvmlockctl_kill_command. # The command that lvmlockctl --kill should use to force LVs offline. # The lvmlockctl --kill command is run when a shared VG has lost - # access to locks (e.g. when sanlock has lost access to storage.) + # access to locks (e.g. when sanlock has lost access to storage). # An empty string means that there will be no automatic attempt by # lvmlockctl --kill to forcibly shut down LVs in the VG, and the user # can manually intervene as described in lvmlockd(8). @@ -1212,7 +1256,7 @@ # Configuration option global/thin_check_executable. # The full path to the thin_check command. - # LVM uses this command to check that a thin metadata device is in a + # LVM uses this command to check that a thin pool metadata device is in a # usable state. When a thin pool is activated and after it is # deactivated, this command is run. Activation will only proceed if # the command has an exit status of 0. Set to "" to skip this check. @@ -1236,6 +1280,14 @@ # This configuration option has an automatic default value. # thin_repair_executable = "/usr/sbin/thin_repair" + # Configuration option global/thin_restore_executable. + # The full path to the thin_restore command. + # LVM uses this command to restore generated data for a thin pool metadata device. + # Also see thin_restore_options. + # (See package device-mapper-persistent-data or thin-provisioning-tools) + # This configuration option has an automatic default value. + # thin_restore_executable = "/usr/sbin/thin_restore" + # Configuration option global/thin_check_options. # List of options passed to the thin_check command. # With thin_check version 2.1 or newer you can add the option @@ -1250,6 +1302,11 @@ # This configuration option has an automatic default value. # thin_repair_options = [ "" ] + # Configuration option global/thin_restore_options. + # List of options passed to the thin_restore command. + # This configuration option has an automatic default value. + # thin_restore_options = [ "" ] + # Configuration option global/thin_disabled_features. # Features to not use in the thin driver. # This can be helpful for testing, or to avoid using a feature that is @@ -1298,6 +1355,14 @@ # This configuration option has an automatic default value. # cache_repair_executable = "/usr/sbin/cache_repair" + # Configuration option global/cache_restore_executable. + # The full path to the cache_restore command. + # LVM uses this command to restore generated data for a cache metadata device. + # Also see cache_restore_options. + # (See package device-mapper-persistent-data or thin-provisioning-tools) + # This configuration option has an automatic default value. + # cache_restore_executable = "/usr/sbin/cache_restore" + # Configuration option global/cache_check_options. # List of options passed to the cache_check command. # With cache_check version 5.0 or newer you should include the option @@ -1310,6 +1375,11 @@ # This configuration option has an automatic default value. # cache_repair_options = [ "" ] + # Configuration option global/cache_restore_options. + # List of options passed to the cache_restore command. + # This configuration option has an automatic default value. + # cache_restore_options = [ "" ] + # Configuration option global/vdo_format_executable. # The full path to the vdoformat command. # LVM uses this command to initial data volume for VDO type logical volume @@ -1324,10 +1394,10 @@ # Configuration option global/vdo_disabled_features. # Features to not use in the vdo driver. # This can be helpful for testing, or to avoid using a feature that is - # causing problems. Features include: online_rename + # causing problems. Features include: online_rename, version4 # # Example - # vdo_disabled_features = [ "online_rename" ] + # vdo_disabled_features = [ "online_rename", "version4" ] # # This configuration option does not have a default value defined. @@ -1337,10 +1407,16 @@ # This configuration option has an automatic default value. # fsadm_executable = "/sbin/fsadm" + # Configuration option global/lvresize_fs_helper_executable. + # The full path to the lvresize_fs_helper command. + # LVM uses this command to help with filesystem operations during lvresize. + # This configuration option has an automatic default value. + # lvresize_fs_helper_executable = "/usr/libexec/lvresize_fs_helper" + # Configuration option global/system_id_source. # The method LVM uses to set the local system ID. # Volume Groups can also be given a system ID (by vgcreate, vgchange, - # or vgimport.) A VG on shared storage devices is accessible only to + # or vgimport). A VG on shared storage devices is accessible only to # the host with a matching system ID. See 'man lvmsystemid' for # information on limitations and correct usage. # @@ -1357,8 +1433,9 @@ # Use an LVM-specific derivation of the local machine-id as the # system ID. See 'man machine-id'. # machineid - # Use the contents of the machine-id file to set the system ID - # (appmachineid is recommended.) + # Use the contents of the machine-id file to set the system ID. + # (appmachineid is recommended to avoid exposing the confidential + # machine-id.) # file # Use the contents of another file (system_id_file) to set the # system ID. @@ -1475,13 +1552,15 @@ # Configuration option activation/reserved_stack. # Stack size in KiB to reserve for use while devices are suspended. - # Insufficent reserve risks I/O deadlock during device suspension. + # Insufficient reserve risks I/O deadlock during device suspension. + # Value 0 disables memory locking. # This configuration option has an automatic default value. # reserved_stack = 64 # Configuration option activation/reserved_memory. # Memory size in KiB to reserve for use while devices are suspended. - # Insufficent reserve risks I/O deadlock during device suspension. + # Insufficient reserve risks I/O deadlock during device suspension. + # Value 0 disables memory locking. # This configuration option has an automatic default value. # reserved_memory = 8192 @@ -1616,7 +1695,7 @@ # This includes LVs that have the following segment types: # raid1, raid4, raid5*, and raid6*. # If a device in the LV fails, the policy determines the steps - # performed by dmeventd automatically, and the steps perfomed by the + # performed by dmeventd automatically, and the steps performed by the # manual command lvconvert --repair --use-policies. # Automatic handling requires dmeventd to be monitoring the LV. # @@ -1640,7 +1719,7 @@ # (copies) and a mirror log. A disk log ensures that a mirror LV does # not need to be re-synced (all copies made the same) every time a # machine reboots or crashes. If a device in the LV fails, this policy - # determines the steps perfomed by dmeventd automatically, and the steps + # determines the steps performed by dmeventd automatically, and the steps # performed by the manual command lvconvert --repair --use-policies. # Automatic handling requires dmeventd to be monitoring the LV. # @@ -1682,7 +1761,7 @@ # Configuration option activation/snapshot_autoextend_threshold. # Auto-extend a snapshot when its usage exceeds this percent. # Setting this to 100 disables automatic extension. - # The minimum value is 50 (a smaller value is treated as 50.) + # The minimum value is 50 (a smaller value is treated as 50). # Also see snapshot_autoextend_percent. # Automatic extension requires dmeventd to be monitoring the LV. # @@ -1712,7 +1791,7 @@ # Configuration option activation/thin_pool_autoextend_threshold. # Auto-extend a thin pool when its usage exceeds this percent. # Setting this to 100 disables automatic extension. - # The minimum value is 50 (a smaller value is treated as 50.) + # The minimum value is 50 (a smaller value is treated as 50). # Also see thin_pool_autoextend_percent. # Automatic extension requires dmeventd to be monitoring the LV. # @@ -1742,7 +1821,7 @@ # Configuration option activation/vdo_pool_autoextend_threshold. # Auto-extend a VDO pool when its usage exceeds this percent. # Setting this to 100 disables automatic extension. - # The minimum value is 50 (a smaller value is treated as 50.) + # The minimum value is 50 (a smaller value is treated as 50). # Also see vdo_pool_autoextend_percent. # Automatic extension requires dmeventd to be monitoring the LV. # @@ -1802,7 +1881,7 @@ # Configuration option activation/polling_interval. # Check pvmove or lvconvert progress at this interval (seconds). # When pvmove or lvconvert must wait for the kernel to finish - # synchronising or merging data, they check and report progress at + # synchronizing or merging data, they check and report progress at # intervals of this number of seconds. If this is set to 0 and there # is only one thing to wait for, there are no progress reports, but # the process is awoken immediately once the operation is complete. @@ -1830,7 +1909,7 @@ # uses are present. Other PVs in the Volume Group may be missing. # degraded # Like complete, but additionally RAID LVs of segment type raid1, - # raid4, raid5, radid6 and raid10 will be activated if there is no + # raid4, raid5, raid6 and raid10 will be activated if there is no # data loss, i.e. they have sufficient redundancy to present the # entire addressable range of the Logical Volume. # partial @@ -1955,7 +2034,7 @@ # If there is more than one report per command, then the format # is applied for all reports. You can also change output format # directly on command line using --reportformat option which - # has precedence over log/output_format setting. + # has precedence over report/output_format setting. # Accepted values: # basic # Original format with columns and rows. If there is more than @@ -1969,12 +2048,13 @@ # - it does not use double quotes around numeric values, # - it uses 'null' for undefined numeric values, # - it prints string list as proper JSON array of strings instead of a single string. + # Note that if json or json_std output format is used, then log/command_log_report=1 is default. # This configuration option has an automatic default value. # output_format = "basic" # Configuration option report/compact_output. # Do not print empty values for all report fields. - # If enabled, all fields that don't have a value set for any of the + # If enabled, all fields that do not have a value set for any of the # rows reported are skipped and not printed. Compact output is # applicable only if report/buffered is enabled. If you need to # compact only specified fields, use compact_output=0 and define @@ -1984,7 +2064,7 @@ # Configuration option report/compact_output_cols. # Do not print empty values for specified report fields. - # If defined, specified fields that don't have a value set for any + # If defined, specified fields that do not have a value set for any # of the rows reported are skipped and not printed. Compact output # is applicable only if report/buffered is enabled. If you need to # compact all fields, use compact_output=1 instead in which case @@ -2008,7 +2088,11 @@ # buffered = 1 # Configuration option report/headings. - # Show headings for columns on report. + # Format of LVM command's report output headings. + # Accepted values: + # 0 no headings, + # 1 headings with column abbreviations, + # 2 headings with full column names. # This configuration option has an automatic default value. # headings = 1 @@ -2087,7 +2171,7 @@ # %F # Equivalent to %Y-%m-%d (the ISO 8601 date format). # %G - # The ISO 8601 week-based year with century as adecimal number. + # The ISO 8601 week-based year with century as a decimal number. # The 4-digit year corresponding to the ISO week number (see %V). # This has the same format and value as %Y, except that if the # ISO week number belongs to the previous or next year, that year
