| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Typos found with codespell.
|
|
|
|
| |
Two new settings for tuning dm-writecache.
|
|
|
|
| |
Use <name> consistenly.
|
|
|
|
|
|
|
|
|
|
|
| |
Add a note to the manpage that lvmlockd is unable to determine
accurately and without side-effects whether a LV is remotely active.
Also change the value of the lv_active_remotely option from false to
undefined for shared VGs to distinctly communicate that inability to
users. Only for local VGs it can be definitely stated that they are not
remotely active.
Signed-off-by: corubba <corubba@gmx.de>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new --valuesonly option causes the lvmconfig output to contain only
values without keys for each config node. This is practical mainly in
case where we use lvmconfig in scripts and we want to assign the value
to a different custom key or simply output the value itself without the
key.
For example:
# lvmconfig --type full activation/raid_fault_policy
raid_fault_policy="warn"
# lvmconfig --type full activation/raid_fault_policy --valuesonly
"warn"
# my_var=$(lvmconfig --type full activation/raid_fault_policy --valuesonly)
# echo $my_var
"warn"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with json_std format
Internally, NUM and BIN fields are marked as DM_REPORT_FIELD_TYPE_NUM_NUMBER
through libdevmapper API. The new 'json_std' format mandates that the report
string representing such a value must be a number, not an arbitrary string.
This is because numeric values in 'json_std' format do not have double quotes
around them. This practically means, we can't use string synonyms
("named reserved values") for such values and the report string must always
represent a proper number.
With 'json' and 'basic' formats, this is not an issue because 'basic' format
doesn't have any structure or typing at all and 'json' format puts all values
in quotes, including numeric ones.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Add more info about kernel target memory allocation associated with
VDO pool usage.
|
|
|
|
|
| |
Put space between size and SI unit.
Automatically make this 'space' as fixed size by Makefile sed script.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Allow to use --vdosettings with lvcreate,lvconvert,lvchange.
Support settings currenly only configurable via lvm.conf.
With lvchange we require inactivate LV for changes to be applied.
Settings block_map_era_length has supported alias block_map_period.
|
|
|
|
|
| |
When used with --deviceidtype, --deldev can specify
a device id to remove.
|
|
|
|
|
| |
lvs was missing the ability to display writecache block size.
now possible with lvs -o writecache_block_size
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
This reverts commit d5a950ca67c106403054ecb847e226e8b5a7c30e.
This commit did not properly recognize GPT cases.
|
|
|
|
|
|
|
| |
$ pvcreate /dev/sdc
Cannot use /dev/sdc: device is partitioned
$ pvcreate -f /dev/sdc
Physical volume "/dev/sdc" successfully created.
|
| |
|
| |
|
|
|
|
| |
new topical man page describing autoactivation
|
| |
|
| |
|
|
|
|
|
|
|
| |
The new system_id_source="appmachineid" will cause
lvm to use an lvm-specific derivation of the machine-id,
instead of the machine-id directly. This is now
recommended in place of using machineid.
|
|
|
|
|
|
|
| |
Add support for DM_IMA_MEASUREMENT_FLAG with
DM_TABLE_STATUS_CMD.
This feature requires DM version 4.45 (5.15+ kernels)
|
| |
|
|
|
|
| |
Dry-run is way more usable when it's verbose.
|
| |
|
|
|
|
| |
Missed bits in previous rename commits.
|
| |
|
| |
|
|
|
|
|
|
|
| |
When splitting VG with thin/cache pool volume, handle pmspare during
such split and allocate new pmspare in new VG or extend existing pmspare
there and eventually drop pmspare in original VG if is no longer needed
there.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When adding a device to the devices file with --adddev, lvm
by default chooses the best device ID type for the new device.
The new --deviceidtype option allows the user to override the
built in preference. This is useful if there's a problem with
the default type, or if a secondary type is preferrable.
If the specified deviceidtype does not produce a device ID,
then lvm falls back to the preference it would otherwise use.
|
| |
|
| |
|
|
|
|
| |
Add supporting target for recreating man-generator when dependencies needs it.
|
|
|
|
| |
Add some examples with -l% usage.
|
| |
|
|
|
|
|
|
|
| |
Missed -l option in man page, although users should prefer
lvresize -r when the also want to do a volume management,
as there they can specify i.e. extents for allocation.
Also mention dm-crypt support in command description.
|
| |
|