| Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
software:files [2024/04/14 17:54]
cyril [Tools] |
software:files [2024/04/21 23:47]
cyril [Tools] |
| * ''<absolute-size>'': ''200G'', ''3T'', ... | * ''<absolute-size>'': ''200G'', ''3T'', ... |
| * ''<relative-size>'': ''+100%FREE'' | * ''<relative-size>'': ''+100%FREE'' |
| | * If using an SSD drive, [[#ssd_trim|TRIM commands]] from the layers below (eg filesystem) will be transparently forwarded without any special configuration. However if you wish that LVM issues its own TRIM commands when some space is not allocated by LVM, you can set the ''issue_discards'' option to 1 in ''/etc/lvm/lvm.conf''. |
| | |
| |
| === LUKS === | === LUKS === |
| * 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) |
| |
| === Filesystem === | === Filesystem === |
| |
| * With ''btrfs'': | * With ''btrfs'': |
| * ''compsize <subvolume-path>'' in order to get statistics about quantity of compressed files, and compression ratio | * ''compsize <subvolume-path>'' in order to get statistics about quantity of compressed files, and compression ratio. |
| | * ''compsize <file-path>'' in order to get compression details about a specific file. |
| | |
| | === SSD TRIM === |
| | |
| | * TRIM (or discard) operation means informing the SSD drive about the unused memory, so that it can perform efficiently wear leveling. |
| | * Checking TRIM support: run ''lsblk --discard'', and check for non-zero values in columns DISC-GRAN (DISCard GRANularity) and DISC-MAX (DISCard MAX bytes). |
| | * **Warning**: make sure that your device supports TRIM before using it, or data loss can occur. |
| | * Each layer must forward the TRIM commands to the layer above, until it reaches the drive. If you haven't done it persistently for LUKS as suggested in the [[#luks|create]] section, you can open it with this option: ''cryptsetup <...> --allow-discards'' |
| | * Then two options are available to enable it: |
| | * Continuous TRIM, i.e. configuring the filesystem to notify instantly each block that is freed. |
| | * It is not advised because doing it to often can reduce the lifetime of poor quality SSDs. |
| | * Periodic TRIM, i.e. explicitly notifying the free blocks periodically. |
| | * Using the ''fstrim'' utils from the util-linux package. |
| | * Manually: run ''fstrim --verbose <mount-point>'' for a single volume, or ''fstrim --verbose -A'' for all mounted filesystems listed in ''/etc/fstab'' and the root filesystem inferred from the kernel command line. |
| | * Weekly: enable the timer ''systemctl start fstrim.timer'' |
| | |
| | |
| | Source : https://wiki.archlinux.org/title/Solid_state_drive |
| |
| === Resizing === | === Resizing === |
| === Borg Backup === | === Borg Backup === |
| |
| * Create a Borg repository in the current folder: <code>borg init -e <encryption> [--append-only]</code> | * Create a Borg repository in the current folder: <code>borg init -e <encryption> [--append-only] .</code> |
| * ''<encryption>'' can be: | * ''<encryption>'' can be: |
| * ''none'' to disable it, for instance on an already encrypted volume | * ''none'' to disable it, for instance on an already encrypted volume |
| |
| === Restic === | === Restic === |
| | |
| | * Create a Restic repository in the current folder: <code>restic init --repo .</code> |
| | * Note that encryption **and** password are mandatory, [[https://github.com/restic/restic/issues/4326|because]]. However you can store the password in a file in the repository, or use the a password file with ''--password-file''. |
| | * Create snapshots: <code>restic --repo <repo> --verbose --compression auto backup <path></code> |
| | * 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'' |
| | |
| |
| === BTRFS snapshots === | === BTRFS snapshots === |
| |
| |
| | |
| | ===== Container files ===== |
| | |
| | Sources: |
| | * [[https://serverfault.com/questions/696554/creating-a-grow-on-demand-encrypted-volume-with-luks|Excellent demonstration]] for creating a growing container file with LUKS and EXT4 using sparse files. |
| |
| ===== Digital Will ===== | ===== Digital Will ===== |
