summaryrefslogtreecommitdiffstats
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
...
* Implement automatic snapshot extension with dmeventd, and add two new optionsPetr Rockai2010-10-151-0/+19
| | | | | | | | to lvm.conf in the activation section: 'snapshot_autoextend_threshold' and 'snapshot_autoextend_percent', that define how to handle automatic snapshot extension. The former defines when the snapshot should be extended: when its space usage exceeds this many percent. The latter defines how much extra space should be allocated for the snapshot, in percent of its current size.
* Fixes for the devices/disable_after_error_count documentation.Petr Rockai2010-10-151-1/+1
|
* Tweak the lvm.conf comment about devices/disable_after_error_count.Petr Rockai2010-10-131-3/+4
|
* Limit repeated accesses to broken devices.Petr Rockai2010-10-131-0/+5
| | | | | Signed-off-by: Takahiro Yasui <takahiro.yasui@hds.com> Reviewed-by: Petr Rockai <prockai@redhat.com>
* Make example.conf description for 'default_data_alignment' more generic.Mike Snitzer2010-08-251-2/+1
|
* Switch to using configure --with-default-data-alignment=<NUM> toMike Snitzer2010-08-201-1/+1
| | | | | | establish DEFAULT_DATA_ALIGNMENT. Again, 0=64KiB, 1=1MiB, 2=2MiB Default is 1.
* Update heuristic used for default and detected data alignment.Mike Snitzer2010-08-201-3/+9
| | | | | | | | | | | | | | | | Add "devices/default_data_alignment" to lvm.conf to control the internal default that LVM2 uses: 0==64k, 1==1MB, 2==2MB, etc. If --dataalignment (or lvm.conf's "devices/data_alignment") is specified then it is always used to align the start of the data area. This means the md_chunk_alignment and data_alignment_detection are disabled if set. (Same now applies to pvcreate --dataalignmentoffset, the specified value will be used instead of the result from data_alignment_offset_detection) set_pe_align() still looks to use the determined default alignment (based on lvm.conf's default_data_alignment) if the default is a multiple of the MD or topology detected values.
* Various small cleanups and fixes related to monitoring.Alasdair Kergon2010-08-161-3/+7
|
* Change default alignment of pe_start to 1MB.Mike Snitzer2010-08-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new standard in the storage industry is to default alignment of data areas to 1MB. fdisk, parted, and mdadm have all been updated to this default. Update LVM to align the PV's data area start (pe_start) to 1MB. This provides a more useful default than the previous default of 64K (which generally ended up being a 192K pe_start once the first metadata area was created). Before this patch: # pvs -o name,vg_mda_size,pe_start PV VMdaSize 1st PE /dev/sdd 188.00k 192.00k After this patch: # pvs -o name,vg_mda_size,pe_start PV VMdaSize 1st PE /dev/sdd 1020.00k 1.00m The heuristic for setting the default alignment for LVM data areas is: - If the default value (1MB) is a multiple of the detected alignment then just use the default. - Otherwise, use the detected value. In practice this means we'll almost always use 1MB -- that is unless: - the alignment was explicitly specified with --dataalignment - or MD's full stripe width, or the {minimum,optimal}_io_size exceeds 1MB - or the specified/detected value is not a power-of-2
* Require --restorefile when using pvcreate --uuid.Mike Snitzer2010-08-121-0/+3
| | | | | | | | | Introduce --norestorefile to allow user to override the new requirement. This can also be overridden with "devices/require_restorefile_with_uuid" in lvm.conf -- however the default is 1. Signed-off-by: Mike Snitzer <snitzer@redhat.com>
* Clean generated files .exported_symbols_generated, example.conf for distclean.Zdenek Kabelac2010-08-031-0/+2
|
* Initial import of document describing LVM's policiesJonathan Earl Brassow2010-07-261-0/+221
| | | | surrounding device faults/failures.
* Always pass unsuspended dm devices through persistent filter to other filters.Alasdair Kergon2010-07-021-7/+9
| | | | Move test for suspended dm devices ahead of other filters.
* pre-releaseAlasdair Kergon2010-06-301-1/+1
|
* Update example.conf.in to describe vgmetadatacopies.Dave Wysochanski2010-06-281-0/+11
| | | | | | | Update example.conf to describe vgmetadatacopies. Provide an explanation for the '0' ("unmanaged") value. Signed-off-by: Dave Wysochanski <dwysocha@redhat.com>
* Fix lvm2cmd example in documentation.Milan Broz2010-06-161-2/+3
|
* Add install_system_dirs makefile target.Alasdair Kergon2010-05-201-7/+7
| | | | Add configure options for system and locking directories.
* Generate example.conf so default lvm.conf contents can be configured.Alasdair Kergon2010-05-202-1/+1
|
* Add activation/polling_interval to lvm.conf as --interval default.Alasdair Kergon2010-04-131-2/+10
|
* INSTALL rules updatesZdenek Kabelac2010-04-091-4/+3
| | | | | | | | | | | | | | | | | | | | | | | | | Patch is inspired by Debian's extra patch. - removes OWNER & GROUP make vars they are parts of INSTALL command. - adds INSTALL_PROGRAM for executable, uses $(INSTALL) - adds INSTALL_DATA for non-executable data, uses ($INSTALL) - adds INSTALL_WDATA for writable non-executable data, uses ($INSTALL) - adds configure option --enable-write_install - to support installatin of writable files used by distribution - replaces usage of ifeq @LIB_SUFFIX@ with $(LIB_SUFFIX) - installs .a files from static builds without executable flag - installs .a files to $(usrlibdir) instead of $(libdir) - installs all static binaries to $(staticdir) - create .so links for devel package in $(usrlibdir) instead of $(libdir) - makes .so and .so.LIB_VERSION files within builddir - removes VERSIONED_SHLIB and created versioned LIB_SHARED automagicaly - install LIB_SHARED via install_lib_shared target - install plugins via install_lib_shared_plugin target - prints whole 'install' command during installation instead of less informative "Installing $(something) $(somewhere)" - install multiple man pages with one INSTALL command - use DISTCLEAN_TARGETS instead of creating multiple distclean targets
* Use vpath instead of VPATH.Zdenek Kabelac2010-04-091-2/+1
| | | | | | | | | | | | | | | Usage of VPATH makes troubles when used within $(builddir). Not only source files are being found through VPATH, but targets as well. (make --debug=v) Thus if user builds the code in $(srcdir) and also in some $(builddir) he gets mangled results as some generated files (i.e. .export.sym) are 'reused' from $(srcdir) instead of $(builddir). This patch switches to use vpath were we could explicitly name suffixes that should be looked via vpath - we must take care, we do not generate files with these suffixes: .c, .in, .po, .exported_symbols
* Improve activation monitoring option processingMike Snitzer2010-03-231-0/+4
| | | | | | | | | | | | | . Add "monitoring" option to "activation" section of lvm.conf . Have clvmd consult the lvm.conf "activation/monitoring" too. . Introduce toollib.c:get_activation_monitoring_mode(). . Error out when both --monitor and --ignoremonitoring are provided. . Add --monitor and --ignoremonitoring support to lvcreate. Update lvcreate man page accordingly. . Clarify that '--monitor' controls the start and stop of monitoring in the {vg,lv}change man pages. Signed-off-by: Mike Snitzer <snitzer@redhat.com>
* mlockall() -> mlock()Zdenek Kabelac2010-03-051-0/+15
| | | | | | | | | | | | | | | | | This patch adds a new implementation of locking function instead of mlockall() that may lock way too much memory (>100MB). New function instead uses mlock() system call and selectively locks memory areas from /proc/self/maps trying to avoid locking areas unused during lock-ed state. Patch also adds struct cmd_context to all memlock() calls to have access to configuration. For backward compatibility functionality of mlockall() is preserved with "activation/use_mlockall" flag. As a simple check, locking and unlocking counts the amount of memory and compares whether values are matching.
* Use $(top_builddir) for inclusion of make.tmpl in Makefiles.Zdenek Kabelac2010-03-041-1/+1
|
* Add activation/udev_rules config option in lvm.conf.Peter Rajnoha2010-01-071-1/+8
| | | | Add dm_tree_add_dev_with_udev_flags to provide wider support for udev flags.
* Rename mirror_device_fault_policy to mirror_image_fault policyMilan Broz2010-01-061-1/+1
|
* Optionally abort on internal errors (and leverage this option in thePetr Rockai2009-11-301-0/+4
| | | | | testsuite). (This is showing a problem in the pvmove test for me, so I expect the tests to start failing -- this needs to be fixed separately though.)
* Correct example.conf to indicate that lvm2 not lvm1 is the default format.Alasdair Kergon2009-10-051-2/+2
| | | | Remove an unused stray LVM1_SUPPORT ifdef.
* Allow for a build directory separate from the source.Alasdair Kergon2009-10-021-3/+4
|
* Add global/si_unit_consistency to enable cleaned-up use of units in output.Alasdair Kergon2009-09-281-0/+7
| | | | | | Add configure --enable-units-compat to set si_unit_consistency off by default. Use standard output units for 'PE Size' and 'Stripe size' in pv/lvdisplay.
* Enable dmeventd monitoring section of config file by default.Alasdair Kergon2009-09-161-5/+4
|
* pre-release cleanupAlasdair Kergon2009-09-151-5/+9
|
* Add y|--yes option for dmsetup to provide a default 'YES' answer to questions.Peter Rajnoha2009-09-111-1/+1
|
* Implement write lock prioritisation for file locking and make it default.Petr Rockai2009-09-021-0/+7
|
* Add activation/udev_sync to lvm.conf.Alasdair Kergon2009-08-041-0/+10
|
* Add devices/data_alignment_detection to lvm.conf.Mike Snitzer2009-08-011-2/+14
| | | | | | | | | | | | | | Adds 'data_alignment_detection' config option to the devices section of lvm.conf. If your kernel provides topology information in sysfs (linux >= 2.6.31) for the Physical Volume, the start of data area will be aligned on a multiple of the ’minimum_io_size’ or ’optimal_io_size’ exposed in sysfs. minimum_io_size is used if optimal_io_size is undefined (0). If both md_chunk_alignment and data_alignment_detection are enabled the result of data_alignment_detection is used. Signed-off-by: Mike Snitzer <snitzer@redhat.com>
* Add devices/data_alignment_offset_detection to lvm.conf.Mike Snitzer2009-08-011-0/+9
| | | | | | | | | If the pvcreate --dataalignmentoffset option is not specified the start of a PV's aligned data area will be shifted by the associated 'alignment_offset' exposed in sysfs (unless devices/data_alignment_offset_detection is disabled in lvm.conf). Signed-off-by: Mike Snitzer <snitzer@redhat.com>
* Add global/wait_for_locks to lvm.conf so blocking on locks can be disabled.Alasdair Kergon2009-07-241-0/+3
|
* Store any errno and error messages issued while processing each command.Alasdair Kergon2009-07-151-1/+2
| | | | | (Enabled by default while we test it, but in due course we'll only store the error messages when we need to.)
* Use the MD device's stripe-width, instead of chunk_size, to align theMike Snitzer2009-07-061-1/+1
| | | | | data blocks of a Physical Volume that is placed directly upon an MD device.
* Use lvconvert --repair instead of vgreduce in mirror dmeventd DSO (mornfall)Milan Broz2009-06-041-15/+10
| | | | Introduce lvconvert --use_policies (mornfall)
* Introduce lvm2_install target.Milan Broz2009-05-111-1/+2
| | | | | | | | | | | | | | | Buildsystem support device-mapper only install, but generic install tagret includes both dm+lvm2. For distribution which uses separate install_device-mapper, there is no way how to install lvm2 only (so after installing lvm2 for packaging purposes built system must remove installed device-mapper files). Fix it by allowing lvm2_install target, similarily like install_cluster for clvmd. (install = install_device-mapper + install_lvm2)
* Add --dataalignment to pvcreate to specify alignment of data area. (mbroz)Alasdair Kergon2009-02-221-4/+10
| | | | | | | | | | | | | | | | | | This patch is not fully tested and leaves some related bugs unfixed. Intended behaviour of the code now: pe_start in the lvm2 format PV label header is set only by pvcreate (or vgconvert -M2) and then preserved in *all* operations thereafter. In some specialist cases, after the PV is added to a VG, the pe_start field in the VG metadata may hold a different value and if so, it overrides the other one for as long as the PV is in such a VG. Currently, the field storing the size of the data area in the PV label header always holds 0. As it only has meaning in the context of a volume group, it is calculated whenever the PV is added to a VG (and can be derived from extent_size and pe_count in the VG metadata).
* Improve the way VGs with PVs missing are handled so manual interventionAlasdair Kergon2008-09-191-5/+7
| | | | is required in fewer circumstances. (mornfall)
* Add device/md_chunk_alignment to lvm.confAlasdair Kergon2008-09-191-0/+5
|
* .Alasdair Kergon2008-04-101-3/+2
|
* Reflect actual default setting of preferred_names in example.conf andDave Wysochanski2008-02-111-4/+4
| | | | update comments.
* Fix default preferred_names filter to use /dev/mapper/mpath devices.Dave Wysochanski2008-02-041-2/+4
| | | | | | | If these devices exist, we should be using them for multipath rather than any underlying device names. Reference: http://kbase.redhat.com/faq/FAQ_96_11196.shtma bz195685
* Add snapshot dmeventd library (enables dmeventd snapshot monitoring).Petr Rockai2008-01-091-4/+14
|
* Enhance the management of readahead settings.Alasdair Kergon2007-11-091-0/+6
|
generated by cgit (git 2.34.1) at 2024-06-14 11:29:44 +0000