Tag Info

Hot answers tagged

6

Most init systems probably won't expect this situation so they won't be prepared to first assemble LVM, then MD, then LVM again. If you put LVM below MD you have to be very careful. MD is supposed to be used with physical disks, but with LVs as RAID members you could easily end up with two members sharing the same disks. That is if using MD as a standalone ...


5

I'm not sure if this is the one-and-done solution, but it worked for me. I had to create my "LVM" with striping options. lvcreate -L 217T -i2 -I64 -n lv_share VolGroup See 4.4.2. Creating Striped Volumes. Then I had to mount it with the -o inode64 option, as Mark mentioned. See 8.2. Mounting an XFS File System.


2

Don't install a new system unless you want to redo your system configuration from scratch. Note that you may want to do that — copy your home directory over, and progressively restore the system configuration, taking care to 1. install etckeeper as soon as you've rebooted after the system installer and 2. not make changes outside of /etc and your home ...


2

It is not something I would do online but I think it is possible. I guess you are using ext4. umount /home $ umount /home shrink the /home filesystem $ fsck -f /dev/mapper/VolGroup-lv_home $ resize2fs /dev/mapper/VolGroup-lv_home 80G shrink the /home logical volume $ lvreduce -L -40G /dev/mapper/VolGroup-lv_home resize the /home partition to the size of ...


2

Assuming your volume group is already full, and you cannot extend it further, you will need to: Shrink the filesystem in lv_home using the specific tools for your filesystem, e.g. resize2fs if you use ext3/4. Resize lv_home accordingly with lvreduce. Increase lv_root with lvresize. Increase the filesystem in lv_root so that it uses all the additional ...


2

First off, you want to unmount the partitions in question. Boot an usb stick or similar. Backing up important data is always recommended before fiddling with filesystems. Reduce the filesystem first in /dev/mapper/vg_dckapstaging-lv_home. Otherwise, resizing the lv will drop the data. The way to do it depends naturally from filesystem. resize2fs works for ...


2

On arch linux, there is an AUR package dropbear_initrd_encrypt that does what you want out of the box. Works pretty well for wired interfaces. I had to hack it up slightly for wireless.


2

If you format a piece of the SSD drive to be used as a bcache cache, then it will not be available anymore to store any other filesystem, obviously. But nothing prevents you from using the remaining part of the SSD drive as you see fit. This applies to for instance WD Black2 There are also other SSHD disks, like Seagete Momentus XT, where the cache is ...


2

It depends on hybrid drive type: new Seagate SSHD drives manufactured since late 2013 have far better caching than earlier models. What is also important, bcache caching strategy is totally different than Seagate Adaptive Memory strategy, and while bcache is very fast in benchmarks, AM learns data topology and can outperform bcache in real situations, eg.: ...


1

You are using the Linux Logical volume manager (LVM). This is a layer between your physical disks and your filesystems that introduces the concepts of 'physical volumes' (PV), 'volume groups' (VG), and 'logical volumes' (LV). In your setup, /dev/sdb1 and /dev/sda2, the partitions of type "Linux LVM" are both physical volumes. On top of these PV you will ...


1

To play with DRBD, you'd be better off adding a new virtual disk to your VM and using that (alongside your existing disk) rather than trying to carve up the virtual disk you already have. As to your questions regarding LVM, the free space you're seeing displayed by the various tools is measured with different frames of reference. PVs are physical devices ...


1

This is a risky operation you should try to clean / (have a look at /var/log /var/spool and delete old and big file) theorical way to proceed include fsck -F /dev/mapper/vg_dckapstaging-lv_home lvresize --size -15G /dev/mapper/vg_dckapstaging-lv_home resize2fs /home lvresize --size +15G /dev/mapper/vg_dckapstaging-lv_root resize2fs / Disclaimer 3.1. be ...


1

You should have --private option for vzctl create: vzctl create CTID --private /vz/primary vzctl create CTID --private /vz/secondary If each container has a dedicated partition, also consider specifying --layout simfs. ploop might be unneeded overhead.


1

I fixed it! Here are the commands I used this time: # parted /dev/sda (parted) mklabel msdos (parted) mkpart primary ext2 2MiB 2GiB (parted) mkpart primary ext4 2GiB 100% (parted) set 1 boot on (parted) q # mkfs.ext2 /dev/sda1 # cryptsetup --key-size 512 --hash sha512 --iter-time 5000 --use-random luksFormat /dev/sda2 # cryptsetup open --type luks ...


1

You cannot resize or change at all any partition on a storage device that is currently mounted. That means that your system needs to be shutdown if you intend to modify the root partition (since you cannot unmount it) You will need to boot in an external OS (e.g. using a live-CD) to perform these tasks. I would recommend you to backup any sensible data ...



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