| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Previously there have been necessary explicit call of backup (often
either forgotten or over-used). With this patch the necessity to
store backup is remember at vg_commit and once the VG is unlocked,
the committed metadata are automatically store in backup file.
This may possibly alter some printed messages from command when the
backup is now taken later.
|
| |
|
|
|
|
| |
Between 'resume' and 'remove' we need to wait for udev to synchronize,
otherwise udev may 'skip' resume event processing if the udev node
is already gone.
|
| |
|
|
| |
Move code manipulating with locking flags into /lib part of lvm.
|
| |
|
|
|
| |
Correct printed lv names in error messages
and add missing trace for return.
|
| |
|
|
| |
Activation code can see from holders needed LVs for resume.
|
| | |
|
| | |
|
| |
|
|
| |
Call lv_update_and_reload implementation.
|
| |
|
|
|
| |
For proper locking we need to gain lock first for mirror which
needs to be deactivated later to be working in cluster.
|
| |
|
|
|
| |
Hmm rpmlint suggest fsf is using a different address these days,
so lets keep it up-to-date
|
| | |
|
| |
|
|
| |
vg cannot be NULL here - it's been already used in the code above.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Routines responsible for polling of in-progress pvmove, snapshot merge
or mirror conversion each used custom lookup functions to find vg and
lv involved in polling.
Especially pvmove used pvname to lookup pvmove in-progress. The future
lvmpolld will poll each operation by vg/lv name (internally by lvid).
Also there're plans to make pvmove able to move non-overlaping ranges
of extents instead of single PVs as of now. This would also require
to identify the opertion in different manner.
The poll_operation_id structure together with daemon_parms structure they
identify unambiguously the polling task.
|
| |
|
|
|
| |
with refactored code we take some VG locks as read-only.
Make the poll_get_copy_vg ready for the change.
|
| |
|
|
|
| |
basically transfer former date ranges from files where
the code originated from (pvmove.c and lvconvert.c)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far pvmove_update_metadata (originaly _update_metadata) was
used for both initial and subsequent metadata updates during polling.
With a new polldaemon (lvmpolld) all operations that require polling
have to be split in two parts: The initiating one and the polling one.
The later step will be used from lvm command spawned by lvmpolld to
monitor and advance the mirror on next segment if required.
1) The initiation part is _update_metadata in pvmove.c which performs
only the first update, setting up the pvmove itself in metadata.
2) pvmove_update_metadata in pvmove_poll.c now handles all other
subsequent metadata updates except the last one.
Due to the split we could remove some code. Also some functions were
moved back to pvmove.c as they were suited for initialisation of pvmove
only.
|
|
|
This commit has no impact on functionality. Code required to
be visible outside pvmove.c is just moved into new file
pvmove_poll.c and some calls are made non-static and declared in
new header file pvmove.h
|
