New answers tagged

1

In my case lvextend --poolmetadata didn't allow for any changes, as it would ask me to perform a Manual Repair™. Therefore, I will describe what worked in my situation. In this scenario all the system partitions are in thinly provisioned Logical Volumes and the entire LVM is encrypted inside a LUKS physical partition. Those of you who don't use encryption ...


0

The best, easy and fast you can do is to copy recovered files to external media and start installations (first Windows, then Linux) from scratch. And this time when install linux use free diskspace, not entire disk


3

Instead of adding disks on the level of operation system you can do this directly in hadoop. You can add them to the dfs.datanode.data.dir property. The format is <property> <name>dfs.datanode.data.dir</name> <value>file:///disk/c0t2,/disk/c0t3,/dev/sde,/dev/sdf</value> </property> I am not 100% sure hadoop can ...


4

To make the space available, you need to use the xfs_growfs command as the filesystem on your logical volume is xfs. xfs_growfs / If it were ext2, ext3, or ext4, then you'd use resize2fs with the name. EDIT: It appears to have been changed in its latest release for Fedora and RHEL 8 and CentOS 8. Using the lv/block device works in RHEL 7 and CentOS 7 but ...


0

The command vgscan has an command line option --cache that must be used to put the the results of the scan into the cache, allowing a subsequent vgchange -ay <vg> call to genrete the mapping In short this work: $ sudo losetup --partscan -f hdd.img $ sudo vgscan --scan $ sudo vgchange -ay <vg> whith vg being the one of the volume group (which ...


0

Use lvscan. vgscan is to scan Volume Group ...


0

Overview Having looked at the source for blocks, what it does is: Shrink the LV's filesystem is shrunk by one LVM PE Shrink the LV itself by one LVM PE (this guarantees one free PE to be used for the bcache header) Edit the VG config, insert a new first segment of size 1 being the PE that was freed in the previous step Create a bcache backing device with --...


0

Here's an example of reducing the size of the workspace logical volume by 10G, and then increasing the size of the db logical volume. lvresize -r -L -10G /dev/mapper/volgroup-workspace lvresize -r -L +10G /dev/mapper/volgroup-db


Top 50 recent answers are included