similar to: [PATCH] daemon: copy entire lvm directory

Currently lvmetad is started in init, and thus using the system (= appliance) configuration of lvm. Later on, in the daemon, a local copy of the lvm configuration is setup, and set it for use using the LVM_SYSTEM_DIR environment variable: this means only the programmes executed by the daemon will use the local lvm configuration, and not lvmetad. Thus manually start lvmetad from the daemon, right

When the daemon starts up it creates a fresh (empty) LVM configuration and starts up lvmetad (which depends on the LVM configuration). However this appears to cause problems: Some types of PV seem to require lvmetad and don't work without it (https://bugzilla.redhat.com/show_bug.cgi?id=1581810). If we don't start lvmetad earlier, the device nodes are not created. Therefore move the

I have a report for 1.20.4 about this error. There is no /etc/lvm/lvm.conf in the guest, which is handled as fatal error. Creating an emtpy file with that name is a workaround for the time being. $ virt-resize --expand /dev/sda2 in.img out.img Examining in.img ... Fatal error: exception Guestfs.Error("lvm_set_filter: open: /tmp/lvmiUFSBa/lvm/lvm.conf: No such file or directory") Maybe

Simplify how we handle lvm.conf.

Hi, this series improves the way LVM is used in the appliance: in particular, now lvmetad can eventually run at all, and with the correct configuration. Also improve the listing strategies. Thanks, Pino Toscano (5): daemon: lvm-filter: set also global_filter daemon: lvm-filter: start lvmetad better daemon: lvm: improve filter for LVs with activationskip flag set daemon: lvm: list

GUESTFSD_EXT_CMD was used by OpenSUSE to track which external commands are run by the daemon and package those commands into the appliance. It is no longer used by recent SUSE builds, so remove it. Thanks: Pino Toscano, Olaf Hering. --- daemon/9p.c | 3 +- daemon/available.c | 7 +-- daemon/base64.c | 6 +-- daemon/blkid.c | 10 ++---

guestfsd calls many different tools. Keeping track of all of them is error prone. This patch introduces a new helper macro to put the command string into its own ELF section: GUESTFSD_EXT_CMD(C_variable, command_name); This syntax makes it still possible to grep for used command names. The actual usage of the collected list could be like this: objcopy -j .guestfsd_ext_cmds -O binary

guestfsd calls many different tools. Keeping track of all of them is error prone. This patch introduces a new helper macro to put the command string into its own ELF section: GUESTFS_EXT_CMD(C_variable, command_name); This syntax makes it still possible to grep for used command names. The actual usage of the collected list could be like this: objcopy -j .guestfs_ext_cmds -O binary

GUESTFSD_EXT_CMD is used by OpenSUSE to track which external commands are run by the daemon and package those commands into the appliance. However because this uses linker trickery it won't work from OCaml code. Replace it with a [nearly] standard C mechanism. Files still have to declare the external commands they will use, eg: DECLARE_EXTERNAL_COMMANDS ("btrfs",

Signed-off-by: Olaf Hering <olaf@aepfle.de> --- Not even compile tested, against 1.24 branch. daemon/btrfs.c | 2 +- daemon/command.c | 3 ++- daemon/debug.c | 3 ++- daemon/ldm.c | 4 ++-- 4 files changed, 7 insertions(+), 5 deletions(-) diff --git a/daemon/btrfs.c b/daemon/btrfs.c index 0b877f8..a0c1542 100644 --- a/daemon/btrfs.c +++ b/daemon/btrfs.c @@ -597,7 +597,7 @@

Hi, this series improves the way LVM is used in the appliance: in particular, now lvmetad can eventually run at all, and with the correct configuration. Also improve the listing strategies. Changes in v2: - dropped patch #5, will be sent separately - move lvmetad statup in own function (patch #2) Thanks, Pino Toscano (4): daemon: lvm-filter: set also global_filter daemon: lvm-filter:

This patch reworks how we start up LVM and lvmetad. It fixes the problem we had converting a guest which had a peculiar LVM configuration: https://bugzilla.redhat.com/show_bug.cgi?id=1581810#c14 However please note I have NOT yet tested it fully. Rich.

On Thursday, 24 May 2018 16:01:22 CEST Richard W.M. Jones wrote: > When the daemon starts up it creates a fresh (empty) LVM configuration > and starts up lvmetad (which depends on the LVM configuration). > > However this appears to cause problems: Some types of PV seem to > require lvmetad and don't work without it > (https://bugzilla.redhat.com/show_bug.cgi?id=1581810). If

Don't carry around Augeas lenses. It is fragile, since if the lens is added to upstream Augeas but the version number has not changed, then Augeas won't parse the target file at all. This specifically causes password adjustments to fail in RHEL 7.1. In future, if we need an Augeas lens, it must be added to Augeas, either upstream or as a downstream patch carried around by distros. ---

Hi, >> > # virt-resize -d --expand /dev/sda1 --LV-expand /dev/mapper/prop-home >> > prop-1.img prop-expand.img >> > command line: virt-resize -d --expand /dev/sda1 --LV-expand >> > /dev/mapper/prop-home prop-1.img prop-expand.img >> > Examining prop-1.img ... >> > libguestfs: trace: add_drive "prop-1.img" "readonly:true"

Hi, I have an fc18 system and trying to resize an LVM partition with an ext4 filesystem and receiving the following message from virt-resize: # virt-resize -d --expand /dev/sda1 --LV-expand /dev/mapper/prop-home prop-1.img prop-expand.img command line: virt-resize -d --expand /dev/sda1 --LV-expand /dev/mapper/prop-home prop-1.img prop-expand.img Examining prop-1.img ... libguestfs: trace:

Hi, I have an fc18 system and trying to resize an LVM partition with an ext4 filesystem and receiving the following message from virt-resize: # virt-resize -d --expand /dev/sda1 --LV-expand /dev/mapper/prop-home prop-1.img prop-expand.img command line: virt-resize -d --expand /dev/sda1 --LV-expand /dev/mapper/prop-home prop-1.img prop-expand.img Examining prop-1.img ... libguestfs: trace:

Hi, >> >> > # virt-resize -d --expand /dev/sda1 --LV-expand /dev/mapper/prop-home >> >> > prop-1.img prop-expand.img >> >> > command line: virt-resize -d --expand /dev/sda1 --LV-expand >> >> > /dev/mapper/prop-home prop-1.img prop-expand.img >> >> > Examining prop-1.img ... >> >> > libguestfs: trace:

On 07/21/2013 07:01 PM, Alex wrote: > Hi, > > I have an fc18 system and trying to resize an LVM partition with an > ext4 filesystem and receiving the following message from virt-resize: virt-resize is part of libguestfs, which is layered on top of libvirt. As such, I'm redirecting this mail to the libguestfs mailing list. > > # virt-resize -d --expand /dev/sda1

Hi, newer lvm2 releases don't have have uncommented "filter" lines, so the current way to edit lvm.conf doesn't work anymore. Instead, switch to augeas (with a "custom" len) for a cleaner and working way to set the lvm filter. Pino Toscano (3): daemon: add add_sprintf daemon: move AUGEAS_ERROR to the common header daemon: lvm-filter: use augeas for setting the