Tag Info

Hot answers tagged

2

When you use lvextend or lvresize, you need to use the + or specify more space or extend that was allocated for your lvm volume example: lvextend -l +100%FREE /dev/datalake/volume or withouth + lvextend -l <total number of extends to catch up> /dev/datalake/volume I prefer to use first method, because in this way,i don't need to know the number ...


1

There are a couple of points I would like to stress: first, I would try to use a dedicated storage device if possible. Hardware built for an specific purpose tends to be more fit for it that generic servers. That being said, I understand that if the budget is low, there may not be a chance of getting a small disk array. Therefore, if you need to use a ...


1

There are quite a few options with varying degrees of resilience, disk efficiency and ease of operation. Here are a few: RAID 0 & 1 RAID 0 and 1 are immediately out of the question, RAID 0 offers no redundancy (in fact it increases risk) and RAID 1 is limited - as you mentioned - to the maximum size of 1 disk. RAID 5 Is an option and you only lose 1 ...


1

Boot from fedora live cd or somesuch, run vgchange -a y if the volume groups are not visible already, and the volume groups logical volumes will appear for you to mount


1

In the end I solved this problem by manually editing the /etc/lvm/backup/lvm_group1. Here are the steps in case anyone else hits this problem: I physically removed the dead drive from the server I executed vgreduce lvm_group1 --removemissing --force I removed from the config the dead drive I added another stripe on a "good" drive in place of the ...


1

What you suggest shouldn't be done online, as it's error prone and possibly dangerous. You need to resize partitions to do that, you likely lose data when trying to mess with the partition your system's root filesystem is placed on. This is what that check is for. Use a livecd with gparted to resize your partitions, then setup an encrypted filesystem in the ...


1

I had the exactly same error. I solved this by updating lvm version to lvm2-2.02.111-2.el6_6.1. Once you update the lvm, you should be able to run vgreduce --removemissing --force vgQ3 http://rpmfind.net/linux/RPM/centos/updates/6.6/x86_64/Packages/lvm2-2.02.111-2.el6_6.1.x86_64.html


1

It doesn't seem that partman (Debian Installer tool for partitioning) supports that. I've filed a wishlist in Debian bug tracker, it's currently marked as "wontfix": https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418519



Only top voted, non community-wiki answers of a minimum length are eligible