|
Size: 724
Comment:
|
Size: 2050
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == KVM Host Disk Layout == | = KVM Host Disk Layout = |
| Line 3: | Line 3: |
| This disk layout has several layers. It uses btrfs on top of lvm on top of luks encryption on top of raid on top of the disks partitions | This disk layout has several layers. It uses btrfs, on top of LVM, on top of luks encryption, on top of raid, on top of the disks partitions. |
| Line 5: | Line 5: |
| === KVM Host === | == Hardware == Two 16G SSD disks are used for the KVM Host. Two 2T SATA disks are used for the KVM Guests filesystem images. |
| Line 7: | Line 8: |
| ==== Physical Disks ==== | Mark your disks! Spend time finding your disks S/N. Put a physical sticker on the disk. In the future this will help you identify a failing disk. === KVM Host Disks === ==== Physical Disks and Partitions ==== |
| Line 35: | Line 41: |
| md1_crypt lvm (vg1) | md1_crypt lvm (vg_system) |
| Line 38: | Line 44: |
| ==== LVM volumes ==== | ==== LVM Volumes ==== Initially the swap partition was 512M, but it ran full and was increased to 1G. That ran full as well, so a swap partition on the second volume was added too. It seems the KVM host happily swaps and will use many gigabytes of swap if the swap partition is there. The consequence is that the guests are slower to respond. So I recommend only swapping if you are really running out of memory. |
| Line 41: | Line 48: |
| vg1 root 2G (/dev/vg1/root) vg1 swap 512M (/dev/vg1/swap) |
vg_system root 2G (/dev/vg_system/root) vg_system swap 512M (/dev/vg_system/swap) |
| Line 45: | Line 52: |
| ==== Filesystems and mountpoints ==== | ==== Filesystems and Mountpoints ==== |
| Line 47: | Line 54: |
| /dev/vg1/root / (btrfs) /dev/md0 /boot (btrfs) /dev/vg1/swap (swap) |
/dev/vg_system/root / (btrfs) /dev/md0 /boot (btrfs) /dev/vg_system/swap (swap) |
| Line 51: | Line 58: |
=== KVM Host Disks for Guest Filesystem Images === ==== Physical Disks and Partitions ==== {{{ sdc 2T sdc1 1856G sdd 2T sdd1 1856G }}} ==== Raid ==== {{{ md2 raid1 (sdc1, sdd1) }}} ==== Luks ==== {{{ md2 luks (md2_crypt) }}} ==== LVM ==== {{{ md2_crypt lvm (vg_storage) }}} ==== LVM Volumes ==== {{{ vg_storage media 4G (/dev/vg_storage/media) vg_storage swap 4G (/dev/vg_storage/swap) }}} ==== Filesystems and Mountpoints ==== {{{ /dev/vg_storage/swap (swap) /dev/vg_storage/media /mnt/media (btrfs) }}} |
KVM Host Disk Layout
This disk layout has several layers. It uses btrfs, on top of LVM, on top of luks encryption, on top of raid, on top of the disks partitions.
Hardware
Two 16G SSD disks are used for the KVM Host. Two 2T SATA disks are used for the KVM Guests filesystem images.
Mark your disks! Spend time finding your disks S/N. Put a physical sticker on the disk. In the future this will help you identify a failing disk.
KVM Host Disks
Physical Disks and Partitions
sda 16G sda1 256M sda2 15360M sdb 16G sdb1 256M sdb2 15360M
Raid
md0 raid1 (sda1, sdb1) md1 raid1 (sda2, sdb2)
Luks
md1 luks (md1_crypt)
LVM
md1_crypt lvm (vg_system)
LVM Volumes
Initially the swap partition was 512M, but it ran full and was increased to 1G. That ran full as well, so a swap partition on the second volume was added too. It seems the KVM host happily swaps and will use many gigabytes of swap if the swap partition is there. The consequence is that the guests are slower to respond. So I recommend only swapping if you are really running out of memory.
vg_system root 2G (/dev/vg_system/root) vg_system swap 512M (/dev/vg_system/swap)
Filesystems and Mountpoints
/dev/vg_system/root / (btrfs) /dev/md0 /boot (btrfs) /dev/vg_system/swap (swap)
KVM Host Disks for Guest Filesystem Images
Physical Disks and Partitions
sdc 2T sdc1 1856G sdd 2T sdd1 1856G
Raid
md2 raid1 (sdc1, sdd1)
Luks
md2 luks (md2_crypt)
LVM
md2_crypt lvm (vg_storage)
LVM Volumes
vg_storage media 4G (/dev/vg_storage/media) vg_storage swap 4G (/dev/vg_storage/swap)
Filesystems and Mountpoints
/dev/vg_storage/swap (swap) /dev/vg_storage/media /mnt/media (btrfs)