search for: passno

...I didn''t like the results I got so far... here is what I''ve tried: define conf ( $id = "01", $spec = " ", $file = " ", $vfstype = " ", $opt = "", $dump = "0", $passno = "0" ) { $key = "$spec/$file/$vfstype/$opt/$dump/$passno" $context = "/files/etc/fstab" $path_list = "spec = \"$spec\"" $path_exact = "*[spec=\"$spec\"]" augeas { "fstab/...

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'',...

...guestfs: recv_from_daemon: received GUESTFS_LAUNCH_FLAG libguestfs: [05639ms] appliance is up libguestfs: trace: launch = 0 libguestfs: trace: inspect_os libguestfs: trace: umount_all guestfsd: main_loop: new request, len 0x28 umount-all: /proc/mounts: fsname=rootfs dir=/ type=rootfs opts=rw freq=0 passno=0 umount-all: /proc/mounts: fsname=proc dir=/proc type=proc opts=rw,relatime freq=0 passno=0 umount-all: /proc/mounts: fsname=/dev/root dir=/ type=ext2 opts=rw,noatime freq=0 passno=0 umount-all: /proc/mounts: fsname=/proc dir=/proc type=proc opts=rw,relatime freq=0 passno=0 umount-all: /proc/mount...

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

.../dev/vda2 guestfsd: main_loop: proc 198 (vfs_type) took 0.00 seconds libguestfs: trace: vfs_type = "LVM2_member" libguestfs: trace: inspect_os libguestfs: trace: umount_all guestfsd: main_loop: new request, len 0x28 umount-all: /proc/mounts: fsname=rootfs dir=/ type=rootfs opts=rw freq=0 passno=0 umount-all: /proc/mounts: fsname=proc dir=/proc type=proc opts=rw,relatime freq=0 passno=0 umount-all: /proc/mounts: fsname=/dev/root dir=/ type=ext2 opts=rw,noatime freq=0 passno=0 umount-all: /proc/mounts: fsname=/proc dir=/proc type=proc opts=rw,relatime freq=0 passno=0 umount-all: /proc/mount...

..."vfat" libguestfs: trace: inspect_os libguestfs: trace: umount_all guestfsd: main_loop: proc 198 (vfs_type) took 0.02 seconds guestfsd: main_loop: new request, len 0x28 umount-all: /proc/mounts: fsname=/dev/root dir=/ type=ext2 opts=rw,noatime,block_validity,barrier,user_xattr,acl freq=0 passno=0 umount-all: /proc/mounts: fsname=/proc dir=/proc type=proc opts=rw,relatime freq=0 passno=0 umount-all: /proc/mounts: fsname=/sys dir=/sys type=sysfs opts=rw,relatime freq=0 passno=0 umount-all: /proc/mounts: fsname=tmpfs dir=/run type=tmpfs opts=rw,nosuid,relatime,size=96136k,mode=755 freq=0 pas...

...-s TYPE /dev/sda1 libguestfs: trace: vfs_type = "xfs" libguestfs: trace: inspect_os libguestfs: trace: umount_all guestfsd: main_loop: proc 198 (vfs_type) took 0.02 seconds guestfsd: main_loop: new request, len 0x28 umount-all: /proc/mounts: fsname=rootfs dir=/ type=rootfs opts=rw freq=0 passno=0 umount-all: /proc/mounts: fsname=proc dir=/proc type=proc opts=rw,relatime freq=0 passno=0 umount-all: /proc/mounts: fsname=/dev/root dir=/ type=ext2 opts=rw,noatime freq=0 passno=0 umount-all: /proc/mounts: fsname=/proc dir=/proc type=proc opts=rw,relatime freq=0 passno=0 umount-all: /proc/mount...

...d filesystem, and it was shut down uncleanly, just replay the journal and check for immediately obvious problems, but don't bother scanning the whole filesystem unless there's a '-f' in sight". AFAICT, the usual way of handling ext3 filesystems seems to be to mark them with fs_passno=0, so they never get fscked from the init scripts - but the journal gets replayed, and a few things get checked at mount time. If mount fails - because something horrible really did happen - then the /etc/rc.sysinit doesn't seem to have any way of coping, or dropping to an interactive shell....

...em without journal. Opts: (null) guestfsd: main_loop: proc 1 (mount) took 0.34 seconds guestfsd: main_loop: new request, len 0x34 guestfsd: main_loop: proc 3 (touch) took 0.01 seconds guestfsd: main_loop: new request, len 0x28 umount-all: /proc/mounts: fsname=rootfs dir=/ type=rootfs opts=rw freq=0 passno=0 umount-all: /proc/mounts: fsname=proc dir=/proc type=proc opts=rw,relatime freq=0 passno=0 umount-all: /proc/mounts: fsname=/dev/root dir=/ type=ext2 opts=rw,noatime freq=0 passno=0 umount-all: /proc/mounts: fsname=/proc dir=/proc type=proc opts=rw,relatime freq=0 passno=0 umount-all: /proc/mount...

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 unclean ext3 filesystem Regards, Yusuf -- Yusuf Goolamabbas yus...

...ore, the current CVS won't encode mono files. It bombs out with a segfault in _vp_quantize_couple(). Program received signal SIGSEGV, Segmentation fault. 0x40039328 in _vp_quantize_couple (p=0x8079d78, vi=0x8052a48, pcm=0x80ae9f0, sofar=0xbfffef54, quantized=0xbfffef64, nonzero=0xbfffef84, passno=0) at psy.c:1038 1038 qA[j]=ang-sofarA[j]; Should this code even be reached on a single-channel file? Is bit-rate selection not working at the moment either? Thanks for Vorbis by the way John -- http://johnwarburton.net/ --- >8 ---- List archives: http://www.xiph.org/archiv...

...took 0.01 secs guestfsd: <= touch (0x3) request length 52 bytes guestfsd: =&gt; touch (0x3) took 0.00 secs guestfsd: <= internal_autosync (0x11a) request length 40 bytes umount-all: /proc/mounts: fsname=/dev/root dir=/ type=ext2 opts=rw,noatime,block_validity,barrier,user_xattr,acl freq=0 passno=0 umount-all: /proc/mounts: fsname=/proc dir=/proc type=proc opts=rw,relatime freq=0 passno=0 umount-all: /proc/mounts: fsname=/sys dir=/sys type=sysfs opts=rw,relatime freq=0 passno=0 umount-all: /proc/mounts: fsname=tmpfs dir=/run type=tmpfs opts=rw,nosuid,relatime,size=95924k,mode=755 freq=0 pas...

...em without journal. Opts: (null) guestfsd: main_loop: proc 1 (mount) took 0.07 seconds guestfsd: main_loop: new request, len 0x34 guestfsd: main_loop: proc 3 (touch) took 0.00 seconds guestfsd: main_loop: new request, len 0x28 umount-all: /proc/mounts: fsname=rootfs dir=/ type=rootfs opts=rw freq=0 passno=0 umount-all: /proc/mounts: fsname=proc dir=/proc type=proc opts=rw,relatime freq=0 passno=0 umount-all: /proc/mounts: fsname=/dev/root dir=/ type=ext2 opts=rw,noatime freq=0 passno=0 umount-all: /proc/mounts: fsname=/proc dir=/proc type=proc opts=rw,relatime freq=0 passno=0 umount-all: /proc/mount...

...isting device nodes in /dev ... [ ok ] * Skipping mount of /dev/pts as it's already mounted * Remounting root filesystem read-only ... mount: / is busy [ !! ] * Skipping root filesystem check (fstab's passno == 0) ... [ ok ] * Checking all filesystems ... [ ok ] * Mounting local filesystems ... mount: mount point /dev/shm does not exist * Some local filesystem failed to mount [ !! ] * Mounting USB device filesy...

v1 was here: https://www.redhat.com/archives/libguestfs/2016-March/thread.html#00157 Not running the 'hwclock' command reduces boot times considerably. However I'm not sure if it is safe. See the question I posted on qemu-devel: http://thread.gmane.org/gmane.comp.emulators.qemu/402194 At the moment, about 50% of the time is consumed by SeaBIOS. Of this, about ⅓rd is SGABIOS

Hi Rich, This is v3 series to add support for resizing MBR logical partitions. changes to v3: 1. merge patch 1 and patch 3 in v3 2. let mbr_part_type return 'primary' for GPT partitions 3. add test for resizing logical partitions 4. fix extending the extended partition (yet). see patch 7. changes to v2: 1. remove p_part_num 2. remove filter_parts 3. name the function

...g guestfs handle 0x24282d0 (state 2) libguestfs: trace: internal_autosync guestfsd: main_loop: proc 276 (pread_device) took 0.00 seconds guestfsd: main_loop: new request, len 0x28 umount-all: /proc/mounts: fsname=/dev/root dir=/ type=ext2 opts=rw,noatime,block_validity,barrier,user_xattr,acl freq=0 passno=0 umount-all: /proc/mounts: fsname=/proc dir=/proc type=proc opts=rw,relatime freq=0 passno=0 umount-all: /proc/mounts: fsname=/sys dir=/sys type=sysfs opts=rw,relatime freq=0 passno=0 umount-all: /proc/mounts: fsname=tmpfs dir=/run type=tmpfs opts=rw,nosuid,relatime,size=97040k,mode=755 freq=0 pas...

When converting from a single transaction to a linked list, I forgot to free the storage for each member of the list. Reported-by: Richard W.M. Jones <rjones at redhat.com> Fixes: 7f5bb9bf13f041ea7702bda557d9dd668bc3423a Signed-off-by: Eric Blake <eblake at redhat.com> --- I'm still not sure why 'make check' passes while 'make check-valgrind' fails for

...op: proc 334 (fstrim) took 0.28 seconds libguestfs: trace: fstrim = 0 libguestfs: trace: shutdown libguestfs: trace: internal_autosync guestfsd: main_loop: new request, len 0x28 umount-all: /proc/mounts: fsname=/dev/root dir=/ type=ext2 opts=rw,noatime,block_validity,barrier,user_xattr,acl freq=0 passno=0 umount-all: /proc/mounts: fsname=/proc dir=/proc type=proc opts=rw,relatime freq=0 passno=0 umount-all: /proc/mounts: fsname=/sys dir=/sys type=sysfs opts=rw,relatime freq=0 passno=0 umount-all: /proc/mounts: fsname=tmpfs dir=/run type=tmpfs opts=rw,nosuid,relatime,size=98324k,mode=755 freq=0...

Hi, &nbsp; &nbsp; I have use&nbsp; kvm ? virsh ? virt&nbsp; &nbsp;for almost half year ?all things goes well ? &nbsp; &nbsp; but recently? I use virt-copy-in&nbsp; found some problem ? I&nbsp; have&nbsp; &nbsp;do&nbsp; nothing&nbsp; with my server&nbsp; ?but the problem appear .&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;