summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* [WIP] test: Add _prepare_lvmdbusddev-mcsontos-test-dbusd-2Marian Csontos2016-03-082-4/+44
|
* test: Update kernels to skip thin-flags withMarian Csontos2016-03-081-0/+2
| | | | See ed5e5c38b5ac4b7c8cb7e809d9d35c72f087e29e
* [WIP] Get lvmdbusd work properlyMarian Csontos2016-03-081-0/+14
|
* Revert "test: dbus autolaunch needs an env.variable"Marian Csontos2016-03-081-2/+0
| | | | | | | This reverts commit c501413c8a0617323544fdb828c29a3d6bf921c5. Conflicts: test/api/dbustest.sh
* test: dbus autolaunch needs an env.variableMarian Csontos2016-03-081-0/+2
| | | | We need either DISPLAY or DBUS_SESSION_BUS_ADDRESS
* [WIP][untested] spec: Add hint-dependencies (`Suggests`)Marian Csontos2016-03-082-0/+10
| | | | (cherry picked from commit 2c4678f2d2d8c61e1100d40d60ede34a48912c3b)
* test: Turn on dbus testMarian Csontos2016-03-081-1/+1
|
* spec: Add missing dependency for dbusdMarian Csontos2016-03-081-0/+1
| | | | (cherry picked from commit 7435de21492f6b37ac7664d1f27b4a8dcc4d0dd4)
* toollib: always process in use pvsDavid Teigland2016-03-071-6/+0
| | | | | | | | | | | | With the recent conversion of pvcreate/pvremove to the common toollib processing function, skipping in-use PVs in _process_pvs_in_vg prevented them from being protected as intended by the in-use flag. The processing code for pvcreate/pvremove checks for the in-use state itself and prevents using an in-use PV. If a PV is skipped, it looks like an unused device and is not protected from being used in pvcreate/pvremove.
* vgscan: add --notifydbus to send a notificationDavid Teigland2016-03-077-1/+36
| | | | | | | | | This command option can be used to trigger a D-Bus notification independent of the usual notifications that are sent from other commands as an effect of changes to PV/VG/LV state. If lvm is not built with dbus notification support or if notify_dbus is disabled in the config, this command will exit with an error.
* dbus: add notification from commandsDavid Teigland2016-03-0717-1/+187
| | | | | | | When a command modifies a PV or VG, or changes the activation state of an LV, it will send a dbus notification when the command is finished. This can be enabled/disabled with a config setting.
* raid_manip: allow for raid leg to be replaced when not both data and ↵Heinz Mauelshagen2016-03-071-1/+1
| | | | | | metadata image are on pvs resolves rhbz#1130329
* coverity: fix possible resource leak in _print_historical_lv functionPeter Rajnoha2016-03-072-6/+7
| | | | | | | | | | | | | | | | | The code in _print_historical_lv function works with temporary "descendants_buffer" that is allocated and freed within this function. When printing text out, we used "outf" macro which called "out_text" fn and it checked return value and if failed, the macro called "return_0" automatically. But since we use the temporary buffer, if any of the out_text calls fails, we need to deallocate this buffer properly - that's the "goto_out", otherwise we'll be leaking memory. So add new "outfgo" helper macro which does the same as "outf", but it calls "goto_out" instead of "return_0" so we can jump to a cleanup hook at the end.
* post-releaseAlasdair G Kergon2016-03-044-2/+8
|
* pre-releasev2_02_145Alasdair G Kergon2016-03-044-6/+6
|
* lvmdbusd: Set localeTony Asleson2016-03-041-0/+3
| | | | Signed-off-by: Tony Asleson <tasleson@redhat.com>
* dbustest.sh: Get dbus test to work on buildbotMarian Csontos2016-03-041-16/+14
| | | | | | | | | | | | | | | - stdout/stderr for test output - debug.log* for daemon output - use install instead of cp for DBus config - use system bus - DBus reloads on new file. Better having it created with correct permissions. Notes: - Squashed commits from mcsontos development branch - Still disabled at this time Signed-off-by: Tony Asleson <tasleson@redhat.com>
* libdm: config: fix dm_config_write_node and variants to properly return ↵Peter Rajnoha2016-03-042-1/+3
| | | | | | | | error on failures The error was not propagated if _write_config (that is part of dm_config_write_node and all its variants) was called recursively for subsections.
* cleanup: previous patch with libdm config node buffer sizePeter Rajnoha2016-03-041-5/+7
|
* libdm: config: remove 4096 char limit due to buffer size if writing ↵Peter Rajnoha2016-03-042-2/+25
| | | | dm_config_node
* WHATS_NEW: historical LVsPeter Rajnoha2016-03-041-0/+13
|
* man: lvrename: also mention possibility to rename historical logical volumesPeter Rajnoha2016-03-041-1/+2
|
* cleanup: comment in the code for renaming historical LVsPeter Rajnoha2016-03-041-1/+4
|
* lvrename: support renaming historical logical volumesPeter Rajnoha2016-03-042-34/+95
|
* commands: lvdisplay: recognize -H|--history switchPeter Rajnoha2016-03-042-4/+37
|
* tests: direct control of lvm1 usage in testsDavid Teigland2016-03-0314-20/+94
| | | | | | | | | | | | | | | | Using lvm1 metadata with lvmetad is not generally allowed, but nothing has prevented creating new lvm1 metadata with lvmetad (missing error checking in pvcreate/vgcreate.) Various tests are using lvm1 with lvmetad and happen to work because of the missing error checks. This commit fixes the tests so they won't fail when the lvm1/lvmetad error checking is fixed. A new variable LVM_TEST_LVM1 is defined and is used in the scripts to decide if lvm1 metadata should be tested. LVM_TEST_LVM1 is not defined when lvmetad is being tested, and the combination of LVM_TEST_LVM1 and LVM_TEST_LVMETAD can be used to verify the desired lvmetad+lvm1 behavior.
* man: Add some information about historical LVs.Alasdair G Kergon2016-03-033-6/+45
|
* tests: add lv-ancestry.sh testPeter Rajnoha2016-03-031-0/+226
|
* tests: add "get lvh_field" for "lvs -H"Peter Rajnoha2016-03-032-0/+11
|
* lvmdump: also list historical LVs in lvmdumpPeter Rajnoha2016-03-031-1/+1
|
* metadata: automatically remove invalid (dangling) historical LVsPeter Rajnoha2016-03-032-1/+48
| | | | | | Historical LV is valid as long as there is at least one live LV among its ancestors. If we find any invalid (dangling) historical LVs, remove them automatically.
* metadata: also validate historical LVs in VG in vg_validate and ↵Peter Rajnoha2016-03-032-0/+108
| | | | check_lv_segments
* metadata: also look at historical LVs when checking LV name availabilityPeter Rajnoha2016-03-037-23/+67
| | | | | Live LVs and historical LVs are in one namespace and the name needs to be unique in whole VG.
* conf: regenerate example.conf.inPeter Rajnoha2016-03-031-0/+16
|
* conf: add metadata/lvs_history_timeout configuration settingPeter Rajnoha2016-03-033-1/+8
|
* metadata: add vg_strip_outdated_historical_lvs fn and call it during VG readPeter Rajnoha2016-03-032-1/+40
| | | | | | | The vg_strip_outdated_historical_lvs iterates over the list of historical LVs we have and it shoots down the ones which are outdated. Configuration hook to set the timeout will be in subsequent patch.
* commands: lvremove: also process historical LVsPeter Rajnoha2016-03-033-7/+16
|
* metadata: add historical_glv_removePeter Rajnoha2016-03-036-5/+82
|
* conf: add metadata/record_lvs_history configuration settingPeter Rajnoha2016-03-033-2/+10
| | | | | | | | | The metadata/record_lvs_history is global switch which enables or disables recording historical LVs in metadata. If both metadata/record_lvs_history=1 lvm.conf option and --nohistory command switch is used at the same time, the --nohistory prevails.
* commands: lvremove: recognize --nohistory optionPeter Rajnoha2016-03-031-1/+2
|
* metadata: honour 'nohistory' switch when removing thin LVsPeter Rajnoha2016-03-031-4/+11
| | | | | When --nohistory switch is used with lvremove, the LV that is removed is not recorded in metadata as 'historical LV'.
* cmd: add 'nohistory' option and wire it up in cmd_contextPeter Rajnoha2016-03-033-0/+4
| | | | | The --nohistory switch will cause historical LVs to not be recorded in metadata on demand.
* report: add new 'none' lv_layout and 'history' lv_role and mark historical ↵Peter Rajnoha2016-03-031-0/+10
| | | | | | | | | | | | | LVs that way Report proper values for historical LVs in lv_layout and lv_role fields. Any historical LV doesn't have any layout anymore and the role is "history". For example: $ lvs -H -o name,lv_attr,lv_layout,lv_role vg/-lvol1 LV Attr Layout Role -lvol1 ----h----- none public,history
* report: add full_descendants field to display descendants with historyPeter Rajnoha2016-03-033-16/+89
| | | | Same as lv_full_ancestors, but the other way round in the ancestry chain.
* report: add full_ancestors field to display ancestors with historyPeter Rajnoha2016-03-033-14/+76
| | | | | | The lv_full_ancestors reporting field is just like the existing lv_ancestors field but it also takes into account any history and indirect relations recorded.
* report: report historical LV names with '-' prefixPeter Rajnoha2016-03-031-7/+16
| | | | | | | All names for historical LVs are prefixed with '-' character to make clear difference between live and historical LVs. The '-' can't be set by users for live LV names during lvcreate hence we never get into a conflict with the names that user defines for live LVs.
* report: display (h)istorical state in lv_attr fieldPeter Rajnoha2016-03-031-2/+5
| | | | | The 'historical' state is displayed as 5th bit ("state") in the lv_attr field and denoted by new 'h' character.
* report: add lv_historical field to identify historical LVsPeter Rajnoha2016-03-033-0/+11
| | | | | | The lv_historical reporting field is a simple binary field that reports whether an LV is historical one ("historical" value or value of "1" displayed) or not (blank string "" or value of "0" displayed).
* commands: lvs: recognize -H|--history switchPeter Rajnoha2016-03-031-5/+7
| | | | | When lvs command is used together with the -H|--history switch, all historical LVs are reported as well.
* report: display lv_name,lv_uuid,vg_name,lv_time and new lv_time_removed for ↵Peter Rajnoha2016-03-037-10/+72
| | | | historical LVs
View Lorry Controller Status