similar to: Managing /etc/fstab with puppet

Hi! I using Augeas to handle dump and passno for certain mount points in /etc/fstab. Each mount point is defined as it''s own augeas block: augeas { ''homeLV'': context => ''/files/etc/fstab'', changes => [

Puppet right now requires every element of a path to have an individual file definition. This makes it had to take an arbitrary path as a parameter. You are forced to require your client to make the entire path structure for you or instead you use an exec resource and call mkdir -p. Using an exec resource does not generate an File resources so autorequire does not work. I didn''t

2015-05-27 15:21 GMT+03:00 Richard W.M. Jones <rjones@redhat.com>: > On Wed, May 27, 2015 at 09:38:38AM +0300, NoxDaFox wrote: > > * RuntimeError: file receive cancelled by daemon - On r = > > libguestfsmod.checksums_out (self._o, csumtype, directory, sumsfile) > > * RuntimeError: hivex_close: do_hivex_close: you must call 'hivex-open' > > first to

Hi all, Sorry for bothering you in this dev mailing list, I'm using libguestfs to customize some vm using as bases the ubuntu cloud images. But I noticed that it takes a lot and then fails when trying to install a packet. Same behaviour on Ubuntu 18.04 and Centos 7.5 Ubuntu: virt-customize 1.36.13 libvirtd (libvirt) 4.0.0 Centos: virt-customize 1.36.10rhel=7,release=6.el7_5.2,libvirt

This bug at http://projects.puppetlabs.com/issues/5211 is showing as ''Closed'', but I am still hitting it with Puppet 2.6.7-1 on RHEL6 (ruby 1.8.7). For /etc/security/limits.conf, got some error using almost the same code as here: http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Augeas?version=7 The only change is: onlyif => "match $path_exact size != 0"

The code to parse btrfs subvol entries in /etc/fstab failed if the entry had more than one comma-separated option, for example: /dev/sda4 /home btrfs rw,user,subvol=foo 0 0 This commit fixes that code to use Augeas correctly. Fixes commit 7ba0e10501f23358c38939930d613bf2393d744d. Reported by: Zhongfu Li https://bugs.launchpad.net/ubuntu/+source/libguestfs/+bug/1615337 ---

Fixes RHBZ#1113153. --- src/inspect-fs-unix.c | 240 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 240 insertions(+) diff --git a/src/inspect-fs-unix.c b/src/inspect-fs-unix.c index 2abbf24..6dfc299 100644 --- a/src/inspect-fs-unix.c +++ b/src/inspect-fs-unix.c @@ -96,6 +96,9 @@ static char *resolve_fstab_device (guestfs_h *g, const char *spec,

Greetings, I am suffering of several weird errors which show randomly and make me suspect some concurrency issue. Libguestfs version is 1.28.1, linux kernel 3.16, libvirt 1.2.9 and qemu 2.1. What I'm trying to do is comparing the disk state at two different point of a guest execution. Disk snapshots are taken through libvirt in different moments (I am aware of caching issue), from such

No change, just reposting without the "for discussion" tag. I think we should allow this as it seems like a nice coding style for a limited subset of imperative-style code. Rich.

When rewriting the heavily imperative original inspection code, I longed for a ‘return’ statement so I could keep the new code as close as possible to the original. OCaml of course does not have such a statement, but it's relatively simply to implement it in the language. The first patch does so, and the second patch rewrites a sample of the inspection code to use it. Rich.

Some of the oldest and most core APIs, reimplemented. This also moves the strange ‘mount_vfs_nochroot’ function into btrfs.c. --- daemon/Makefile.am | 2 + daemon/btrfs.c | 43 ++++++++++++++++++++ daemon/daemon.h | 6 --- daemon/mount.c | 99 ----------------------------------------------- daemon/mount.ml | 62 +++++++++++++++++++++++++++++

I posted this problem on IRC yesterday. Here are some logs. Recap on the problem: When I do inspect_os() (from the python api) or invoke virt-inspector, I get this error: libguestfs: error: internal_parse_mountable: internal_parse_mountable_stub: /dev/vg_nestedctos1/lv_root: No such file or directory I don't have this problem when I invoke it using the OS supplied binaries (version 1.14.8).

That seems to be the indication given by this webpage http://www.zip.com.au/~akpm/linux/ext3/ext3-usage.html However, default install of Redhat 7.2 setsup fs_passno(6th field of /etc/fstab) as 2 which asks you if you want to run fsck after an unclean shutdown The question is, is fsck required after an unclean shutdown or should one just rely on journal replay. What does fsck do when it sees an

Is btrfs subvol support failing just for me? Looks like nothing adds the required '@/' string. virt-ls uses the first variant of the command: ><rescue> mount -vo subvol=var/spool,ro /dev/sda2 /sysroot/ [ 113.852047] BTRFS info (device sda2): disk space caching is enabled [ 113.852869] BTRFS: has skinny extents mount: mount(2) failed: No such file or directory ><rescue>

On Fri, Oct 10, Richard W.M. Jones wrote: > My guess is that the last one (opt/value) will be different for you. Thanks for the pointers. I will poke around. At least augtool on the host seems to behave correctly: olaf@bax:~ $ cd /dev/shm/$$ bash: cd: /dev/shm/3570: Datei oder Verzeichnis nicht gefunden olaf@bax:~ $ mkdir $_ olaf@bax:~ $ cd $_ olaf@bax:/dev/shm/3570 $ mkdir etc

On Fri, Oct 10, 2014 at 01:47:01PM +0200, Olaf Hering wrote: > > Is btrfs subvol support failing just for me? Looks like nothing adds the > required '@/' string. virt-ls uses the first variant of the command: > > ><rescue> mount -vo subvol=var/spool,ro /dev/sda2 /sysroot/ > [ 113.852047] BTRFS info (device sda2): disk space caching is enabled > [

Hi all, I encountered the following error when I tried to run virt-sysprep on a qcow2 image. virt-sysprep: error: no operating systems were found in the guest image The version I used for libguest is as follows: [libguestfs-1.36.5] The same issue happened on other versions such as libguestfs-1.32.7. # ./run ./sysprep/virt-sysprep -v -x -a

~ ~ ~ ~ ~ rss:/etc # 358C written rss:/etc # man mount Reformatting mount(8), please wait... MOUNT(8) Linux Programmer's Manual MOUNT(8) NAME mount - mount a file system SYNOPSIS mount [-lhV] mount -a [-fFnrsvw] [-t vfstype] mount [-fnrsvw] [-o options [,...]] device | dir mount [-fnrsvw] [-t vfstype] [-o options] device dir

Adds support for systemd .mount files, uses Augeas to extract mount points. Fixes RHBZ#1113153. Maros Zatko (1): inspection: add support for systemd .mount files src/inspect-fs-unix.c | 240 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 240 insertions(+) -- 1.9.3

Hello. Is there a simple way, at a shell script level, of finding out whether an ext3 fs has a sane journal, other than mounting it or running a full fsck ? I may quite well be missing a few things here, but what I think I'd like is some option extra to e2fsck that says "if this is a journalled filesystem, and it was shut down uncleanly, just replay the journal and check for immediately