1
0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-22 17:35:59 +03:00
lvm2/tools/vgscan.c

131 lines
4.4 KiB
C
Raw Normal View History

2001-10-12 01:35:55 +04:00
/*
2008-01-30 17:00:02 +03:00
* Copyright (C) 2001-2004 Sistina Software, Inc. All rights reserved.
* Copyright (C) 2004-2009 Red Hat, Inc. All rights reserved.
2001-10-12 01:35:55 +04:00
*
2004-03-30 23:35:44 +04:00
* This file is part of LVM2.
2001-10-12 01:35:55 +04:00
*
2004-03-30 23:35:44 +04:00
* This copyrighted material is made available to anyone wishing to use,
* modify, copy, or redistribute it subject to the terms and conditions
* of the GNU Lesser General Public License v.2.1.
2001-10-12 01:35:55 +04:00
*
* You should have received a copy of the GNU Lesser General Public License
2004-03-30 23:35:44 +04:00
* along with this program; if not, write to the Free Software Foundation,
* Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
2001-10-12 01:35:55 +04:00
*/
#include "tools.h"
static int _vgscan_single(struct cmd_context *cmd, const char *vg_name,
struct volume_group *vg,
struct processing_handle *handle __attribute__((unused)))
2002-11-18 17:04:08 +03:00
{
log_print_unless_silent("Found %svolume group \"%s\" using metadata type %s",
vg_is_exported(vg) ? "exported " : "", vg_name,
vg->fid->fmt->name);
2002-11-18 17:04:08 +03:00
check_current_backup(vg);
2003-10-22 02:06:07 +04:00
return ECMD_PROCESSED;
2002-11-18 17:04:08 +03:00
}
2001-10-12 01:35:55 +04:00
/*
* Two main vgscan cases related to lvmetad usage:
* 1. vgscan
* 2. vgscan --cache
*
* 1. The 'vgscan' command (without --cache) may or may not attempt to
* repopulate the lvmetad cache, and may or may not use the lvmetad
* cache to display VG info:
*
* i. If lvmetad is being used and is in a normal state, then 'vgscan'
* will simply read and display VG info from the lvmetad cache.
*
* ii. If lvmetad is not being used, 'vgscan' will read all devices to
* display the VG info.
*
* iii. If lvmetad is being used, but has been disabled (because of
* duplicate devs or lvm1 metadata), or has a non-matching token
* (because the device filter is different from the device filter last
* used to populate lvmetad), then 'vgscan' will begin by rescanning
* devices to repopulate lvmetad. If lvmetad is enabled after the
* rescan, then 'vgscan' will simply read and display VG info from the
* lvmetad cache (like case i). If lvmetad is disabled after the
* rescan, then 'vgscan' will read all devices to display VG info
* (like case ii).
*
* 2. The 'vgscan --cache' command will always attempt to repopulate
* the lvmetad cache by rescanning all devs (regardless of whether
* lvmetad was previously disabled or had an unmatching token.)
* lvmetad may be enabled or disabled after the rescan (depending
* on whether duplicate devs or lvm1 metadata was found).
* If enabled, then it will simply read and display VG info from the
* lvmetad cache (like case 1.i.). If disabled, then it will
* read all devices to display VG info (like case 1.ii.)
*/
int vgscan(struct cmd_context *cmd, int argc, char **argv)
2001-10-12 01:35:55 +04:00
{
const char *reason = NULL;
int maxret, ret;
2003-11-14 17:03:48 +03:00
2001-10-12 01:35:55 +04:00
if (argc) {
log_error("Too many parameters on command line");
return EINVALID_CMD_LINE;
}
if (arg_is_set(cmd, notifydbus_ARG)) {
if (!lvmnotify_is_supported()) {
log_error("Cannot notify dbus: lvm is not built with dbus support.");
return ECMD_FAILED;
}
if (!find_config_tree_bool(cmd, global_notify_dbus_CFG, NULL)) {
log_error("Cannot notify dbus: notify_dbus is disabled in lvm config.");
return ECMD_FAILED;
}
set_pv_notify(cmd);
set_vg_notify(cmd);
set_lv_notify(cmd);
return ECMD_PROCESSED;
}
if (!lock_vol(cmd, VG_GLOBAL, LCK_VG_WRITE, NULL)) {
log_error("Unable to obtain global lock.");
return ECMD_FAILED;
}
if (cmd->filter->wipe)
cmd->filter->wipe(cmd->filter);
lvmcache_destroy(cmd, 1, 0);
if (!lvmetad_used() && arg_is_set(cmd, cache_long_ARG))
log_verbose("Ignoring vgscan --cache command because lvmetad is not in use.");
if (lvmetad_used() && (arg_is_set(cmd, cache_long_ARG) || !lvmetad_token_matches(cmd) || lvmetad_is_disabled(cmd, &reason))) {
if (lvmetad_used() && !lvmetad_pvscan_all_devs(cmd, arg_is_set(cmd, cache_long_ARG))) {
log_warn("WARNING: Not using lvmetad because cache update failed.");
lvmetad_make_unused(cmd);
}
if (lvmetad_used() && lvmetad_is_disabled(cmd, &reason)) {
log_warn("WARNING: Not using lvmetad because %s.", reason);
lvmetad_make_unused(cmd);
}
}
if (!lvmetad_used())
log_print_unless_silent("Reading all physical volumes. This may take a while...");
else
log_print_unless_silent("Reading volume groups from cache.");
2001-10-12 01:35:55 +04:00
maxret = process_each_vg(cmd, argc, argv, NULL, NULL, 0, 0, NULL, &_vgscan_single);
2003-11-14 17:03:48 +03:00
if (arg_is_set(cmd, mknodes_ARG)) {
2003-11-14 17:03:48 +03:00
ret = vgmknodes(cmd, argc, argv);
if (ret > maxret)
maxret = ret;
}
lvmetad: two phase vg_update Previously, a command sent lvmetad new VG metadata in vg_commit(). In vg_commit(), devices are suspended, so any memory allocation done by the command while sending to lvmetad, or by lvmetad while updating its cache could deadlock if memory reclaim was triggered. Now lvmetad is updated in unlock_vg(), after devices are resumed. The new method for updating VG metadata in lvmetad is in two phases: 1. In vg_write(), before devices are suspended, the command sends lvmetad a short message ("set_vg_info") telling it what the new VG seqno will be. lvmetad sees that the seqno is newer than the seqno of its cached VG, so it sets the INVALID flag for the cached VG. If sending the message to lvmetad fails, the command fails before the metadata is committed and the change is not made. If sending the message succeeds, vg_commit() is called. 2. In unlock_vg(), after devices are resumed, the command sends lvmetad the standard vg_update message with the new metadata. lvmetad sees that the seqno in the new metadata matches the seqno it saved from set_vg_info, and knows it has the latest copy, so it clears the INVALID flag for the cached VG. If a command fails between 1 and 2 (after committing the VG on disk, but before sending lvmetad the new metadata), the cached VG retains the INVALID flag in lvmetad. A subsequent command will read the cached VG from lvmetad, see the INVALID flag, ignore the cached copy, read the VG from disk instead, update the lvmetad copy with the latest copy from disk, (this clears the INVALID flag in lvmetad), and use the correct VG metadata for the command. (This INVALID mechanism already existed for use by lvmlockd.)
2016-06-08 22:42:03 +03:00
unlock_vg(cmd, NULL, VG_GLOBAL);
2003-11-14 17:03:48 +03:00
return maxret;
2001-10-12 01:35:55 +04:00
}