summaryrefslogtreecommitdiff
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
...
* configure: check for BLKZEROOUT supportZdenek Kabelac2020-10-021-0/+27
|
* configure: update helpZdenek Kabelac2020-09-291-5/+5
| | | | Help shows new defaults.
* lvm: add readline alternative editlineBastian Germann2020-09-291-0/+23
| | | | | | | | | | | | | LVM2 is distributed under GPLv2 only. The readline library changed its license long ago to GPLv3. Given that those licenses are incompatible and you follow the FSF in their interpretation that dynamically linking creates a derivative work, distributing LVM2 linked against a current readline version might be legally problematic. Add support for the BSD licensed editline library as an alternative for readline. Link: https://thrysoee.dk/editline
* configure: enable integrity by defaultDavid Teigland2020-09-161-1/+1
|
* configure: just upper case start of sentenceZdenek Kabelac2020-09-141-1/+1
|
* configure: compile with vdo and writecache by defaultZdenek Kabelac2020-09-101-2/+2
| | | | | | | | | | Enable compilation of vdo and writecache support as internaly supported segment types by default. For disabling use: --with-vdo=none --with-writcache=none
* Allow dm-integrity to be used for raid imagesDavid Teigland2020-04-151-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* configure: continue build if prlimit is missingZdenek Kabelac2019-08-261-1/+2
|
* configure: check for prlimitZdenek Kabelac2019-08-261-1/+1
| | | | | | Update configure and make code compilable if prlimit() is not present. Since the code is suspicious do not cope yet with it's replacement with set/getrlimit().
* configure: Fix setting of CLDFLAGS defaultMarian Csontos2019-08-191-3/+3
|
* configure: Fix the default in help stringMarian Csontos2019-08-191-1/+1
|
* configure: check for pselectZdenek Kabelac2019-04-161-1/+1
|
* lvextend: refresh shared LV remotely using dlm/corosyncDavid Teigland2019-03-211-0/+20
| | | | | | | | | When lvextend extends an LV that is active with a shared lock, use this as a signal that other hosts may also have the LV active, with gfs2 mounted, and should have the LV refreshed to reflect the new size. Use the libdlmcontrol run api, which uses dlm_controld/corosync to run an lvchange --refresh command on other cluster nodes.
* headers: use configure.h as 1st. headerZdenek Kabelac2018-12-141-0/+5
| | | | | | | | | | | Ensure configure.h is always 1st. included header. Maybe we could eventually introduce gcc -include option, but for now this better uses dependency tracking. Also move _REENTRANT and _GNU_SOURCE into configure.h so it doesn't need to be present in various source files. This ensures consistent compilation of headers like stdio.h since it may produce different declaration.
* build: Upse PYTHON_CONFIG env.variable when setMarian Csontos2018-12-061-1/+0
| | | | This adds up to Commit 6462e8dffc7ed53973ce796cec18fecc0fb89d77.
* Place the first PE at 1 MiB for all defaultsDavid Teigland2018-11-261-10/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | . When using default settings, this commit should change nothing. The first PE continues to be placed at 1 MiB resulting in a metadata area size of 1020 KiB (for 4K page sizes; slightly smaller for larger page sizes.) . When default_data_alignment is disabled in lvm.conf, align pe_start at 1 MiB, based on a default metadata area size that adapts to the page size. Previously, disabling this option would result in mda_size that was too small for common use, and produced a 64 KiB aligned pe_start. . Customized pe_start and mda_size values continue to be set as before in lvm.conf and command line. . Remove the configure option for setting default_data_alignment at build time. . Improve alignment related option descriptions. . Add section about alignment to pvcreate man page. Previously, DEFAULT_PVMETADATASIZE was 255 sectors. However, the fact that the config setting named "default_data_alignment" has a default value of 1 (MiB) meant that DEFAULT_PVMETADATASIZE was having no effect. The metadata area size is the space between the start of the metadata area (page size offset from the start of the device) and the first PE (1 MiB by default due to default_data_alignment 1.) The result is a 1020 KiB metadata area on machines with 4KiB page size (1024 KiB - 4 KiB), and smaller on machines with larger page size. If default_data_alignment was set to 0 (disabled), then DEFAULT_PVMETADATASIZE 255 would take effect, and produce a metadata area that was 188 KiB and pe_start of 192 KiB. This was too small for common use. This is fixed by making the default metadata area size a computed value that matches the value produced by default_data_alignment.
* pvscan systemd service for event based activationDavid Teigland2018-11-261-0/+1
| | | | | | | | | | | | | The pvscan systemd service for autoactivation was mistakenly dropped along with the lvmetad related services. The activation generator program now looks at the new lvm.conf setting "event_activation" (default 1) to switch between event activation and direct activation. Previously, the old use_lvmetad setting was used to switch between event and direct activation.
* Add dm-writecache supportDavid Teigland2018-11-061-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* build: Fix CLDFLAGS defaultMarian Csontos2018-10-301-2/+5
|
* build: Use PYTHON env. variable when providedMarian Csontos2018-10-101-1/+1
|
* More cleanup needed for dropped scriptsDavid Teigland2018-09-131-2/+2
| | | | and drop the lvm2 prefix from lvmlockd service
* configure: fix LVMCONFIG_PATH assignmentPeter Rajnoha2018-08-301-1/+1
|
* Remove lvmetadDavid Teigland2018-07-111-47/+0
| | | | | | | | | | | | | Native disk scanning is now both reduced and async/parallel, which makes it comparable in performance (and often faster) when compared to lvm using lvmetad. Autoactivation now uses local temp files to record online PVs, and no longer requires lvmetad. There should be no apparent command-level change in behavior.
* build: add vdo configuration option --with-vdo=Zdenek Kabelac2018-07-091-0/+54
| | | | | | | | | | | | | Checks whether VDO support is enabled. Detects presence of 'vdoformat' tool which is required for to format VDO pool. ATM build of VDO is NOT automatically enabled (None is default). To enable build of LVM with VDO support use: configure --with-vdo=internal TODO: Maybe future version may switch to link some small VDO library for formating (would require linking and package dependency).
* dmeventd: base vdo pluginZdenek Kabelac2018-07-091-0/+1
| | | | | | | | | | | Introduce VDO plugin for monitoring VDO devices. This plugin can be used also by other users, as plugin checks for UUID prefix 'LVM-' and run lvm actions only on those devices. Non LVM- device are only monitored and log warnings when usage threshold reaches 80%.
* utils: add clzllZdenek Kabelac2018-06-221-0/+1
| | | | Check for __builtin_clzll and add wrapper when missing.
* build: support --disable-silent-rulesZdenek Kabelac2018-06-221-0/+10
| | | | | Add support for standardized option for have verbose builds. Useful for distro builds where more details can be useful.
* dmfilemapd: Move to libdm/dm-toolsJoe Thornber2018-06-141-1/+0
| | | | No longer uses any lvm code.
* dmsetup: move to libdm/dm-tools/dmsetupJoe Thornber2018-06-141-0/+1
| | | | | links against libdevmapper again. no longer includes code from lvm.
* Remove makefile entries for removed scriptDavid Teigland2018-06-131-1/+0
|
* Remove python bindings for liblvm2appDavid Teigland2018-06-081-4/+0
|
* test/unit: Rename Makefile.in -> MakefileJoe Thornber2018-06-081-1/+0
| | | | There's nothing being expanded.
* liblvm: remove lvmapiJoe Thornber2018-06-081-61/+2
| | | | This has been deprecated for a while.
* scripts/lvm2_activation_generator_systemd_red_hat: rewrite to use lvmconfigJoe Thornber2018-06-071-0/+3
| | | | Unit tested the new code, but not run functional tests (assuming they exist).
* Remove clvmd and associated codeDavid Teigland2018-06-051-288/+1
| | | | More code reduction and simplification can follow.
* Merge branch 'master' into 2018-05-11-fork-libdmJoe Thornber2018-05-161-1/+2
|\
| * tests: move into generated fileZdenek Kabelac2018-05-151-0/+1
| | | | | | | | | | Since python path is evaluated and we cannot use anymore /usr/bin/env switch to generated file.
| * build: configure detect libaioZdenek Kabelac2018-05-151-1/+1
| | | | | | | | | | | | | | | | | | No point to start building lvm without this header file. Although there could be 'some point' in supporting standalone build of 'just' libdm where the libaio might be avoided. TODO: think about configure option for building libdm only.
| * build: rename device-mapper to device_mapperZdenek Kabelac2018-05-121-0/+1
| | | | | | | | | | | | | | | | | | As Makefiles already do use target with name 'device-mapper' rename this new device-mapper dir to non-conflicting name. We also seem to already use '_' in other dir names. Also rename device_mapper/Makefile to source for generating Makefile.in so we can use it for build in other source dirs properly.
* | device-mapper: Fork libdm internally.Joe Thornber2018-05-161-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | The device-mapper directory now holds a copy of libdm source. At the moment this code is identical to libdm. Over time code will migrate out to appropriate places (see doc/refactoring.txt). The libdm directory still exists, and contains the source for the libdevmapper shared library, which we will continue to ship (though not neccessarily update). All code using libdm should now use the version in device-mapper.
* | build: Don't generate symlinks in include/ dirJoe Thornber2018-05-141-1/+0
|/ | | | | | | As we start refactoring the code to break dependencies (see doc/refactoring.txt), I want us to use full paths in the includes (eg, #include "base/data-struct/list.h"). This makes it more obvious when we're breaking abstraction boundaries, eg, including a file in metadata/ from base/
* configure.ac: bad configure generated due to stray ;;Joe Thornber2018-05-031-1/+1
|
* configure.ac: Remove some more remnants of optional RAIDJoe Thornber2018-05-031-18/+3
| | | | (It's now always 'internal')
* Revert "build: Stop creating the symlinks in include/ on the fly."Joe Thornber2018-05-011-0/+1
| | | | This reverts commit cdcea0bf55c170f538c3ffc114792eb3c993f4ac.
* Remove lvm1 and pool disk formatsDavid Teigland2018-04-301-58/+0
| | | | | | | | | | | There are likely more bits of code that can be removed, e.g. lvm1/pool-specific bits of code that were identified using FMT flags. The vgconvert command can likely be reduced further. The lvm1-specific config settings should probably have some other fields set for proper deprecation.
* configure: Remove --enable-testingJoe Thornber2018-04-301-10/+0
|
* build: Remove unused Makefiles from configure.acJoe Thornber2018-04-301-5/+0
| | | | Should have been in earlier patch.
* build: rename configure.in -> configure.acJoe Thornber2018-04-301-0/+2268
Squashes a warning from autotools
View Lorry Controller Status