shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-21 13:34:40 +03:00
Code Releases Activity
3d26bde1c0
lvm2/lib/Makefile.in

148 lines
3.3 KiB
Makefile
Raw Normal View History

Makefiles & autoconf.
2001-09-21 16:37:43 +04:00
#
Update copyright notices.
2004-03-30 23:35:44 +04:00
# Copyright (C) 2001-2004 Sistina Software, Inc. All rights reserved.
cache: New 'cachepool' segment type This patch adds the new cachepool segment type - the first of two necessary to eventually create 'cache' logical volumes. In addition to the new segment type, updates to makefiles, configure files, the lv_segment struct, and some necessary libdevmapper flags. The cachepool is the LV and corresponding segment type that will hold all information pertinent to the cache itself - it's size, cachemode, cache policy, core arguments (like migration_threshold), etc.
2014-01-27 15:27:16 +04:00
# Copyright (C) 2004-2014 Red Hat, Inc. All rights reserved.
Makefiles & autoconf.
2001-09-21 16:37:43 +04:00
#
Correct typo in comments: s/is part of the LVM2/is part of LVM2/. Signed-off-by: Jim Meyering <jim@meyering.net> Author: Jim Meyering <jim@meyering.net>
2007-09-21 14:16:45 +04:00
# This file is part of LVM2.
Makefiles & autoconf.
2001-09-21 16:37:43 +04:00
#
Update copyright notices.
2004-03-30 23:35:44 +04:00
# This copyrighted material is made available to anyone wishing to use,
# modify, copy, or redistribute it subject to the terms and conditions
# of the GNU General Public License v.2.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software Foundation,
doc: change fsf address Hmm rpmlint suggest fsf is using a different address these days, so lets keep it up-to-date
2016-01-21 13:49:46 +03:00
# Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Makefiles & autoconf.
2001-09-21 16:37:43 +04:00
srcdir = @srcdir@
top_srcdir = @top_srcdir@
Allow for a build directory separate from the source.
2009-10-02 23:10:31 +04:00
top_builddir = @top_builddir@
make: cflow target works again Restored 'make cflow' functinality. Produces some quick referece of function chaining and usage.
2021-03-20 01:10:55 +03:00
abs_srcdir = @abs_srcdir@
Makefiles & autoconf.
2001-09-21 16:37:43 +04:00
Update makefiles (incl. cmdlib).
2004-03-26 16:21:12 +03:00
SOURCES =\
vgchange
2001-10-16 20:25:28 +04:00
activate/activate.c \
Another sync point - numerous fixes & clean ups.
2003-07-05 02:34:56 +04:00
cache/lvmcache.c \
Add dm-writecache support dm-writecache is used like dm-cache with a standard LV as the cache. $ lvcreate -n main -L 128M -an foo /dev/loop0 $ lvcreate -n fast -L 32M -an foo /dev/pmem0 $ lvconvert --type writecache --cachepool fast foo/main $ lvs -a foo -o+devices LV VG Attr LSize Origin Devices [fast] foo -wi------- 32.00m /dev/pmem0(0) main foo Cwi------- 128.00m [main_wcorig] main_wcorig(0) [main_wcorig] foo -wi------- 128.00m /dev/loop0(0) $ lvchange -ay foo/main $ dmsetup table foo-main_wcorig: 0 262144 linear 7:0 2048 foo-main: 0 262144 writecache p 253:4 253:3 4096 0 foo-fast: 0 65536 linear 259:0 2048 $ lvchange -an foo/main $ lvconvert --splitcache foo/main $ lvs -a foo -o+devices LV VG Attr LSize Devices fast foo -wi------- 32.00m /dev/pmem0(0) main foo -wi------- 128.00m /dev/loop0(0)
2018-08-27 22:53:09 +03:00
writecache/writecache.c \
Allow dm-integrity to be used for raid images dm-integrity stores checksums of the data written to an LV, and returns an error if data read from the LV does not match the previously saved checksum. When used on raid images, dm-raid will correct the error by reading the block from another image, and the device user sees no error. The integrity metadata (checksums) are stored on an internal LV allocated by lvm for each linear image. The internal LV is allocated on the same PV as the image. Create a raid LV with an integrity layer over each raid image (for raid levels 1,4,5,6,10): lvcreate --type raidN --raidintegrity y [options] Add an integrity layer to images of an existing raid LV: lvconvert --raidintegrity y LV Remove the integrity layer from images of a raid LV: lvconvert --raidintegrity n LV Settings Use --raidintegritymode journal|bitmap (journal is default) to configure the method used by dm-integrity to ensure crash consistency. Initialization When integrity is added to an LV, the kernel needs to initialize the integrity metadata/checksums for all blocks in the LV. The data corruption checking performed by dm-integrity will only operate on areas of the LV that are already initialized. The progress of integrity initialization is reported by the "syncpercent" LV reporting field (and under the Cpy%Sync lvs column.) Example: create a raid1 LV with integrity: $ lvcreate --type raid1 -m1 --raidintegrity y -n rr -L1G foo Creating integrity metadata LV rr_rimage_0_imeta with size 12.00 MiB. Logical volume "rr_rimage_0_imeta" created. Creating integrity metadata LV rr_rimage_1_imeta with size 12.00 MiB. Logical volume "rr_rimage_1_imeta" created. Logical volume "rr" created. $ lvs -a foo LV VG Attr LSize Origin Cpy%Sync rr foo rwi-a-r--- 1.00g 4.93 [rr_rimage_0] foo gwi-aor--- 1.00g [rr_rimage_0_iorig] 41.02 [rr_rimage_0_imeta] foo ewi-ao---- 12.00m [rr_rimage_0_iorig] foo -wi-ao---- 1.00g [rr_rimage_1] foo gwi-aor--- 1.00g [rr_rimage_1_iorig] 39.45 [rr_rimage_1_imeta] foo ewi-ao---- 12.00m [rr_rimage_1_iorig] foo -wi-ao---- 1.00g [rr_rmeta_0] foo ewi-aor--- 4.00m [rr_rmeta_1] foo ewi-aor--- 4.00m
2019-11-21 01:07:27 +03:00
integrity/integrity.c \
build: remove --with-{snapshots,mirrors,raid,thin,cache} options from ./configure It now behaves as if the were all set as 'internal'
2018-04-30 12:11:23 +03:00
cache_segtype/cache.c \
Some new features.
2002-11-18 17:04:08 +03:00
commands/toolcontext.c \
Makefiles & autoconf.
2001-09-21 16:37:43 +04:00
config/config.c \
o Trivial binary tree
2001-10-25 15:38:19 +04:00
datastruct/btree.c \
Extract some common functions.
2003-09-18 00:35:57 +04:00
datastruct/str_list.c \
[lib/device/bcache] Tweaks after Kabi's review
2018-01-30 15:13:48 +03:00
device/bcache.c \
bcache: Move the utils to a separate file. This makes it clearer that they don't access the cache internals.
2018-05-03 11:34:41 +03:00
device/bcache-utils.c \
o added dev-cache.c, dev-io and sorted source files alphabetically
2001-10-03 16:46:17 +04:00
device/dev-cache.c \
device usage based on devices file The LVM devices file lists devices that lvm can use. The default file is /etc/lvm/devices/system.devices, and the lvmdevices(8) command is used to add or remove device entries. If the file does not exist, or if lvm.conf includes use_devicesfile=0, then lvm will not use a devices file. When the devices file is in use, the regex filter is not used, and the filter settings in lvm.conf or on the command line are ignored. LVM records devices in the devices file using hardware-specific IDs, such as the WWID, and attempts to use subsystem-specific IDs for virtual device types. These device IDs are also written in the VG metadata. When no hardware or virtual ID is available, lvm falls back using the unstable device name as the device ID. When devnames are used, lvm performs extra scanning to find devices if their devname changes, e.g. after reboot. When proper device IDs are used, an lvm command will not look at devices outside the devices file, but when devnames are used as a fallback, lvm will scan devices outside the devices file to locate PVs on renamed devices. A config setting search_for_devnames can be used to control the scanning for renamed devname entries. Related to the devices file, the new command option --devices <devnames> allows a list of devices to be specified for the command to use, overriding the devices file. The listed devices act as a sort of devices file in terms of limiting which devices lvm will see and use. Devices that are not listed will appear to be missing to the lvm command. Multiple devices files can be kept in /etc/lvm/devices, which allows lvm to be used with different sets of devices, e.g. system devices do not need to be exposed to a specific application, and the application can use lvm on its own set of devices that are not exposed to the system. The option --devicesfile <filename> is used to select the devices file to use with the command. Without the option set, the default system devices file is used. Setting --devicesfile "" causes lvm to not use a devices file. An existing, empty devices file means lvm will see no devices. The new command vgimportdevices adds PVs from a VG to the devices file and updates the VG metadata to include the device IDs. vgimportdevices -a will import all VGs into the system devices file. LVM commands run by dmeventd not use a devices file by default, and will look at all devices on the system. A devices file can be created for dmeventd (/etc/lvm/devices/dmeventd.devices) If this file exists, lvm commands run by dmeventd will use it. Internal implementaion: - device_ids_read - read the devices file . add struct dev_use (du) to cmd->use_devices for each devices file entry - dev_cache_scan - get /dev entries . add struct device (dev) to dev_cache for each device on the system - device_ids_match - match devices file entries to /dev entries . match each du on cmd->use_devices to a dev in dev_cache, using device ID . on match, set du->dev, dev->id, dev->flags MATCHED_USE_ID - label_scan - read lvm headers and metadata from devices . filters are applied, those that do not need data from the device . filter-deviceid skips devs without MATCHED_USE_ID, i.e. skips /dev entries that are not listed in the devices file . read lvm label from dev . filters are applied, those that use data from the device . read lvm metadata from dev . add info/vginfo structs for PVs/VGs (info is "lvmcache") - device_ids_find_renamed_devs - handle devices with unstable devname ID where devname changed . this step only needed when devs do not have proper device IDs, and their dev names change, e.g. after reboot sdb becomes sdc. . detect incorrect match because PVID in the devices file entry does not match the PVID found when the device was read above . undo incorrect match between du and dev above . search system devices for new location of PVID . update devices file with new devnames for PVIDs on renamed devices . label_scan the renamed devs - continue with command processing
2020-06-23 21:25:41 +03:00
device/device_id.c \
device: add infrastructure to support external device info
2014-12-12 14:55:41 +03:00
device/dev-ext.c \
o added dev-cache.c, dev-io and sorted source files alphabetically
2001-10-03 16:46:17 +04:00
device/dev-io.c \
Separate out md superblock detection code.
2004-11-18 23:02:21 +03:00
device/dev-md.c \
Detect and wipe swap signatures in pvcreate.
2009-03-17 16:59:56 +03:00
device/dev-swap.c \
refactor: move lib/device/device.c -> lib/device/dev-type.c
2013-06-12 13:53:55 +04:00
device/dev-type.c \
Detect LUKS signature in pvcreate One shiny day we should use libblkid here. But now using LUKS is very common together with LVM and pvcreate destroys LUKS completely. So for user's convenience, try to detect LUKS signature and allow abort.
2010-08-20 03:08:18 +04:00
device/dev-luks.c \
pvcreate: don't support unpartitioned DASD devices with CDL formatted The former patch(dab3ebce4c7) is a little bit strict. For example, it is OK to create PV on unpartitioned DASD devices with LDL formatted. So after lvm version containing the patch, LVs created on those devices could not be found. Signed-off-by: Lidong Zhong <lzhong@suse.com>
2015-10-12 10:09:11 +03:00
device/dev-dasd.c \
devices: ignore lvm1 and pool devices
2018-05-01 22:32:15 +03:00
device/dev-lvm1-pool.c \
o composite filter that allows us to merge filters. Think of it as &&'ing filters in order. eg, f = composite_filter_create(2, regex_filter, persistent_filter); ownership of the filters passes, they will be destroyed when f's destroy method is called.
2001-10-22 18:39:12 +04:00
display/display.c \
Add --type to lvcreate/resize. Add virtual segment types, zero and error. A large sparse device can be constructed as a writeable snapshot of a large zero device.
2004-05-11 20:01:58 +04:00
error/errseg.c \
Handle metadata with unknown segment types more gracefully.
2009-10-16 21:41:49 +04:00
unknown/unknown.c \
o composite filter that allows us to merge filters. Think of it as &&'ing filters in order. eg, f = composite_filter_create(2, regex_filter, persistent_filter); ownership of the filters passes, they will be destroyed when f's destroy method is called.
2001-10-22 18:39:12 +04:00
filters/filter-composite.c \
o Filter which caches valid devices in a file. Pass in init == 1 to the constructor if you want it to ignore the existing cache and check every device again (eg, vgscan, pvscan).
2001-10-22 18:14:00 +04:00
filters/filter-persistent.c \
filters/filter-regex.c \
Sysfs block device filtering option for 2.6.
2004-02-13 17:46:04 +03:00
filters/filter-sysfs.c \
Set devices/md_component_detection = 1 to ignore devices containing md superblocks. [Luca Berra]
2004-04-16 20:12:04 +04:00
filters/filter-md.c \
filters: add firmware RAID filter Just like MD filtering that detects components of software RAID (md), add detection for firmware RAID. We're not adding any native code to detect this - there are lots of firmware RAIDs out there which is just out of LVM scope. However, with current changes with which we're able to get device info from external sources (e.g. external_device_info_source="udev"), we can do this easily if the external device status source has this kind of information - which is the case of "udev" source where the results of blkid scans are stored. This detection should cover all firmware RAIDs that blkid can detect and which are identified as: ID_FS_TYPE = {adaptec,ddf,hpt45x,hpt37x,isw,jmicron,lsi_mega,nvidia,promise_fasttrack,silicon_medley,via}_raid_member
2014-09-09 17:05:57 +04:00
filters/filter-fwraid.c \
Do not scan device if it is part of active multipath. Add filter which tries to check if scanned device is part of active multipath. Firstly, only SCSI major number devices are handled in filter. Then it checks if device has exactly one holder (in sysfs) and if it is device-mapper device and DM-UUID is prefixed by "MPATH-". If so, this device is filtered out. The whole filter can be switched off by setting mpath_component_detection in lvm.conf. https://bugzilla.redhat.com/show_bug.cgi?id=597010 Signed-off-by: Milan Broz <mbroz@redhat.com>
2011-11-11 19:11:08 +04:00
filters/filter-mpath.c \
filters: check for mpath before opening devs Split out the partitioned device filter that needs to open the device and move the multipath filter in front of it. When a device is multipathed, sending I/O to the underlying paths may cause problems, the most obvious being I/O errors visible to lvm if a path is down. Revert the incorrect <backtrace> messages added when a device doesn't pass a filter. Log each filter initialisation to show sequence. Avoid duplicate 'Using $device' debug messages.
2013-08-14 02:26:58 +04:00
filters/filter-partitioned.c \
filters/filter-type.c \
filters: add "usable device" filter Usable device filter is responsible for filtering out unusable DM devices. The filter has 3 modes of operation: - FILTER_MODE_NO_LVMETAD: When this mode is used, we check DM device usability by looking: - whether device is empty - whether device is blocked - whether device is suspended (only on devices/ignore_suspended_devices=1) - whether device uses an error target - whether device name/uuid is reserved - FILTER_MODE_PRE_LVMETAD: When this mode is used, we check DM device usability by looking: - whether device is empty - whether device is suspended (only on devices/ignore_suspended_devices=1) - whether device uses an error target - whether device name/uuid is reserved - FILTER_MODE_POST_LVMETAD: When this mode is used, we check DM device usability by looking: - whether device is blocked - whether device is suspended (only on devices/ignore_suspended_devices=1) These modes will be used by subsequent patch to create different instances of this filter, depending on lvmetad use.
2014-09-23 14:49:01 +04:00
filters/filter-usable.c \
vgimportclone: add native command This is cleaner and more efficient than the script. The args and usage are unchanged.
2016-05-25 21:57:33 +03:00
filters/filter-internal.c \
devices: ignore lvm1 and pool devices
2018-05-01 22:32:15 +03:00
filters/filter-signature.c \
device usage based on devices file The LVM devices file lists devices that lvm can use. The default file is /etc/lvm/devices/system.devices, and the lvmdevices(8) command is used to add or remove device entries. If the file does not exist, or if lvm.conf includes use_devicesfile=0, then lvm will not use a devices file. When the devices file is in use, the regex filter is not used, and the filter settings in lvm.conf or on the command line are ignored. LVM records devices in the devices file using hardware-specific IDs, such as the WWID, and attempts to use subsystem-specific IDs for virtual device types. These device IDs are also written in the VG metadata. When no hardware or virtual ID is available, lvm falls back using the unstable device name as the device ID. When devnames are used, lvm performs extra scanning to find devices if their devname changes, e.g. after reboot. When proper device IDs are used, an lvm command will not look at devices outside the devices file, but when devnames are used as a fallback, lvm will scan devices outside the devices file to locate PVs on renamed devices. A config setting search_for_devnames can be used to control the scanning for renamed devname entries. Related to the devices file, the new command option --devices <devnames> allows a list of devices to be specified for the command to use, overriding the devices file. The listed devices act as a sort of devices file in terms of limiting which devices lvm will see and use. Devices that are not listed will appear to be missing to the lvm command. Multiple devices files can be kept in /etc/lvm/devices, which allows lvm to be used with different sets of devices, e.g. system devices do not need to be exposed to a specific application, and the application can use lvm on its own set of devices that are not exposed to the system. The option --devicesfile <filename> is used to select the devices file to use with the command. Without the option set, the default system devices file is used. Setting --devicesfile "" causes lvm to not use a devices file. An existing, empty devices file means lvm will see no devices. The new command vgimportdevices adds PVs from a VG to the devices file and updates the VG metadata to include the device IDs. vgimportdevices -a will import all VGs into the system devices file. LVM commands run by dmeventd not use a devices file by default, and will look at all devices on the system. A devices file can be created for dmeventd (/etc/lvm/devices/dmeventd.devices) If this file exists, lvm commands run by dmeventd will use it. Internal implementaion: - device_ids_read - read the devices file . add struct dev_use (du) to cmd->use_devices for each devices file entry - dev_cache_scan - get /dev entries . add struct device (dev) to dev_cache for each device on the system - device_ids_match - match devices file entries to /dev entries . match each du on cmd->use_devices to a dev in dev_cache, using device ID . on match, set du->dev, dev->id, dev->flags MATCHED_USE_ID - label_scan - read lvm headers and metadata from devices . filters are applied, those that do not need data from the device . filter-deviceid skips devs without MATCHED_USE_ID, i.e. skips /dev entries that are not listed in the devices file . read lvm label from dev . filters are applied, those that use data from the device . read lvm metadata from dev . add info/vginfo structs for PVs/VGs (info is "lvmcache") - device_ids_find_renamed_devs - handle devices with unstable devname ID where devname changed . this step only needed when devs do not have proper device IDs, and their dev names change, e.g. after reboot sdb becomes sdc. . detect incorrect match because PVID in the devices file entry does not match the PVID found when the device was read above . undo incorrect match between du and dev above . search system devices for new location of PVID . update devices file with new devnames for PVIDs on renamed devices . label_scan the renamed devs - continue with command processing
2020-06-23 21:25:41 +03:00
filters/filter-deviceid.c \
o Rename many occurrences of 'backup' to 'archive' to reduce confusion. o Extract file creation/renaming code into a library and change backup code to use it too. o Support umask. o Bring lvm.conf man page up-to-date.
2002-01-09 22:16:48 +03:00
format_text/archive.c \
Move archiver code from tools into library.
2005-05-17 17:46:38 +04:00
format_text/archiver.c \
o sync backup changes
2001-12-20 14:52:54 +03:00
format_text/export.c \
format_text/flags.c \
o Get format-text.c compiling.
2002-01-07 12:16:20 +03:00
format_text/format-text.c \
o sync backup changes
2001-12-20 14:52:54 +03:00
format_text/import.c \
Some new features.
2002-11-18 17:04:08 +03:00
format_text/import_vsn1.c \
format_text/text_label.c \
Fix reporting of LV fields alongside unallocated PV segments.
2008-06-25 20:52:27 +04:00
freeseg/freeseg.c \
o label.c now compiles.
2002-01-11 13:43:32 +03:00
label/label.c \
add device hints to reduce scanning Save the list of PVs in /run/lvm/hints. These hints are used to reduce scanning in a number of commands to only the PVs on the system, or only the PVs in a requested VG (rather than all devices on the system.)
2018-12-07 23:35:22 +03:00
label/hints.c \
Implement a no_locking module that *does* attempt activation.
2002-04-11 18:10:32 +04:00
locking/file_locking.c \
o First changes to add snapshot support. I'm taking a different route from LVM1 here in that snapshots are a seperate entity from the logical volumes, I think of them as an application of an LV (or two lvs rather). As such there is a list of snapshots held against the vg, and there is *not* a SNAPSHOT, or SHAPSHOT_ORG flag in lv->status.
2002-02-12 19:31:31 +03:00
locking/locking.c \
Makefiles & autoconf.
2001-09-21 16:37:43 +04:00
log/log.c \
cache: Add functions that create/remove cache LVs A cache LV - from LVM's perpective - is a user accessible device that links the cachepool LV and the origin LV. The following functions were added to facilitate the creation and removal of this top-level LV: 1) 'lv_cache_create' - takes a cachepool and an origin device and links them into a new top-level LV of 'cache' segment type. No allocation is necessary in this function, as the sub-LVs contain all of the necessary allocated space. Only the top-level layer needs to be created. 2) 'lv_cache_remove' - this function removes the top-level LV of a cache LV - promoting the cachepool and origin sub-LVs to top-level devices and leaving them exposed to the user. That is, the cachepool is unlinked and free to be used with another origin to form a new cache LV; and the origin is no longer cached. (Currently, if the cache needs to be flushed, it is done in this function and the function waits for it to complete before proceeding. This will be taken out in a future patch in favor of polling.)
2014-02-04 17:59:58 +04:00
metadata/cache_manip.c \
writecache: move code into new file put writecache specific code in writecache_manip.c should be no functional change
2019-09-24 23:28:02 +03:00
metadata/writecache_manip.c \
Allow dm-integrity to be used for raid images dm-integrity stores checksums of the data written to an LV, and returns an error if data read from the LV does not match the previously saved checksum. When used on raid images, dm-raid will correct the error by reading the block from another image, and the device user sees no error. The integrity metadata (checksums) are stored on an internal LV allocated by lvm for each linear image. The internal LV is allocated on the same PV as the image. Create a raid LV with an integrity layer over each raid image (for raid levels 1,4,5,6,10): lvcreate --type raidN --raidintegrity y [options] Add an integrity layer to images of an existing raid LV: lvconvert --raidintegrity y LV Remove the integrity layer from images of a raid LV: lvconvert --raidintegrity n LV Settings Use --raidintegritymode journal|bitmap (journal is default) to configure the method used by dm-integrity to ensure crash consistency. Initialization When integrity is added to an LV, the kernel needs to initialize the integrity metadata/checksums for all blocks in the LV. The data corruption checking performed by dm-integrity will only operate on areas of the LV that are already initialized. The progress of integrity initialization is reported by the "syncpercent" LV reporting field (and under the Cpy%Sync lvs column.) Example: create a raid1 LV with integrity: $ lvcreate --type raid1 -m1 --raidintegrity y -n rr -L1G foo Creating integrity metadata LV rr_rimage_0_imeta with size 12.00 MiB. Logical volume "rr_rimage_0_imeta" created. Creating integrity metadata LV rr_rimage_1_imeta with size 12.00 MiB. Logical volume "rr_rimage_1_imeta" created. Logical volume "rr" created. $ lvs -a foo LV VG Attr LSize Origin Cpy%Sync rr foo rwi-a-r--- 1.00g 4.93 [rr_rimage_0] foo gwi-aor--- 1.00g [rr_rimage_0_iorig] 41.02 [rr_rimage_0_imeta] foo ewi-ao---- 12.00m [rr_rimage_0_iorig] foo -wi-ao---- 1.00g [rr_rimage_1] foo gwi-aor--- 1.00g [rr_rimage_1_iorig] 39.45 [rr_rimage_1_imeta] foo ewi-ao---- 12.00m [rr_rimage_1_iorig] foo -wi-ao---- 1.00g [rr_rmeta_0] foo ewi-aor--- 4.00m [rr_rmeta_1] foo ewi-aor--- 4.00m
2019-11-21 01:07:27 +03:00
metadata/integrity_manip.c \
Refactor metadata.[ch] into lv.[ch] for lv functions. This patch is similar to the other patches for pv and vg functionality, and separates lv functionality into separate files, concentrating on reporting fields and simple functions.
2010-09-30 17:05:45 +04:00
metadata/lv.c \
o lv_manip.c will contain the code for lv_create, lv_extend and lv_reduce.
2001-11-06 13:29:56 +03:00
metadata/lv_manip.c \
o New function 'merge_segments' o Call said function at end of lv_extend
2002-01-07 18:08:28 +03:00
metadata/merge.c \
o pvcreate o added uuid unit o stubbed partition stuff
2001-10-12 14:32:06 +04:00
metadata/metadata.c \
Add mirror.c
2003-04-30 19:24:49 +04:00
metadata/mirror.c \
Misc: Move some thin pool functions to a new file Functions that handle set-up, tear-down and creation of thin pool volumes will be more generally applicable when more targets exist that make use of device-mapper's persistent data format. One of these targets is the dm-cache target. I've selected some functions that will be useful for the cache segment type to be moved, since they will no longer be thin pool specific but are more broadly useful to any segment type that makes use of a 'pool' LV.
2014-01-22 20:11:29 +04:00
metadata/pool_manip.c \
Refactor metadata.[ch] into pv.[ch] for pv functions. The metadata.[ch] files are very large. This patch makes a first attempt at separating out pv functions and data, particularly related to the reporting fields calculations. More code could be moved here but for now I'm stopping at reporting functions 'get' / 'set' functions.
2010-09-30 17:05:20 +04:00
metadata/pv.c \
move pv_list code into lib
2020-01-14 23:12:20 +03:00
metadata/pv_list.c \
Initial pv_segment code.
2005-04-20 00:58:25 +04:00
metadata/pv_manip.c \
o code for building free area lists on a pv. Compiles but not run.
2001-11-05 19:41:38 +03:00
metadata/pv_map.c \
Add ability to down-convert RAID1 arrays. Also, add some simple RAID tests to testsuite.
2011-08-11 22:24:40 +04:00
metadata/raid_manip.c \
Rename old segtypes files to segtype.
2004-09-16 22:40:56 +04:00
metadata/segtype.c \
o First changes to add snapshot support. I'm taking a different route from LVM1 here in that snapshots are a seperate entity from the logical volumes, I think of them as an application of an LV (or two lvs rather). As such there is a list of snapshots held against the vg, and there is *not* a SNAPSHOT, or SHAPSHOT_ORG flag in lv->status.
2002-02-12 19:31:31 +03:00
metadata/snapshot_manip.c \
add thin_manip.c like the other manip files move basic lv_is_* to macros data_lv -> pool_lv - we decided to call it 'pool' everywhere now
2011-09-06 23:25:42 +04:00
metadata/thin_manip.c \
vdo: introduce segment types and manip functions Core functionality introducing lvm VDO support.
2018-06-29 12:11:14 +03:00
metadata/vdo_manip.c \
Refactor metadata.[ch] into vg.[ch] for vg functions. The metadata.[ch] files are very large. This patch makes a first attempt at separating out vg functions and data, particularly related to the reporting fields calculations.
2010-09-30 17:04:55 +04:00
metadata/vg.c \
build: remove --with-{snapshots,mirrors,raid,thin,cache} options from ./configure It now behaves as if the were all set as 'internal'
2018-04-30 12:11:23 +03:00
mirror/mirrored.c \
Some new features.
2002-11-18 17:04:08 +03:00
misc/crc.c \
Attempt to load missing targets using modprobe. Simplify dev_manager_info().
2005-10-17 22:00:02 +04:00
misc/lvm-exec.c \
o Rename many occurrences of 'backup' to 'archive' to reduce confusion. o Extract file creation/renaming code into a library and change backup code to use it too. o Support umask. o Bring lvm.conf man page up-to-date.
2002-01-09 22:16:48 +03:00
misc/lvm-file.c \
locking: Separate out flock and signal code.
2014-05-01 20:37:14 +04:00
misc/lvm-flock.c \
Split out lvm-logging.h from log.h.
2008-10-30 20:27:28 +03:00
misc/lvm-globals.c \
lib: Move lcm and gcd to lib/misc for wider use.
2016-08-18 16:06:13 +03:00
misc/lvm-maths.c \
locking: Separate out flock and signal code.
2014-05-01 20:37:14 +04:00
misc/lvm-signal.c \
Default stripesize 64k & config file setting for it; Clear many compiler warnings (i386) & associated bugs - hopefully without introducing too many new bugs:-) (Same exercise required for other archs.) Default compilation has optimisation - or else use ./configure --enable-debug
2002-12-20 02:25:55 +03:00
misc/lvm-string.c \
Add lvm_getpagesize wrapper.
2006-08-17 22:23:44 +04:00
misc/lvm-wrappers.c \
Refactor the percent (mirror sync, snapshot usage) handling code to use fixed-point values instead of a combination of a float value and an enum.
2010-11-30 14:53:31 +03:00
misc/lvm-percent.c \
lvm: drop usage of dl library Since lvm no longer supports any dlopen-able plugins (which in practice was never really usable) drop linking with -ldl.
2018-12-14 23:51:11 +03:00
misc/sharedlib.c \
Another sync point - numerous fixes & clean ups.
2003-07-05 02:34:56 +04:00
mm/memlock.c \
dbus: add notification from commands When a command modifies a PV or VG, or changes the activation state of an LV, it will send a dbus notification when the command is finished. This can be enabled/disabled with a config setting.
2016-02-22 18:42:03 +03:00
notify/lvmnotify.c \
lib/properties: Common code for handling properties. The common bits from lib/report/properties.[c|h] have been moved to lib/properties/prop_common.[c|h] to allow re-use of property handling functionality without polluting the report handling functionality. Signed-off-by: Tony Asleson <tasleson@redhat.com>
2013-07-12 21:09:44 +04:00
properties/prop_common.c \
build: remove --with-{snapshots,mirrors,raid,thin,cache} options from ./configure It now behaves as if the were all set as 'internal'
2018-04-30 12:11:23 +03:00
raid/raid.c \
Add properties.[ch] to lib/report, defined based on columns.h. Extend the existing reporting infrastructure definitions and structures to include a 'get' and 'set' function for each field. We will provide a 'get' and 'set' function for each of these fields, which will be utilized by exported lvm2app functions. Define a default _not_implemented 'get' and 'set' function that just sets an errno and returns 0. Future patches will actually implement the specific 'get' and 'set' functions for each property. For read-only properties, only the 'get' function will be implemented. Define vg_get_property() function to query a property. We will call this from a lvm2app function.
2010-08-20 16:44:47 +04:00
report/properties.c \
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
report/report.c \
build: remove --with-{snapshots,mirrors,raid,thin,cache} options from ./configure It now behaves as if the were all set as 'internal'
2018-04-30 12:11:23 +03:00
snapshot/snapshot.c \
Begin to separate out segment types.
2004-05-05 01:25:57 +04:00
striped/striped.c \
build: remove --with-{snapshots,mirrors,raid,thin,cache} options from ./configure It now behaves as if the were all set as 'internal'
2018-04-30 12:11:23 +03:00
thin/thin.c \
Add --type to lvcreate/resize. Add virtual segment types, zero and error. A large sparse device can be constructed as a writeable snapshot of a large zero device.
2004-05-11 20:01:58 +04:00
uuid/uuid.c \
Add new liblvm build directory and move lvm_base.c. The original liblvm.a has been moved to liblvm-internal.a. We now use liblvm.a for the new application library and build it inside liblvm directory. Change dependencies so tools depend on liblvm application library, and application library depends on liblvm internal.
2009-03-06 19:19:52 +03:00
zero/zero.c
Some new features.
2002-11-18 17:04:08 +03:00
configure --disable-devmapper if you don't have libdevmapper
2003-01-09 01:44:07 +03:00
ifeq ("@DEVMAPPER@", "yes")
Update makefiles (incl. cmdlib).
2004-03-26 16:21:12 +03:00
SOURCES +=\
configure --disable-devmapper if you don't have libdevmapper
2003-01-09 01:44:07 +03:00
activate/dev_manager.c \
activate/fs.c
endif
lvmpolld: Add standalone polldaemon. See doc/lvmpolld_overview.txt
2015-05-09 02:59:18 +03:00
ifeq ("@BUILD_LVMPOLLD@", "yes")
SOURCES +=\
lvmpolld/lvmpolld-client.c
endif
Add lvmlockd
2015-03-05 23:00:44 +03:00
ifeq ("@BUILD_LVMLOCKD@", "yes")
SOURCES +=\
locking/lvmlockd.c
endif
vdo: introduce segment types and manip functions Core functionality introducing lvm VDO support.
2018-06-29 12:11:14 +03:00
ifeq ("@VDO@", "internal")
SOURCES += vdo/vdo.c
endif
Rename liblvm to liblvm-internal. Make preparation for using liblvm for new application library.
2009-03-06 19:17:28 +03:00
LIB_NAME = liblvm-internal
LIB_STATIC = $(LIB_NAME).a
Makefiles & autoconf.
2001-09-21 16:37:43 +04:00
Update cflow file generation - support build dir and use $(top_srcdir) to obtain sources. Create make.tmpl target for simplier generation of cflow files with the help of CFLOW_LIST, CFLOW_LIST_TARGET, CFLOW_TARGET. Still cflow usage is not perfect.
2010-03-29 18:11:17 +04:00
CFLOW_LIST = $(SOURCES)
CFLOW_LIST_TARGET = $(LIB_NAME).cflow
makefiles: fixing linking Avoid adding -g more then once for debug builds. Avoid enabling DEBUG_MEM when we build multithreaded tools. Link executables with -fPIE -pie and --export-dynamic LDFLAGS Introduce PROGS_FLAGS to add option to pass flags for external libs. Link lvm2 internally library only when really used. Link DAEMON_LIBS with daemons. Pass VALGRIND_CFLAGS internally Set shell failure mode on couple places.
2017-08-01 01:01:07 +03:00
PROGS_CFLAGS = $(BLKID_CFLAGS) $(UDEV_CFLAGS)
Makefiles & autoconf.
2001-09-21 16:37:43 +04:00
makefiles: fixing linking Avoid adding -g more then once for debug builds. Avoid enabling DEBUG_MEM when we build multithreaded tools. Link executables with -fPIE -pie and --export-dynamic LDFLAGS Introduce PROGS_FLAGS to add option to pass flags for external libs. Link lvm2 internally library only when really used. Link DAEMON_LIBS with daemons. Pass VALGRIND_CFLAGS internally Set shell failure mode on couple places.
2017-08-01 01:01:07 +03:00
include $(top_builddir)/make.tmpl
makefiles: use BLKID/UDEV_CFLAGS properly blkid.h needs BLKID_CFLAGS Do not add UDEV_CFLAGS everywhere and use it only when needed.
2014-03-06 19:03:08 +04:00
Build shared parts with 'make' command (mpatocka) When some parts of lvm are built as shared libraries (for example with --with-snapshots=shared), the 'make' command does not build these parts. The shared parts are built with 'make install' command. This bug can be seen if you go to 'lib' subdirectory and type 'make'. If you type 'make', the shared libraries are not built, if you type 'make all', the shared libraries are built. The reason for the bug is the line $(SUBDIRS): $(LIB_STATIC) If make is executed without any arguments, it makes the first target in the Makefile. If the first target is '$(SUBDIRS): $(LIB_STATIC)', it only builds static libraries. This patch moves '$(SUBDIRS): $(LIB_STATIC)' after include $(top_srcdir)/make.tmpl. make.tmpl contains the 'all' target as its first target, so 'make' will be equivalent to 'make all' and shared libraries will be build with 'make' command. Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
2009-06-03 15:31:06 +04:00
$(SUBDIRS): $(LIB_STATIC)
makefiles: ensure no old .h are left Ensure make clean cleans any left-over file from their previous location so they are not in conflict with new ones. Also hide error message when .commands file is not present.
2015-09-08 15:33:29 +03:00
CLEAN_TARGETS += misc/configure.h misc/lvm-version.h
Copy Permalink