updates

backup/backup_btrfs_using_snapshot/README.md

@@ -1,5 +1,4 @@
-backup btrfs filesystem using snapshot
-======================================
+# backup btrfs filesystem using snapshot
 
 **WARNING! Running this file, you accept that you know what you're doing. All actions with this script are at your own
 risk.**
@@ -16,4 +15,4 @@ Variables inside a script:
 - **SOURCE_FILESYSTEM_PATH** (e.g. `"/mnt/data/ssd/folder"`): Source btrfs filesystem to create snapshot from.
 - **BACKUP_FILESYSTEM_PATH** (e.g `"/mnt/data/backup"`): Destination filesystem to send created snapshot. In general
 this is a backup path.
-- **SNAPSHOTS_PATH** (e.g. `"/mnt/data/ssd/.snapshots"`): Temporary filesystem to create snapshot.
+- **SNAPSHOTS_PATH** (e.g. `"/mnt/data/ssd/.snapshots"`): Temporary filesystem to create snapshot.

backup/bareos_pool_operations/README.md

@@ -29,8 +29,6 @@ volumes statistics, running with `--test yes` option.
 - permissions to run `bconsole` command and access to **$poolpath** (don't mind if you run this script from Bareos Admin
   Job you're, otherwise you should edit `/etc/sudoers` or run from root).
 - git package (`apt` or `yum install git` depending on your linux distro).
-- **shflags** library: https://code.google.com/archive/p/shflags/ This script automatically clones this to the current
-  directory.
 
 **Usage:**
 

backup/calculate_and_check_md5/README.md

@@ -12,4 +12,4 @@ risk.**
 [**check_md5.sh**](check_md5.sh) scripts.
 3. (Optional) Modify your [**check_error_notifications.sh**](check_error_notifications.sh) to send an error message to your
 messenger.
-4. Run `calculate_md5.sh` to calculate md5 checksums in `$SOURCE_PATH`, then run `check_md5.sh` to check.
+4. Run `calculate_md5.sh` to calculate md5 checksums in `$SOURCE_PATH`, then run `check_md5.sh` to check.

backup/kvm_vm_backup/README.md

@@ -35,7 +35,7 @@ It's possible to use this script to back up your KVM images with [Bareos](https:
 'after scripts'. The example bellows shows you how to back up virtual machine named 'my_machine' from 'my_server.domain'
 in active mode then clean up on finish:
 
-**/etc/bareos/bareos-dir.d/job/my_machine.conf**
+*/etc/bareos/bareos-dir.d/job/my_machine.conf:*
 
 ```text
 Job {
@@ -55,7 +55,7 @@ Job {
 }  
 ```
 
-**/etc/bareos/bareos-dir.d/jobdefs/my_jobdef.conf**
+*/etc/bareos/bareos-dir.d/jobdefs/my_jobdef.conf:*
 
 ```text
 JobDefs {
@@ -72,7 +72,7 @@ JobDefs {
 }
 ```
 
-**/etc/bareos/bareos-dir.d/fileset/kvm_vm_fileset.conf**
+*/etc/bareos/bareos-dir.d/fileset/kvm_vm_fileset.conf:*
 
 ```text
 FileSet {
@@ -90,8 +90,8 @@ FileSet {
 
 ## Requirements
 
-- Backing up in `--active` mode required channel device (rg.qemu.guest_agent.0) and qemu-guest-agent to be installed on 
-  the guest system. `apt install qemu-guest-agent` or `yum install qemu-guest-agent`. To check qemu-quest-agent 
+- Backing up in `--active` mode required channel device (rg.qemu.guest_agent.0) and qemu-guest-agent to be installed on
+  the guest system. `apt install qemu-guest-agent` or `yum install qemu-guest-agent`. To check qemu-quest-agent
   connection, run the next command from the virtualization host:
 
 ```bash

benchmark/filesystems_benchmarks/README.md

@@ -53,7 +53,7 @@ ramdisk.
 - **BLOCK_DEVICES** (e.g. `"/dev/sdc /dev/sde /dev/sdg /dev/sdi"`): Space separated block devices list to perform tests
 with.
 - **ZFS_POOL_TOPOLOGY** (e.g. `"mirror sdc sde mirror sdg sdi"`): ZFS pool topology to create and perform tests with.
-- **BLOCK_DEVICES_START_LETTER** (e.g. `"a"`): First letter of block devices sequence to benchmark (`a` will be an 
+- **BLOCK_DEVICES_START_LETTER** (e.g. `"a"`): First letter of block devices sequence to benchmark (`a` will be an
 `sda`).
 - **BLOCK_DEVICES_END_LETTER** (e.g. `"j"`): Last letter of block devices sequence to benchmark.
 - **NUMBER_OF_ITERATIONS** (e.g. `3`): Number of write/read iterations.
@@ -71,9 +71,9 @@ compression algorythm for ZFS pool filesystem compression option.
 - [**btrfs_vs_zfs_raid1_vs_raid10_options_performance.sh**](btrfs_vs_zfs_raid1_vs_raid10_options_performance.sh) -
 Comparison of two or four disks btrfs raid10 with different data layout vs one or two mirrored ZFS pools performance.
 - [**README.md**](README.md) - this file.
-- [**single_btrfs_disk_performance.sh**](single_btrfs_disk_performance.sh) - test performance of btrfs filesystem placed on
-single disk (e.g. if you wish to test SSD performance of the disk).
-- [**single_btrfs_disks_with_parallel_streams_performance.sh**](single_btrfs_disks_with_parallel_streams_performance.sh) -
-test several single disks in parallel (e.g. if you wish to test your hardware disk controller speed).
+- [**single_btrfs_disk_performance.sh**](single_btrfs_disk_performance.sh) - test performance of btrfs filesystem placed
+on single disk (e.g. if you wish to test SSD performance of the disk).
+- [**single_btrfs_disks_parallel_streams_performance.sh**](single_btrfs_disks_parallel_streams_performance.sh)- test
+several single disks in parallel (e.g. if you wish to test your hardware disk controller speed).
 - [**zfs_mirrors_performance.sh**](zfs_mirrors_performance.sh) - test performance of ZFS mirror pools (e.g. if you wish to
 test RADI1, RAID10, etc...)