| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
software:files [2024/04/22 00:04]
cyril [Tools] |
software:files [2024/07/05 08:09] (current)
cyril [Tools] |
| * If you want to use LVM and don't need to boot on the disk, not much to do in this section, just remove all the existing partitions with ''gparted'', then go directly to the next one to create the LVM volumes directly on the raw device. | * If you want to use LVM and don't need to boot on the disk, not much to do in this section, just remove all the existing partitions with ''gparted'', then go directly to the next one to create the LVM volumes directly on the raw device. |
| * Otherwise, create a ''gpt'' partition table with ''gparted'' | * Otherwise, create a ''gpt'' partition table with ''gparted'' |
| * If you need to boot on the disk, create the required ''boot'' and ''grub'' partitions with ''gparted'' | * If you need to boot on the disk, with ''gparted'': |
| | * create the EFI partition: set size around 200-400MB, format it to fat32, set ''boot'' and ''esp'' flags |
| | * create the boot partition: set size around 300-500MB, format it to ext2 |
| | * mount everything: root partition to /mnt, boot partition to /mnt/boot, efi partition to /mnt/boot/efi, ''mount --bind'' /mnt/{dev,proc,sys}, ''mount -t efivarfs efivarfs /mnt/sys/firmware/efi/efivars'' |
| | * chroot to the new root: ''chroot /mnt'' |
| | * install grub: ''grub-install --root-directory=/ --boot-directory=/boot --efi-directory=/boot/efi --bootloader-id=<os-name>'' |
| | * you can check the EFI install with ''efibootmgr -v'' (and remove an entry with ''efibootmgr -b <0005> -B'' |
| | * grub-mkconfig -o /boot/grub/grub.cfg |
| * If you want to use LVM, create a single large partition with the remaining space with ''gparted'' to create the LVM volumes on this partition. | * If you want to use LVM, create a single large partition with the remaining space with ''gparted'' to create the LVM volumes on this partition. |
| * Otherwise create the required system and data partitions with ''gparted'' | * Otherwise create the required system and data partitions with ''gparted'' |
| === LVM === | === LVM === |
| |
| * create physical volume: ''pvcreate <device-name>''. | * create physical volume: ''pvcreate <device-name>'' (device can be the whole device if not a boot device, or a partition). |
| * Check with ''pvdisplay'' or ''pvs''. | * Check with ''pvdisplay'' or ''pvs''. |
| * if it complains with the error ''Cannot use <device-name>: device is partitioned'', you need to remove existing traces of partition table or filesystem with the command ''wipefs --all <device-name>'' | * if it complains with the error ''Cannot use <device-name>: device is partitioned'', you need to remove existing traces of partition table or filesystem with the command ''wipefs --all <device-name>'' |
| |
| * Encrypt the volume/partition/device: ''cryptsetup luksFormat -c aes-xts-plain64 -h sha256 -s 512 <volume-name>'' | * Encrypt the volume/partition/device: ''cryptsetup luksFormat -c aes-xts-plain64 -h sha256 -s 512 <volume-name>'' |
| * ''<volume-name>>'' is the device or partition name if not using LVM, or ''/dev/mapper/<vgroup-name>-<lvolume-name>'' if using it. | * ''<volume-name>'' is the device or partition name if not using LVM, or ''/dev/mapper/<vgroup-name>-<lvolume-name>'' if using it. |
| * Choose a strong passphrase as it can be brute-forced (at least 80 bits of entropy) | * Choose a strong passphrase as it can be brute-forced (at least 80 bits of entropy) |
| * By default it will configure the key derivation take 2 seconds | * By default it will configure the key derivation take 2 seconds |
| * Open (decrypt) the volume: ''cryptsetup luksOpen <volume-name> <evolume-name!>'' | * Open (decrypt) the volume: ''cryptsetup luksOpen <volume-name> <evolume-name!>'' |
| * If using an SSD drive, you probably should enable [[#ssd_trim|TRIM-forwarding]]: ''cryptsetup --allow-discards --persistent refresh <evolume-name>'' (check [[https://wiki.archlinux.org/title/Solid_state_drive#dm-crypt|security implications]] though) | * If using an SSD drive, you probably should enable [[#ssd_trim|TRIM-forwarding]]: ''cryptsetup --allow-discards --persistent refresh <evolume-name>'' (check [[https://wiki.archlinux.org/title/Solid_state_drive#dm-crypt|security implications]] though). Check with ''cryptsetup luksDump <volume-name>''. If you enabled it by mistake (for instance on a non-SSD), you can disable it with ''cryptsetup --persistent refresh <evolume-name>'' (it resets flags). |
| |
| === Filesystem === | === Filesystem === |
| |
| === Resizing === | === Resizing === |
| | |
| | ==== Extending ==== |
| | |
| | * Resize the LVM logical volume: ''lvresize -L <absolute-size> <lvolume-name>'' |
| | * ''<absolute-size>'' can also be an increment, e.g. ''+50G'' |
| | * Open the volume with Luks: ''cryptsetup luksOpen <lvolume-name> <evolume-name>'' |
| | * Resize the filesystem: |
| | * ext4: ''e2fsck -f <evolume-name> ; resize2fs <evolume-name>'' |
| | * btrfs: mount the filesystem then ''btrfs filesystem resize max /mnt/<evolume-name>'' |
| | |
| | |
| | ==== Reducing ==== |
| |
| TODO | TODO |
| * ''borg list <repo>'' | * ''borg list <repo>'' |
| * ''borg info <repo>::<archive>'' | * ''borg info <repo>::<archive>'' |
| | * ''borg diff <repo>::<archive1> <archive2>'' |
| | * ''borg mount <repo>::<archive> <mountpoint>'' |
| | |
| |
| === Restic === | === Restic === |
| * The chunker cannot be configured, contrary to Borg. It is equivalent to [[https://restic.readthedocs.io/en/stable/100_references.html#backups-and-deduplication|19,23]],[[https://restic.net/blog/2015-09-12/restic-foundation1-cdc/|21,512]], similarly to Borg's default [[https://borgbackup.readthedocs.io/en/stable/internals/data-structures.html#buzhash-chunker|19,23,21,4095]], but unlike my chosen values. | * The chunker cannot be configured, contrary to Borg. It is equivalent to [[https://restic.readthedocs.io/en/stable/100_references.html#backups-and-deduplication|19,23]],[[https://restic.net/blog/2015-09-12/restic-foundation1-cdc/|21,512]], similarly to Borg's default [[https://borgbackup.readthedocs.io/en/stable/internals/data-structures.html#buzhash-chunker|19,23,21,4095]], but unlike my chosen values. |
| * ''--compression'': unlike Borg, there is only choicies ''auto'', ''max'' and ''off'' | * ''--compression'': unlike Borg, there is only choicies ''auto'', ''max'' and ''off'' |
| | * ''restic --repo <repo> snapshots'' to list snapshots |
| |
| |
