similar to: guestfish zerofree on LVM ?

Thanks all for the advice. It seems there is an issue with Dracut booting from these hosts when LVM is used. dracut: Scanning devices sda2 for LVM logical volumes VolGroup/lv_swap VolGroup/lv_root dracut: inactive '/dev/VolGroup/lv_swap' [1.94 GiB] inherit dracut: inactive '/dev/VolGroup/lv_root' [230.69 GiB] inherit dracut: PARTIAL MODE. Incomplete logical volumes will be

Fasiha Ashraf --- On Sat, 22/8/09, Fasiha Ashraf <feehapk@yahoo.co.in> wrote: From: Fasiha Ashraf <feehapk@yahoo.co.in> Subject: Re: [Xen-users] my bootlog To: "Boris Derzhavets" <bderzhavets@yahoo.com> Date: Saturday, 22 August, 2009, 11:12 AM Please check what wrong here grub.conf        title Fedora (2.6.30-rc6-tip)         root (hd0,6)         kernel

zerofree is a package that can take an ext2 (only?) filesystem, work out what parts of the filesystem are not used, and either zero them or sparsify them. This was useful in about 2009 when I added it to Fedora. However nowadays it's more convenient to use the equivalent kernel functionality (via the ‘fstrim’ command or equivalent ioctls). The kernel functionality also works correctly for

Hi all, Can I ask if zerofree or resize2fs could also be applicable to ext4? Guestfish help of these two commands indicates that they are applicable to ext2/3. But ext4 is not covered in the help. However, I have tested these two commands in my Fedora 12 laptop, and it seems that both commands work well with ext4. So I don't quite understand why the help of these two commands only mention

Hi, These are my make menuconfig screen shots. I haven''t found any xen option in v2.6.30-rc. Why is that so? this happens with most of the version. What should I do? should I just let it as it is an run the make command to build the kernel? Regards, Fasiha Ashraf See the Web''s breaking stories, chosen by people like you. Check out Yahoo! Buzz. Love Cricket?

Hi All, I just tried to create a DomU using the following method... (I normally use the Xen install kernel when I create CentOS domus, but when I tried that with the PXE image, that had the same effect as below). This is the first time I have created a Fedora domu in ages... years, even. virt-install \ --paravirt \ --name demo \ --ram 500 \

Hello Richard, On Sun, 18 Feb 2018, Richard W.M. Jones wrote: > If you wish to take it over, I can orphan it instead. I'm happy to take zerofree. Regards, Robert

On Sun, 18 Feb 2018, Richard W.M. Jones wrote: > There's also a more serious data safety issue: Although this probably > works OK for ext2 since that format is frozen in time, it probably > corrupts ext4 filesystems containing features that it doesn't know > about. > > It is for these reasons that I don't think you should use this package > and I intend to retire

As mentioned yesterday, Xen 4.6 packages are now available for testing. These also include an update to libvirt 1.3.0, in line with what's available for CentOS 7. Please test, particularly the upgrade if you can, and report any problems here. To upgrade: yum update --enablerepo=centos-virt-xen-testing To install from scratch: * Install centos-release-xen from centos-extras yum install

I've install a CentOS Stream 9 system from a kickstart file that specified (among other things) several logical volumes: logvol / --fstype="ext4" --size=10240 --name=lv_root --vgname=VolGroup logvol /var --fstype="ext4" --size=4096 --name=lv_var --vgname=VolGroup logvol swap --fstype="swap" --size=2048 --name=lv_swap --vgname=VolGroup When that system rebooted,

On 04/13/2016 12:02 AM, ???? wrote: > In /etc/rc.d/rc.sysinit, > there's "mount -a -n -t nonfs,nfs4,smbfs,ncpfs,cifs,gfs,gfs2i,glusterfs -O > no_netdev". > > > I have other same type servers. And on other servers with same /etc/fstsb, > file system is correct. > There's no difference between normal server's rc.sysinit and this problem > server's

hi, The problem: for kvm/qemu disks are /dev/vdx devices when using the virtio driver. For vmware, drives are /dev/sdx devices. For hp servers, /dev/ccisss/whatever (sorry, no proliant with an array controller handy to check it). in order to just have one kickstart script to maintain I am trying to use the %pre section but getting a bit stuck. This is what I have: %pre if [ -b /dev/sda ] then

> -----Original Message----- > From: Johnny Hughes > On 12/01/2014 04:48 AM, Bob Ball wrote: > > > > [<ffffffff81575480>] panic+0xc4/0x1e1 > > [<ffffffff81054836>] find_new_reaper+0x176/0x180 > > [<ffffffff81055345>] forget_original_parent+0x45/0x2c0 > > [<ffffffff81107214>] ? task_function_call+0x44/0x50 > >

Has anyone managed to create an encrypted disk partition with CentOS 8 kickstart? 1 reqpart --add-boot 2 part /boot --fstype ext3 --size=1024 --ondrive=sda 3 part pv.1 --size=1 --grow --ondrive=sda --encrypted --pashphrase="bla" 4 volgroup vol0 pv.100000 5 logvol / --vgname=vg_00 --name=lv_root --size=102400 --fstype=ext4 ... No matter what I specify in line 3, the installer bombs out.

On 04/13/2016 08:44 PM, ???? wrote: > # mount > /dev/mapper/VolGroup-lv_root on / type ext4 (rw,usrquota,grpquota) > proc on /proc type proc (rw) > sysfs on /sys type sysfs (rw) > devpts on /dev/pts type devpts (rw,gid=5,mode=620) > tmpfs on /dev/shm type tmpfs (rw) > /dev/vda1 on /boot type ext4 (rw) > /dev/vdb on /mnt/extradiskA type ext4 (rw,usrquota,grpquota) >

I've started updating systems to CentOS 7.6, and so far I have one failure. This system has two peculiarities which might have triggered the problem. The first is that one of the software RAID arrays on this system is degraded. While troubleshooting the problem, I saw similar error messages mentioned in bug reports indicating that sGNU/Linux ystems would not boot with degraded software

From: "Richard W.M. Jones" <rjones at redhat.com> Callers are supposed to use the availability API to check for functions that may not be available in particular builds of libguestfs. If they don't do this, currently they tend to get obscure error messages, eg: libguestfs: error: zerofree: /dev/vda1: zerofree: No such file or directory This commit changes the error

On Sun, Feb 18, 2018 at 09:19:09PM +0100, Robert Scheck wrote: > On Sun, 18 Feb 2018, Richard W.M. Jones wrote: > > There's also a more serious data safety issue: Although this probably > > works OK for ext2 since that format is frozen in time, it probably > > corrupts ext4 filesystems containing features that it doesn't know > > about. > > > > It is

Hey, Can anyone tell me why option 1 works and option 2 fails ? I know I need swap and such, however in trouble shooting this issue I trimmed down my config. It fails on trying to format my logical volume, because the mount point does not exist (/dev/volgroup/logvol) It seems that with option 2, the partitions are created and LVM is setup correctly. However the volgroup / logvolume was not

Re: https://bugzilla.redhat.com/show_bug.cgi?id=521674 Perl modules are unversioned, but should carry version numbers Currently perl RPM deps are unversioned. Apparently if we add a version number into the perl module(s) then we can fix that, eg: our $VERSION = "1.0.68"; This would allow Perl users to specify the version either through an RPM dependency or in code like this: