Tag Info

New answers tagged

0

If you want to have the guest boot load itself with e.g. grub, then then disk has to have a partition table. Otherwise, you have to have the guest kernel and initrd in the host and pass them to qemu to load directly. Also rather than add additional disks you can simply resize the existing disk to add storage to the vm.


2

Description From the lvmetad man page: lvmetad is a metadata caching daemon for LVM. The daemon receives notifications from udev rules (which must be installed for LVM to work correctly when lvmetad is in use). Through these notifications, lvmetad has an up-to-date and consistent image of the volume groups available in the system. By default, ...


0

You make this message disappear by setting your GRUB_CMDLINE_LINUX_DEFAULT variable in /etc/default/grub with crypt_opts=<whatever#1>,lvm=<whatever#2> The script in /usr/share you mention set the variable cryptlvm with . For further reference, my own GRUB_CMDLINE_LINUX_DEFAULT contains: ...


2

Okay, I've figured out how to do what I tried to. This will be a some kind of a tutorial. During this time I didn't yet realized, that manipulations with LVs are actually possible when the filesystems are mounted and booted into some live Linux distro (SystemRescueCD). People here explained me, that there is no necessity in this if you're not manipulating ...


3

You don't need to shrink the pv or rebuild the array. You just need to create a new array out of the new drives and add that as a new pv ( pvcreate + vgextend ), then pvmove all of the existing lvs off the old pv, then remove the old pv ( vgreduce ) and take that drive out of service.


2

It's not lvmove but pvmove. pvmove --alloc=anywhere /dev/md0:89600-102950 /dev/md0:0-12070 That should move any extents within the 89600-102950 range to 0-12070 range. According to the data you posted that should result in your LVs being relocated to the beginning of your PV.


1

By some mystery I had wiped the volume group and the physical volume in it. It was just a matter of recovering them using the metadata I could back-up using testdisk. I copied the original /etc/lvm folder on the Desktop of the live user, then $ pvcreate --uuid "cZ83jX-WXkk-tNG4-ulGT-sAqq-HlKq-Omtqc8" \ --restorefile ...



Top 50 recent answers are included