similar to: Lvm and backup

Hi everyone! I''ve been reading this list for a while and I''m thinking that the best way to do backups is using LVM snapshots as discussed here several times. The problem is that when i use a LVM logical volume as windows disk, windows writes the partition table onto the LV so the LV itself is not a partition - it''s a whole disk. lvm/device-mapper does not create the

On Wed, Dec 02, 2015 at 08:53:39PM +0100, Axel Glienke wrote: > Creating snapshot: > > [root at lvmtest ~]# lvcreate -L5G -s -n root_snap /dev/centos/root > Reducing COW size 5,00 GiB down to maximum usable size 2,94 GiB. > Logical volume "root_snap" created. > [root at lvmtest ~]# lvs > LV VG Attr LSize Pool Origin Data% Meta% Move > Log

Hi list, I'm having one of those 'I'm stupid' -problems with LVM on CentOS 5.2. I've been working with traditional partitions until now, but I've finally been sold on the theoretical benefits of using LVM, but for now I only have a huge pile of broken filesystems to show for my efforts. My scenario; I attach a disk, either over USB or iSCSI. I create a PV on this

Hi. I have some narrow questions and a larger one. If I make an existinig LVM VG a storage pool, can I use some of the LV's for libvirt and some for the host? Or does the VG needed to be completely dedicated to virtualization? Assuming mixed use is possible, is it possible to do an LVM snapshot of an LV in use for a VM? The snapshot would have to be initiated and used on the host, I

sorry: centos7 "fresh" minimal with a actual update cat proc/cmdline: BOOT_IMAGE=/vmlinuz-3.10.0-229.20.1.el7.x86_64 root=/dev/mapper/centos_root ro rd.lvm.lv=centos/root rd.lvm.lv=centos/swap crashkernel=auto rhgb quiet LANG=de_DE.UTF-8 systemd.debug ls /dev/mapper: centos-swap control Zitat von Gordon Messmer <gordon.messmer at gmail.com>: > On 12/02/2015 11:09 AM,

On Fri, May 19, 2023 at 04:08:49PM +0200, Laszlo Ersek wrote: > In the LUKS-on-LVM inspection test, call the "check_filesystems" function > yet another time, now with such "--key" options that exercise the recent > "/dev/mapper/VG-LV" -> "/dev/VG/LV" translation (unescaping) from > libguestfs-common. > > Bugzilla:

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,

Volumes are aggregation of bricks, so I would consider bricks as a unique entity here rather than volumes. Taking the constraints from the blog [1]. * All bricks should be carved out from an independent thinly provisioned logical volume (LV). In other words, no two brick should share a common LV. More details about thin provisioning and thin provisioned snapshot can be found here. * This thinly

I am performing some configuration testing on a kvm host. When installing a guest operating system is it advisable to place each instance in a separate lv or better to accept the default and store them on the root file system? Respecting lvm, does one configure lvs in a virtual server to take space from the main vg or does one allocate lv space from inside that allocated to the virtual instance?

Hi, I'm trying to resize a 15GB LVM root partition on a fedora20 server with a fedora20 guest and I'm having a problem. Is this supported on fedora20? I recall having a similar problem (maybe even exact same problem) all the way back in fedora16 or fedora17, but hoped/thought it would be fixed by now? # virt-df -h test1-011015.img Filesystem Size Used

I've upgraded my x86_64 4.2 box to the latest kernel 2.6.9.34 and tried an lvm snapshot. It worked fine and I was able to mount the snapshot etc. Now I cannot seem to remove the snapshot. If I try a 'lvremove' it asks if I want to remove the 'active' snapshot, if I say yes it just hangs and the box goes to 99% wait io, however the disk lights do not come on during this. The

On 6/23/2015 11:23 AM, Mauricio Tavares wrote: > AIX does use lvm a lot. Main difference is their filesystem > allows live shrinking. Kinda nice to dynamically size a partition > depending on needs, as opposite to the so often suggested approach of > formatting the entire drive as one single partition. Symlinking is > great until whatever the destination is does not mount. I

Hi... I have had a problem when I am going to detach one specific LVM partitions of Xen, so I have been trying xm destroy <domain>, lvchange -an <lvm_partition>, lvremove -f.... So I haven''t had sucess. I restarted the server with init 1 yet and nothing... I have seem two specific process started xenwatch and xenbus, but I am not sure if this processes have some action over

I've been running into a reproducible problem when using default LVM volume group names to present block devices for virtual machines in KVM, and I'm wondering why it is happening. On dom0 I make a default VolGroup00 for the operating system. I make a second VolGroup01 for logical volumes that will be block devices for virtual systems. In VolGroup01, I make two lv's for one system:

When a disk image uses LVM thinp (thin provisioning), the guestfs_lvs API would return the thinp pools. This confused other APIs because thinp pools don't have corresponding /dev/VG/LV device nodes. Filter the LVs that are returned using "lv_role=public". Thanks: Fabian Deutsch --- daemon/lvm.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/daemon/lvm.c

Hi People I just updated a CentOS 5.2 Server that is a Guest inside VMware ESX 3.50 Server using "yum update". As far as I can tell the only three packages were updated Jul 24 16:37:49 Updated: php-common - 5.1.6-20.el5_2.1.i386 Jul 24 16:37:50 Updated: php-cli - 5.1.6-20.el5_2.1.i386 Jul 24 16:37:50 Updated: php - 5.1.6-20.el5_2.1.i386 But when I rebooted the Server one of my

Hello, I need to automate installation of CentOS 7.0 using PXE and kickstart. My server is diskless, I'm installing CentOS on a 25GB LUN on a FC SAN with 4 paths. This LUN is the only one accessible by the server. Anaconda processes successfully the installation. But on reboot, I get stuck on a prompt after BIOS. I think I have an issue with storage configuration / bootloader

On 1/9/22 15:37, Gordon Messmer wrote: > 1: The system also includes a volume group named "BackupGroup" and > that group activates on boot (post-dracut).? Why are those LVs > activated when rd.lvm.lv is specified? As far as I can tell, this is because in the dracut boot process, the device backing VolGroup is activated, but the device backing BackupGroup is not.? As a

Hi This topic is perhaps not for this list, but it I'm running on a CentOS 4.4 and it seems that a lot of people here uses 3Ware and RAID volumes. I did a RAID migration on a 3Ware 9590SE-12, so that an exported disk grew from 700GB to 1400GB. The exported disk is managed by LVM. The problem now is that I don't really know what to do now to let LVM and my locigal volume to make use of

Hello, I would really appreciate some help/guidance with this problem. First of all sorry for the long message. I would file a bug, but do not know if it is my fault, dm-cache, qemu or (probably) a combination of both. And i can imagine some of you have this setup up and running without problems (or maybe you think it works, just like i did, but it does not): PROBLEM LVM cache writeback