Merge branch 'master' of github:tiyn/wiki

wiki/docker-images/johnktims_-_folding-at-home.md

@@ -22,7 +22,7 @@ There are some special variables to set.
 
 ### GPU
 
-GPU support is documented in [the docker entry](../docker.md).
+GPU support is documented in [the docker article](../docker.md).
 
 ## rebuild.sh
 

wiki/linux/arch-linux/installation.md

@@ -1,9 +1,7 @@
 # Arch installation with LUKS encryption and LVM
 
-This is the English version of the
-[German installation guide on rvbg.eu](https://wiki.rvbg.eu/#arch/installation.md).
 This guide is based upon a
-[german arch wiki entry](https://wiki.archlinux.de/title/Moderne_Installation_mit_UEFI_und_Verschlüsselung).
+[german arch wiki article](https://wiki.archlinux.de/title/Moderne_Installation_mit_UEFI_und_Verschlüsselung).
 
 At the end of this guide a fully functional Arch Linux will be installed.
 
@@ -208,4 +206,4 @@ this will install a bunch of useful software including a graphical environment.
 You can go on to other guides aswell.
 
 Additionally if you have a NVidia Graphics Cards you should read
-[the NVidia entry](../nvidia.md) too.
+[the NVidia article](../nvidia.md) too.

wiki/linux/disk-management.md

@@ -1,15 +1,23 @@
 # Disk Management
 
+This article focusses on non-LVM and non-MDADM storage.
+For [LVM](lvm.md), [MDADM](./mdadm.md) and [LUKS volumes](./dm-crypt.md) there
+are separate entries.
+
+## Create Partition
+
+In the following it is assumed that the disk is `/dev/sda`
+
+- open up parted with `parted /dev/sdd`
+- if not already done create a partition table with `mklabel GPT`
+- create a primary partition (ext4 format) with `mkpart primary 2048s 100%`
+- `quit` parted
+
 ## Grow non-LVM ext4 partition
 
 ATTENTION: Please note that the partition to enlarge has to be the last one with
 the free space after it.
 
-SSH into the VM.
-
-- run `lsblk` check if the disk size has changed
-- if not `reboot` the machine
-
 In the following it is assumed that the partition to enlarge is `/dev/sda2`
 
 - change the size of the partition with `parted /dev/sda`

wiki/linux/dm-crypt.md

@@ -13,3 +13,19 @@ Where `/dev/sda2` is the device you want to create.
 To open and map a device run `cryptsetup -y -v luksFormat /dev/sda1 crypt0` where
 `/dev/sda1` is your encrypted device and `crypt0` is where it will be mapped to
 with `dev/mapper/crypt0`.
+
+## Resize a LUKS encrypted volume
+
+If you have volume groups on the encrypted volume make sure to close them
+with the following command modified to your needs:
+`vgchange -a n <volume group>`
+
+Open the encrypted volume (assuming its stored at `/dev/sda2` and you map it
+to `crypt-volume`):
+`cryptsetup luksOpen /dev/sda2 crypt-volume`
+
+Now resize the encrypted volume to all available space of the partition.
+If you don't want to extend the encrypted volume to the whole partition
+or the partition is to small for your purposes, make sure to resize the
+partition first accordingly (see [disk management](./disk-management.md)).
+`cryptsetup resize crypt-volume`

wiki/linux/lvm.md

@@ -24,10 +24,24 @@ pvcreate /dev/sdc1
 vgextend <name of your volume group> /dev/sdc1
 ```
 
+## Resize a physical volume
+
+To increase the size of a physical volume you have to have free free space
+in the partition containing the physical volume.
+A guide to change 'normal' partitions can be found in the
+[disk management article](./disk-management.md); if you have a volume that is
+encrypted with LUKS a guide is available in
+[the dm-crypt articel](./dm-crypt.md).
+
+To resize the physical volume to the size of the containing volume run:
+`pvresize /dev/mapper/<name of physical volume>`
+
 ## Increase size of a logical volume
 
-To increase the size of the logical volume you need to have free space in the
+To increase the size of the logical volume you have to have free space in the
 according volume group. You can check that by running: `vgdisplay`.
+If you don't have enough space you have to resize the physical volume as
+described in this article.
 Then run:
 
 ```shell

wiki/linux/mdadm.md

@@ -2,14 +2,44 @@
 
 `mdadm` is a utility to create and manage raid devices.
 
+## Get information about a raid
+
+To get an info for a running raid (assuming it is `/dev/md0`) run
+`mdadm -D /dev/md0`.
+
+### Add disk/partition to raid device
+
+You can add a disk or partition to a raid device by running the following.
+It is assumed you are adding a partition called `/dev/sdd1` but it could also
+be a whole drive and the mdadm drive is called `/dev/md0`.
+
+`mdadm --add /dev/md0 /dev/sdd1`
+
 ## Raid 1
 
 Raid 1 creates a mirror with even amount of drives.
 
-### Create Raid 0 device
+### Create raid 1 device
 
-You can create a Raid 0 device with
+You can create a Raid 1 device with
 `mdadm --create --verbose /dev/md0 --level=1 --raid-devices=2 /dev/sda /dev/sdb`
 where `sda` and `sdb` are the disks you want to include in your raid.
 You can increase the number of raid devices, but they have to be at least 2.
 If it is an uneven amount of disks in the raid, a disk will act as a spare disk.
+
+### Convert raid 1 to raid 5
+
+Assuming the raid device is called `/dev/md0`.
+All other drives are part of the `md0` raid device.
+
+- Remove all drives but 2 by running `mdadm /dev/md0 --fail /dev/sda1` and
+  `mdadm /dev/md0 --remove /dev/sda1` where `sda1` is the drive to remove
+- Make sure your raid 1 array has only 2 active drives by running
+  `mdadm --grow /dev/md0 -n 2`
+- Now convert your raid 1 to a raid 5 device with `mdadm --grow /dev/md0 -l5`
+- Add the disks you removed back to the raid with
+  `mdadm /dev/md0 --add /dev/sda1`
+- Finally grow the active drive number to your needs (in this example 4)
+  `mdadm --grow /dev/md0 -n4`
+- `mdadm` now reshapes the raid. You can monitor it by running
+  `watch cat /proc/mdstat`

wiki/linux/proxmox.md

@@ -14,6 +14,9 @@ After that follow the instructions and fill in the fields to your liking.
 
 ### Enlarging disk of a VM
 
+Make sure there is enough disk space available.
+For further information see [the disk management article](./disk-management.md)
+
 SSH into Proxmox.
 Enlarge a disk by using:
 
@@ -21,13 +24,14 @@ Enlarge a disk by using:
 qm resize <vmid> <vm-disk-to-enlarge> <size>
 ```
 
-For example (100G is 100GibiByte):
+For example if you want to the disk 100 by 100G (100GibiByte):
 
 ```shell
 qm resize 100 ide0 +100G
 ```
 
-After that grow the filesystem as described in [the disk-management article](disk-management.md).
+After that grow the filesystem in the vm as described in
+[the disk management article](./disk-management.md).
 
 ## Remove local-lvm and add its size to local
 

wiki/linux/vim/c-language.md

@@ -1,7 +1,8 @@
 # C in Vim
 
 C is a common programming language.
-In this entry we will focus on making vim support c and use vim as an ide for c.
+In this article we will focus on making vim support c and use vim as an ide for
+c.
 
 ## Autocompletion
 

wiki/linux/vim/golang.md

@@ -1,8 +1,10 @@
 # GoLang in Vim
 
 GoLang is a common programming language.
-In this entry we will focus on making vim support Go and use vim as an ide for it.
+In this article we will focus on making vim support Go and use vim as an ide
-This guide is based on a guide from [octetz.com](https://octetz.com/docs/2019/2019-04-24-vim-as-a-go-ide/).
+for it.
+This guide is based on a guide from
+[octetz.com](https://octetz.com/docs/2019/2019-04-24-vim-as-a-go-ide/).
 
 ## Build, Test, Run, Docs, Debug, Format
 

wiki/linux/vim/python.md

@@ -1,8 +1,8 @@
 # Python in Vim
 
 Python is a common programming language.
-In this entry we will focus on making vim support python and use vim as an ide
+In this article we will focus on making vim support python and use vim as an
-for it.
+ide for it.
 
 ## Autocompletion
 

wiki/linux/vim/vhdl.md

@@ -1,7 +1,7 @@
 # VHDL in Vim
 
 VHDL is a hardware description language.
-In this entry we will focus on making vim support VHDL.
+In this article we will focus on making vim support VHDL.
 
 ## Linting
 

wiki/matrix.md

@@ -12,7 +12,7 @@ This setup guide follows a modified version of the
 [guide by matusnovak](https://gist.github.com/matusnovak/37109e60abe79f4b59fc9fbda10896da).
 Furthermore this guide will assume you already have a
 [traefik v2.4](./traefik.md) instance setup as described in the
-[traefik docker image entry](./docker-images/traefik.md).
+[traefik docker image article](./docker-images/traefik.md).
 
 ### DNS records