summaryrefslogtreecommitdiff
path: root/scripts/Makefile.in
Commit message (Collapse)AuthorAgeFilesLines
* make: Fix build in chrootdev-mcsontos-lib-tools-dependencyMarian Csontos2022-09-201-0/+1
| | | | When building in a buildroot, must create libexec directory explicitly.
* lvresize: add new options and defaults for fs handlingDavid Teigland2022-09-131-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new option "--fs String" for lvresize/lvreduce/lvextend controls the handling of file systems before/after resizing the LV. --resizefs is the same as --fs resize. The new option "--fsmode String" can be used to control mounting and unmounting of the fs during resizing. Possible --fs values: checksize Only applies to reducing size; does nothing for extend. Check the fs size and reduce the LV if the fs is not using the affected space, i.e. the fs does not need to be shrunk. Fail the command without reducing the fs or LV if the fs is using the affected space. resize Resize the fs using the fs-specific resize command. This may include mounting, unmounting, or running fsck. See --fsmode to control mounting behavior, and --nofsck to disable fsck. resize_fsadm Use the old method of calling fsadm to handle the fs (deprecated.) Warning: this option does not prevent lvreduce from destroying file systems that are unmounted (or mounted if prompts are skipped.) ignore Resize the LV without checking for or handling a file system. Warning: using ignore when reducing the LV size may destroy the file system. Possible --fsmode values: manage Mount or unmount the fs as needed to resize the fs, and attempt to restore the original mount state at the end. nochange Do not mount or unmount the fs. If mounting or unmounting is required to resize the fs, then do not resize the fs or the LV and fail the command. offline Unmount the fs if it is mounted, and resize the fs while it is unmounted. If mounting is required to resize the fs, then do not resize the fs or the LV and fail the command. Notes on lvreduce: When no --fs or --resizefs option is specified: . lvextend default behavior is fs ignore. . lvreduce default behavior is fs checksize (includes activating the LV.) With the exception of --fs resize_fsadm|ignore, lvreduce requires the recent libblkid fields FSLASTBLOCK and FSBLOCKSIZE. FSLASTBLOCK*FSBLOCKSIZE is the last byte used by the fs on the LV, which determines if reducing the fs is necessary.
* remove static autoactivationDavid Teigland2022-01-271-14/+0
| | | | | | | | | event based autoactivation is now the only method that lvm provides for autoactivation. Setting lvm.conf event_activation=0 can still be used to disable event based autoactivation commands, but doing so will no longer enable static autoactivation.
* new udev autoactivationDavid Teigland2021-10-071-1/+0
| | | | | | | | | | | | | | new udev rule 69-dm-lvm.rules replaces 69-dm-lvm-meta.rules and lvm2-pvscan.service udev rule calls pvscan directly on the added device pvscan output indicates if a complete VG can be activated udev env var LVM_VG_NAME_COMPLETE is used to pass complete VG name from pvscan to the udev rule udev rule uses systemd-run to run vgchange -aay <vgname>
* vdo: rename vdoimport to lvm_import_vdoZdenek Kabelac2021-08-261-2/+2
| | | | Missed bits in previous rename commits.
* vdo: Rename vdoimport to lvm_import_vdo.Marian Csontos2021-08-261-1/+1
|
* vdo: add vdoimport supportZdenek Kabelac2021-07-091-0/+4
| | | | | | | | | | | | | Add tool 'vdoimport' to support easy conversion of an existing VDO manager managed VDO volumes into lvm2 managed VDO LV. When physical converted volume is already a logical volume, conversion happens with the VG itself, just with validation for extent_size, so the virtually sized logical VDO volume size can be expressed in extents. Example of basic simple usage: vdoimport --name vg/vdolv /dev/mapper/vdophysicalvolume
* makefiles: better loggingZdenek Kabelac2021-03-021-5/+5
| | | | | Show only filename instead of full path name when building in builddir != srcdir
* makefiles: correcting login of makefileZdenek Kabelac2018-12-171-2/+2
| | | | | | Fixing some ordering issue with inclusion of common make.tmpl. Correcting dependency calculation Simplifying inclusive makefile
* makefiles: missing cleaningZdenek Kabelac2018-12-171-0/+1
|
* makefiles: quite installZdenek Kabelac2018-12-171-2/+3
|
* makefiles: updates for less verbosityZdenek Kabelac2018-11-291-27/+32
|
* 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.
* scripts: remove lvmetad from makefileDavid Teigland2018-11-151-11/+0
|
* More cleanup needed for dropped scriptsDavid Teigland2018-09-131-3/+5
| | | | and drop the lvm2 prefix from lvmlockd service
* build: drop some more old filesZdenek Kabelac2018-07-021-0/+4
|
* scripts: clvmd goneZdenek Kabelac2018-06-151-8/+0
|
* Remove makefile entries for removed scriptDavid Teigland2018-06-131-2/+0
|
* scripts/lvm2_activation_generator_systemd_red_hat: rewrite to use lvmconfigJoe Thornber2018-06-071-14/+2
| | | | Unit tested the new code, but not run functional tests (assuming they exist).
* build: libbase.aJoe Thornber2018-06-041-2/+2
|
* build: link lvm2_activation_generator_systemd_red_hat with libdevice-mapper.aJoe Thornber2018-06-041-2/+2
|
* device-mapper: Fork libdm internally.Joe Thornber2018-05-161-2/+2
| | | | | | | | | | | | 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.
* [makefile] add -laio to makefilesDavid Teigland2018-04-201-1/+1
|
* makefiles: script executable missed dynamicZdenek Kabelac2017-08-011-1/+1
| | | | | Add missing ELDFLAGS when linking binary. Also pass CFLAGS for cases where we build code coverage compilation.
* configure: tune BUILD_DMEVENTDZdenek Kabelac2017-08-011-1/+1
| | | | | | | | | | Drop 'DMEVENT' make variable and use BUILD_DMEVENTD like with other daemons. NOTE: by default we do not build dmeventd - maybe time to change as lot of build targets basically do need dmeventd... Switch to use SYSTEMD_LIBS and avoid linking systemd library with every linked tool when dbus notification are enabled. (TODO add missing testing for lib presence)
* make: also clean up lvmdump.sh with substitutions - there's original ↵Peter Rajnoha2016-09-231-0/+1
| | | | lvmdump.sh.in
* vgimportclone: add native commandDavid Teigland2016-06-221-1/+1
| | | | | This is cleaner and more efficient than the script. The args and usage are unchanged.
* make: add generated parts of lvmdbusd to DISTCLEAN_TARGETS for make distcleanPeter Rajnoha2016-06-021-0/+2
|
* lvmdbus: Add new daemon.Alasdair G Kergon2016-02-171-1/+14
|
* doc: change fsf addressZdenek Kabelac2016-01-211-1/+1
| | | | | Hmm rpmlint suggest fsf is using a different address these days, so lets keep it up-to-date
* makefiles: switch to rpath-linkZdenek Kabelac2015-10-141-2/+2
| | | | | Plain rpath is to invasive and gets into binary. We only want to provide hint for linker.
* makefiles: older gcc needs hint with rpathZdenek Kabelac2015-10-131-0/+3
| | | | | gcc 4.3 seems not to be able to find linked library without specifying -rpath to linker (plain -L) is not enough.
* makefiles: drop explicit linkingZdenek Kabelac2015-10-131-5/+0
| | | | Nothing in /sscripts needs devmapper-event library so drop its linking.
* makefiles: distclean missing filesZdenek Kabelac2015-09-111-0/+1
|
* Add lvmlockddev-dct-lvmlockd-AZDavid Teigland2015-07-021-0/+6
|
* lvmpolld: Add standalone polldaemon.Ondrej Kozina2015-05-091-0/+9
| | | | See doc/lvmpolld_overview.txt
* make: move blkdeactivate script and blkdeactivate.8 man page installation ↵Peter Rajnoha2015-04-141-5/+7
| | | | | | from install_lvm2 to install_device-mapper target This completes commit 7a4e27eee51e89a550bc55f78daea6d943293202.
* systemd: install lvm2-cluster-activation script as executablePeter Rajnoha2014-05-211-1/+1
|
* make: fix commit 1756bf6Peter Rajnoha2014-05-071-1/+1
| | | | "DIST_TARGET" should be "DISTCLEAN_TARGET"
* makefile: fix regressionZdenek Kabelac2014-04-301-1/+1
| | | | | | Commit 1af05a7a166a470d1b9d86f88fdc64c2d984124b was incorrect. Generated files from configure could be only distclean-ed. (in-release fix)
* makefiles: clear targets in with make cleanZdenek Kabelac2014-04-181-12/+20
| | | | | Make clean usually cleans all compiled files. Make distclean cleans configure generated files
* systemd: rename lvm2-cluster-activation and lvm2-clvmd services to follow ↵Peter Rajnoha2014-02-111-4/+5
| | | | | | | | | | | | | | existing naming lvm2_cluster_activation_red_hat.service.in -> lvm2_cluster_activation_systemd_red_hat.service.in lvm2_clvmd_red_hat.service.in -> lvm2_clvmd_red_hat.service.in Edit lvm2-cluster-activation reference on cmirror - take new lvm2-cmirrord.service, it was just cmirrord(.service) before as the old initscript was used in compatibility mode. Also, use WantedBy=multi-user.target instead of sysinit.target in lvm2-cluster-activation.service.
* systemd: add systemd unit for cmirrordPeter Rajnoha2014-02-111-0/+4
|
* Add systemd native service for clvmd and cluster activationOndrej Kozina2014-02-101-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | The commit splits original clvmd service in two new native services for systemd enabled systems while original init scripts remain unaltered. New systemd native services: 1) clvmd daemon itself (lvm2_clvmd_red_hat.service.in) 2) (de)activation of clustered VGs (lvm2_cluster_activation_red_hat.service.in) There're several reasons to split it. First, there's no support for conditional stop in systemd and AFAIK they don't plan to support it. In other words: if the deactivation fails for some reason, systemd doesn't care and will simply kill all remaining processes in original cgroup (by default). Killing the remaining procs can be suppressed however it doesn't solve the following problem: You can't repeat the stop command of a failed service. The repeated stop command is simply not propagated to the service in a failed state. You would have to start and then try to stop the service again. Unfortunately, this can't be done while the daemon is still running (and we need the daemon to stay active until all clustered VGs are deactivated properly). In a separated setup we need only to restart the failed activation service and that's fine.
* compile/link: use RELRO/PIE compiler/linker options for executablesPeter Rajnoha2013-12-051-1/+3
|
* cleanup: for commit 546db1cPeter Rajnoha2013-10-231-1/+1
| | | | | - properly clean lvm2-pvscan@.service on distclean - use @sbindir@ for sbin path in ExecStop
* udev+systemd: make pvscan --cache -aay run as systemd background job from udevPeter Rajnoha2013-10-181-0/+2
| | | | | | | | | | | | | | | | | | | The new lvm2-pvscan@.service is responsible for on-demand execution of "pvscan --cache --activate ay" which causes lvmetad to be updated and LVM activation done if the VG is complete. Also, use udev-systemd mechanism to instantiate the job as the lvm2-pvscan@$devnode.service on each newly appeared PV in the system. This prevents the background job to be killed (that would happen if it was directly forked from udev rule - this behaviour is seen in recent versions of udev with the help of systemd that can track detached processes - the detached process would still be in the same cgroup). To enable this official udev-systemd protocol for instantiating background jobs, use new --enable-udev-systemd-background-jobs configure switch (it's disabled by default). This option is highly recommended wherever systemd is used!
* distclean: add missing itemsPeter Rajnoha2013-06-121-1/+3
| | | | | | | These were missing in distclean target under scripts dir: blk_availability_init_red_hat blk_availability_systemd_red_hat.service blkdeactivate.sh
* scripts: introduce blkdeactivatePeter Rajnoha2012-10-121-0/+10
| | | | | | | | | | | | | | | blkdeactivate - utility to deactivate block devices Traverses the tree of block devices and tries to deactivate them. Currently, it supports device-mapper-based devices together with LVM. See man/blkdeactivate.8 for more info. It is targeted for use during shutdown to properly deactivate the whole block device stack - systemd and init scripts are provided as well. However, it might be used directly on command line too. Please, see the commentary at the top of the blkdeactivate script for dependencies and versions of other utilities required.
* make: fix make in scripts dir for --disable-applibPeter Rajnoha2012-08-011-5/+14
|