summaryrefslogtreecommitdiff
path: root/WHATS_NEW_DM
Commit message (Collapse)AuthorAgeFilesLines
* post-releaseMarian Csontos2023-04-211-0/+3
|
* pre-releasev2_03_21Marian Csontos2023-04-211-1/+1
|
* post-releaseMarian Csontos2023-03-211-0/+3
|
* pre-releasev2_03_20Marian Csontos2023-03-211-2/+2
|
* post-releaseMarian Csontos2023-02-211-0/+3
|
* pre-releasev2_03_19Marian Csontos2023-02-211-1/+1
|
* WHATS_NEW_DM: updateZdenek Kabelac2023-02-131-0/+1
|
* udev: import previous results of blkid when in suspended stateYu Watanabe2023-02-071-0/+1
| | | | | | | | | | | | | | | | Follow-up for e10f67e91728f1e576803df884049ecbd92874d0. The commit e10f67e91728f1e576803df884049ecbd92874d0 tries to keep device node symlinks even if the device is in the suspended state. However, necessary properties that may previously obtained by the blkid command were not imported at least in the .rules file. So, unless ID_FS_xyz properties are imported by another earlier .rules file, the device node symlinks are still lost when event is processed in the suspended state. Let's explicitly import the necessary properties. RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=2158628 GHPR: https://github.com/lvmteam/lvm2/pull/105
* udev: remove rule for explicit creation of /dev/mapper/controlPeter Rajnoha2023-02-021-0/+1
| | | | | | | | | | | | We used KERNEL=="device-mapper", NAME="/dev/mapper/control" udev rule to create the /dev/mapper/control file. The "NAME" rule should be only used to rename network devices, otherwise udev issues a warning message. The device-mapper driver has proper DEVNAME=/dev/mapper/control propagated in the uevent environment when it is loaded so we don't need further instruction on where to create the node - udev knows already. Also, these days, it is created directly by kernel inside devtmpfs. This makes the NAME="/dev/mapper/control" rule completely obsolete.
* post-releaseMarian Csontos2023-01-031-0/+3
|
* pre-releaseMarian Csontos2022-12-221-1/+1
|
* dmsetup: fix udev event handling for createZdenek Kabelac2022-11-251-0/+1
| | | | | | | | | | | | | | | | | | | | With newer kernels (>5.13) DM_CREATE no longer generates uevent for DM devices without table. There are even no sysfs block device entries in such case, although device has asigned major:minor and it is being listed by 'dmsetup info'. So this patch calculates amount of 'table' lines and in case no table line comes from cmdline or stdin - waiting on cookie is avoided generically instead of disabling just case with option --notable - which then also skipped handling of an option --addnodeoncreate (which is however historical and should be avoided) As a result there should be no leaking udev cookies and endlessly waiting commands like this: dmsetup create mytestdev </dev/null
* post-releaseMarian Csontos2022-11-101-0/+3
|
* pre-releasev2_03_17Marian Csontos2022-11-101-2/+2
|
* WHATS_NEW: updatePeter Rajnoha2022-08-111-0/+1
|
* post-releaseMarian Csontos2022-05-181-0/+3
|
* pre-releasev2_03_16Marian Csontos2022-05-181-2/+2
|
* post-releaseMarian Csontos2022-02-071-0/+3
|
* pre-releasev2_03_15Marian Csontos2022-02-071-2/+2
|
* libdm: unmangling UUID for DM_DEVICE_LISTZdenek Kabelac2021-12-201-0/+1
| | | | | Properly unmangle UUID if they are provided as result of DM_DEVICE_LIST ioctl on newer linux kernels.
* post-releaseMarian Csontos2021-10-201-0/+3
|
* pre-releasev2_03_14Marian Csontos2021-10-201-2/+2
|
* libdm: dmsetup measure support for IMAAlasdair G Kergon2021-09-231-0/+1
| | | | | | | Add support for DM_IMA_MEASUREMENT_FLAG with DM_TABLE_STATUS_CMD. This feature requires DM version 4.45 (5.15+ kernels)
* libdm: support DM_NAME_LIST_FLAGZdenek Kabelac2021-09-231-0/+1
| | | | | | | | | | | | | | | | | Kernel patch 8b638081bd4520f63db1defc660666ec5f65bc15 introduced support to return UUID in DM_LIST_DEVICES_CMD. Useful when asking for UUID of each device where the list could be now returned directly with NAME && UUID for each device. Returning UUID is done in backward-compatible way. There's one unused 32-bit word value after the event number. This patch sets the bit DM_NAME_LIST_FLAG_HAS_UUID if UUID is present and DM_NAME_LIST_FLAG_DOESNT_HAVE_UUID if it isn't (if none of these bits is set, then we have an old kernel that doesn't support returning UUIDs). The UUID is stored after this word. The 'next' value is updated to point after the UUID, so that old version of libdevmapper will skip the UUID without attempting to interpret it.
* libdm: enhance tracking of activated LVsZdenek Kabelac2021-09-131-0/+1
| | | | | | Existing mechanism was not able to trace root volume issue. Simplify the functionality by using simply using activated flag and trace the dtree in reverse order.
* cache: fix parentheses for migration_thresholdZdenek Kabelac2021-09-131-0/+1
| | | | | | | | | | | When generating table line for cache target line, the estimation of added arguments was incorrectly calculated as the evaluation order of "?" is made after "+". However the result was 'masked' by the Reported-by: Jian Cai jcai19
* post-releaseMarian Csontos2021-08-111-0/+3
|
* pre-releasev2_03_13Marian Csontos2021-08-111-2/+2
|
* post-releaseMarian Csontos2021-05-071-0/+3
|
* pre-releasev2_03_12Marian Csontos2021-05-071-2/+2
|
* WHATS_NEW: updatesZdenek Kabelac2021-04-121-0/+1
|
* WHATS_NEW: updatesZdenek Kabelac2021-04-061-0/+1
|
* all: fix typosSamanta Navarro2021-03-301-1/+1
|
* libdm: add dm_tree_node_add_thin_pool_target_v1Zdenek Kabelac2021-02-011-0/+1
| | | | Supports thin-pool without crop.
* post-releaseMarian Csontos2021-01-081-0/+3
|
* pre-releasev2_03_11Marian Csontos2021-01-081-2/+2
|
* dm: remove created devices on error pathZdenek Kabelac2020-10-191-0/+1
| | | | | | | | DM tree keeps track of created device while preloading a device tree. When fail occures during such preload, it will now try to remove all created and preloaded device. This makes it easier to maintain stacking of device, since we do not need to check in-depth for existance of all possible created devices during the failure.
* post-releaseMarian Csontos2020-08-091-0/+3
|
* pre-releasev2_03_10Marian Csontos2020-08-091-2/+2
|
* blkdeactivate: add support for VDO in blkdeactivate scriptPeter Rajnoha2020-04-091-0/+1
| | | | | | Make it possible to tear down VDO volumes with blkdeactivate if VDO is part of a device stack (and if VDO binary is installed). Also, support optional -o|--vdooptions configfile=file.
* post-releaseMarian Csontos2020-03-261-0/+3
|
* pre-releasev2_03_09Marian Csontos2020-03-261-2/+2
|
* WHATS_NEW_DM: updateZdenek Kabelac2020-03-051-0/+2
|
* post-releaseMarian Csontos2020-02-111-0/+3
|
* pre-releasev2_03_08Marian Csontos2020-02-111-1/+1
|
* libdm: support device RELOAD with maj:min and devname setZdenek Kabelac2019-12-101-0/+1
| | | | | | | | | | When devices are created - we were not giving meaning error messages when the failure happened on 'reload' part of creation. With this patch we are now able to report both name and major:minor. Enhancment is most visible with 'crypto' devices, which are using 'secure' memory erase bit.
* post-releaseMarian Csontos2019-11-301-0/+3
|
* pre-releasev2_03_07Marian Csontos2019-11-301-2/+2
|
* post-releaseMarian Csontos2019-10-231-0/+3
|
* pre-releasev2_03_06Marian Csontos2019-10-231-2/+2
|
View Lorry Controller Status