This is a list of API changes in libblockdev 3.0 with suggested replacements.
bd_switch_init_checks() has been removed. Checks for runtime dependencies during libblockdev initialization are now disabled and plugins will be loaded even if a runtime dependency is missing.
bd_"plugin"_check_deps functions have been removed from all plugins. Use
bd_"plugin"_is_tech_avail to check for plugin dependencies.
bd_lvm_data_lv_name() has been removed, use
data_lv from BDLVMLVdata instead.
bd_lvm_metadadata_lv_name() has been removed, use
metadata_lv from BDLVMLVdata instead.
BD_LVM_MAX_LV_SIZE constant has been removed, use
Multiple thinpool and cache metadata size related constants have been removed without replacement. We recommend using functions like
bd_lvm_lvactivate() has a new parameter
FALSE to preserve the original behaviour.
bd_crypto_luks_uuid() has been removed, use
uuid from BDCryptoLUKSInfo instead.
bd_crypto_luks_get_metadata_size() has been removed, use
LUKS2-specific functions were removed. The "generic" LUKS functions which now support both LUKSv1 and LUKSv2 should be used instead.
bd_crypto_luks_open_keyring has been removed,
bd_crypto_luks_open with the keyring context (see below)
can be used instead.
bd_crypto_tc_open_full has been removed,
bd_crypto_tc_open can be used instead.
bd_crypto_tc_open arguments have been changed to match the "full" function.
Functions that allowed using arbitrary binary data for passphrases were removed. The "generic" functions should be used instead,
see the key slot context information below.
All functions that require some type of passphrase or key as an input now expect
This is a private opaque context that needs to be set by one of the
based on the type of the context required.
bd_nvdimm_namepace_get_supported_sector_sizes has been removed, use
bd_fs_wipe have new parameter
that allows controlling whether the signatures will be removed from a mounted device or not. Use
TRUE to preserve the original behaviour.
Following functions have a new parameter
fstype that allows to skip scanning the device
for signature. Use
NULL to preserve the original behaviour.
bd_fs_..._wipe functions have been removed. Use
bd_fs_xfs_check have a new parameter
that allows specifying extra options for the fsck tools. This makes the functionality consistent with the other filesystems.
BDFsResizeFlags enum was renamed to
BDFsError enum was renamed to
The part plugin has been rewritten to use libfdisk library instead of libparted. The following functions, enums and definitions related to partition and disk flags have been removed.
bd_part_set_part_idfunctions to set partition GUID (GPT) or ID (MSDOS) to set the required type/id instead.
bd_part_set_part_attributes have been added to allow controlling the bootable flag (MSDOS) and partition attributes (GPT).
bd_part_get_part_id function has been removed. The partition id parameter is now available in
bd_loop_setup_from_fd has a new parameter
0 to preserve the original behaviour.
bd_loop_get_autoclear have been removed. Use
Support for DM RAID (
BD_DM_TECH_RAID technology) was removed from the plugin. Following functions were removed without replacement:
bitmap argument of the
bd_md_create function now accepts arbitrary string instead of a boolean value.
Previous value of
FALSE is now represented by
NULL, i.e. letting
mdadm decide itself whether to create an internal bitmap or not.