Tags give the ability to mark specific points in history as being important
-
v2_03_11
3e8bd8d1 · ·Release 2.03.11 - Improvements to VDO, writecache and integrity volumes. - And lot of bugfixes.
-
v2_03_10
4d9f0606 · ·Release 2.03.10 - Add integrity with raid capability. - Add writecache and integrity support to lvmdbusd. - Zero pool metadata on allocation (disable with allocation/zero_metadata=0). - Failure in zeroing or wiping will fail command (bypass with -Zn, -Wn). - Bug fixes.
-
v2_03_09
e1c2b412 · ·Release 2.03.09 - Fixed compilation errors with GCC 10. - Fixed few writecache and pvck releated bugs. - Fixed busy loop in dmeventd.
-
-
v2_03_08
b9752d71 · ·Release 2.03.08 - IMPORTANT: Prohibit reshape of stacked raid LVs to prevent corruption. - Improved handling of writecache and VDO volumes.
-
v2_03_07
3d7f7556 · ·Release 2.03.07 - Subcommand in vgck for repairing headers and metadata. - Fix resize of thin-pool with data and metadata of different segtype. - Fix activation order when removing merged snapshot. - Experimental VDO support for lvmdbusd.
-
v2_03_06
b9391b1b · ·Release 2.03.06 NOTABLE CHANGES: Prevent creating VGs with PVs with different logical block sizes. Setting 'devices/allow_mixed_block_sizes' to 1 keeps the old behavior but may lead to data corruption. Improvements to cache volumes handling.
-
v2_02_186
4e576148 · ·Release 2.02.186 Bug fix release. Notable changes: Fix not working RAID repair. Allow --stripes/--stripesize in 'mirror' conversions. Disable incorrect linear to mirror of active LV in cluster VG.
-
v2_03_05
60bd9e84 · ·Release 2.03.05 Change when and how VG metadata are repaired: - Move metadata repairs from VG reading to VG writing. - Report/display/scan commands that read VGs will no longer write/repair. - Improve VG reading to work if one good copy of metadata is found. - Add vgck --updatemetadata command that will repair metadata problems. MD component detection improvements: - Add config setting md_component_checks to control MD component checks. - Add end of device MD component checks when dev has no udev info.
-
-
v2_03_03
cb6277aa · ·Release 2.03.03 Bugfix and Feature Release Notable changes: - Add pvck --dump option to extract metadata from disk. - New scan_lvs option, defaultingo to 0 so LVs are not scanned for PVs.
-
v2_02_185
3aeff09b · ·Release 2.02.185 Bug fix release. Notable changes: Use pselect in daemons to avoid race during shutdown causing hanging process. Automatically grow _tmeta when thin data gets too big for the metadata volume. Grow _pmspare when extending _tmeta.
-
v2_02_184
7cbee7e9 · ·Release 2.02.184 Bug fix release. Notable changes: New scan_lvs option with default setting 0, which filters out logical volumes from scanning for PV headers. Fix issue with cleaner policy not working with large cache volumes where migration threshold was smaller than chunk size.
-
v2_03_02
5230a1a9 · ·Release 2.03.02 Bugfix release. Among other things, this resolves following issues: * Fix (de)activation of RaidLVs with visible SubLVs, * Prohibit mirrored 'mirror' log via lvcreate and lvconvert, * Use sync io if async io_setup fails, or use_aio=0 is set in config, * Fix libdevmapper-event library linking.
-
v2_02_183
f5ea02ff · ·Release 2.02.183 Bug fix release. Use sync IO when AIO fails due to system reaching the aio request limit. Add global/use_aio configuration option to disable aio. MD RAID verion 0.90 devices are filtered out preventing them to be seen as duplicate PVs. Fix regression in dmstats resulting in no output.
-
-
-
-
-
v2_03_01
913c2891 · ·Release 2.03.01 Important bugfix release. This addresses an issue introduced in 2.02.178 where concurrent write at the start of the logical volume and at end of VG metadata might result in overwriting the LV data.