| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The MD kernel raid1 personality does no use any writemostly leg as the primary.
In case a previous linear LV holding data gets upconverted to
raid1 it becomes the primary leg of the new raid1 LV and a full
resynchronization is started to update the new legs.
No writemostly and/or writebehind setting may be allowed during
this initial, full synchronization period of this new raid1 LV
(using the lvchange(8) command), because that would change the
primary (i.e the previous linear LV) thus causing data loss.
lvchange has a bug not preventing this scenario.
Fix rejects setting writemostly and/or writebehind on resychronizing raid1 LVs.
Once we have status in the lvm2 metadata about the linear -> raid upconversion,
we may relax this constraint for other types of resynchronization
(e.g. for user requested "lvchange --resync ").
New lvchange-raid1-writemostly.sh test is added to the test suite.
Resolves: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855895
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We use --foo Number[k|Units] to indicate that
the default units of the number is k, but other
units listed below are also accepted.
Capitalize and underline Units so it is consistent
with other variables, and reference it at the end.
Technically, the k should be bold, but this
tends to make the text visually hard to read
because of the excessive highlights scattered
everywhere. So it's left normal text for now
(it's unlikely to confuse anyone.)
|
| |
|
|
|
|
| |
Print ... after a repeatable option in the OPTIONS section.
An alternative would be to just mention in the text description
that the option is repeatable.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
When the test would need to try to write some large amount of data
we can give it 'zero' segments - for obvious reason such written data
can't be verified but in some test cases it doesn't really matter.
Usage follows 'error_dev' style.
For now test suite is not supporting any combination of
error/delay/zero segments so only 1 type could be used per PV.
|
| |
|
|
| |
Slows only data extents on a PV.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Previously when lvremove tried to remove 'active' origin,
it had been asking for every 'snapshot' LV separately
and doing individual single snapshot removals first.
To be faster it now deactivates origin before removal
all connected snapshots.
This avoids multiple reloads of dm table for origin volume
which were unnecessary as origin was meant to be removed as well.
|
| | |
|
| |
|
|
|
| |
Placing [] around each individual option is the most
common style, and it improves the readability.
|
| |
|
|
|
|
|
|
|
|
|
| |
There are two kinds of common options:
1. options common to all variants of a given command name
2. options common to all lvm commands
Previously, both kinds of common options were listed together
under "Common options". Now the first are printed under
"Common options for command" (when needed), and the second
are printed under "Common options for lvm" (always).
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Remove the "usage notes" which should just
live in the man pages.
When there are 3 or more variants of a command,
print all the options produces a lot of output,
so require --longhelp to print all the options
in these cases.
|
| |
|
|
|
| |
add several missing references
remove references to lvmdiskscan lvmchange
|
| | |
|
| | |
|
| |
|
|
|
| |
Checking if --deferred would make it any faster - but it's as slow
as without this new optional flag anyway (4.10).
|
| |
|
|
|
|
|
| |
Check 'dmsetup version' is called before starting any more
advanced logic in $DM_DEV_DIR.
Call also replaces mkdir as it creates needed path with control node.
|
| | |
|
| |
|
|
|
|
| |
To speedup initial construction and destruction of test devices
(mainly in case more then 1 is needed) call dmsetup
in parallel.
|
| |
|
|
| |
Test suite does not support clustered mirroring.
|
| | |
|
| |
|
|
|
| |
Instead of printing "raid*". There are already
notes mentioning that "raid" refers to "raid<N>"
|
| | |
|
| |
|
|
|
|
| |
The --name, --size, --extents options deserve a special
note at the start of the man page, before appearing in
the usage section.
|
| |
|
|
|
|
|
|
| |
Add a section describing variables.
In the full options list, include common
options in the alphabetical listing instead
of at the end.
|
| |
|
|
|
|
|
| |
The --type option has previously been accepted for
lvresize/lvextend. Using it did not affect the operation
of the command. The value was simply verified as matching
the current seg type of the LV.
|
| |
|
|
| |
Add missing tests for some lvresize acceptable options.
|
| |
|
|
| |
Already know string is 'lvm-' so use name[3].
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Document new dmeventd/thin_command lvm.conf configurable.
|
| |
|
|
| |
Fixing colorization bugs
|
| | |
|
| |
|
|
| |
Keep all allocations 'mempool' allocated for simple cleanup.
|
| |
|
|
|
|
|
|
|
|
| |
Commit f45b68940667563e1a8d3bbd5d30864c04381bdf caused regression
of lvresize -m and --type parameter
After fix this sequence may work when we also fix syntax description:
lvcreate -l1 -m1 -n lv1 vg
lvextend --type mirror -m1 -l+1 vg/lv1
|
| | |
|
| |
|
|
| |
print 'lvm config' not 'lvm-config'
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For this syntax:
lvconvert --thinpool LV1 --poolmetadata LV2
lvconvert --cachepool LV1 --poolmetadata LV2
Restore the metadata swapping behavior in addition to
the pool creation behavior. When LV1 is already a pool,
the metadata LV will be swapped with LV2.
When LV1 is not a pool, it will be converted to a
pool using the specified LV for metadata.
This syntax is no longer advertised because of the
ambiguous behavior. The primary syntaxes for pool
creation and metadata swapping will be the advertised
methods.
|
| |
|
|
|
|
|
|
|
|
|
| |
As we now user binary search - it's nondeterministict
which of the same 'args' will be give - so duplicates
need 'extra' care.
So provide same hack for output for --uuidstr_ARG as
for input.
Solves 'pvscan -u'.
|
| |
|
|
| |
As man-generator is not liked with libdm as of now - some more wrappers.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since there is a lot of options and lot of searches,
use binary search to keep strcmp at minimum.
The interesting part is - alphabetically sorted array contains
duplicates and some of them are not the 'right anwer', so
after we find matching string but not matching long_ARG,
we may need to check if the surrouding strings are the right matching
one.
The single loops is used also for strictly define --foo_long
(i.e. --stripes) and just differs at final part.
TODO1: replace strstr call with some flag (just like short_opt).
TODO2: drop '--' from being stored and tests by strcmp.
|
