193     /var/log
189     /var/log/sysstat
1       /var/log/*****
1       /var/log/*****
1       /var/log/*****
1       /var/log/*****
1       /var/log/*****
1       /var/log/*****

/usr/bin/archnews
/usr/bin/evhz
/usr/bin/pager
/usr/bin/pinentry-ncurses
/usr/bin/shortping
/usr/bin/showcolors
/usr/bin/xlock

895643648 B 854.2 MB 2125.2 s (35:25 min) 421438 B/s 411.56 KB/s
898371584 B 856.8 MB 2132.5 s (35:32 min) 421280 B/s 411.41 KB/s
901783552 B 860.0 MB 2139.8 s (35:39 min) 421431 B/s 411.55 KB/s
904785920 B 862.9 MB 2147.0 s (35:46 min) 421420 B/s 411.54 KB/s
908300288 B 866.2 MB 2154.0 s (35:54 min) 421678 B/s 411.79 KB/s
911953920 B 869.7 MB 2161.2 s (36:01 min) 421969 B/s 412.08 KB/s
914890752 B 872.5 MB 2168.4 s (36:08 min) 421929 B/s 412.04 KB/s
919408640 B 876.8 MB 2175.4 s (36:15 min) 422647 B/s 412.74 KB/s
923365376 B 880.6 MB 2182.6 s (36:22 min) 423061 B/s 413.15 KB/s

  Size of logical volume ubuntu-vg/ubuntu-lv changed from <14.25 GiB (3647 extents) to <28.50 GiB (7295 extents).
  Logical volume ubuntu-vg/ubuntu-lv successfully resized.
resize2fs 1.45.5 (07-Jan-2020)
Filesystem at /dev/ubuntu-vg/ubuntu-lv is mounted on /; on-line resizing required
old_desc_blocks = 2, new_desc_blocks = 4
The filesystem on /dev/ubuntu-vg/ubuntu-lv is now 7470080 (4k) blocks long.

In order to create a new encrypted filing system managed by cryptmount,
       you can use the supplied 'cryptmount-setup' program, which can be  used
       by the superuser to interactively configure a basic setup.

       Alternatively,  suppose  that  we  wish to setup a new encrypted filing
       system, that will have a target-name of "opaque".  If we  have  a  free
       disk partition available, say /dev/hdb63, then we can use this directly
       to store the encrypted filing system.  Alternatively,  if  we  want  to
       store  the  encrypted filing system within an ordinary file, we need to
       create space using a recipe such as:

$dd if=/dev/zero of=/home/opaque.fs bs=1M count=512

       and then replace all occurences of '/dev/hdb63' in the  following  with
       '/home/opaque.fs'.   (/dev/urandom  can  be used in place of /dev/zero,
       debatably for extra security, but is rather slower.)

       First,  we  need  to  add  an  entry  in  /etc/cryptmount/cmtab,  which
       describes  the  encryption  that will be used to protect the filesystem
       itself and the access key, as follows:

           opaque {
               dev=/dev/hdb63 dir=/home/crypt
               fstype=ext2 mountoptions=defaults cipher=twofish
               keyfile=/etc/cryptmount/opaque.key
               keyformat=builtin
           }

       Here, we will be using the "twofish" algorithm to  encrypt  the  filing
       system  itself, with the built-in key-manager being used to protect the
       decryption key (to be stored in /etc/cryptmount/opaque.key).

       In  order  to  generate  a  secret  decryption  key   (in   /etc/crypt‐
       mount/opaque.key)  that  will  be  used  to  encrypt  the filing system
itself, we can execute, as root:

$cryptmount --generate-key 32 opaque

       This will generate a 32-byte (256-bit) key, which is known to  be  sup‐
       ported  by the Twofish cipher algorithm, and store it in encrypted form
       after asking the system administrator for a password.

       If we now execute, as root:

$cryptmount --prepare opaque

       we will then be asked for the password that we  used  when  setting  up
       /etc/cryptmount/opaque.key,  which  will  enable  cryptmount to setup a
       device-mapper target (/dev/mapper/opaque).  (If you  receive  an  error
       message  of the form device-mapper ioctl cmd 9 failed: Invalid argument
       , this may mean that you have chosen a key-size that isn't supported by
       your chosen cipher algorithm.  You can get some information about suit‐
       able key-sizes by checking the output  from  "more  /proc/crypto",  and
       looking at the "min keysize" and "max keysize" fields.)

       We  can  now  use  standard tools to create the actual filing system on
       /dev/mapper/opaque:

$mke2fs /dev/mapper/opaque

       (It may be advisable, after the filesystem is first mounted,  to  check
       that  the  permissions of the top-level directory created by mke2fs are
       appropriate for your needs.)

       After executing

$cryptmount --release opaque
$mkdir /home/crypt

       the encrypted filing system is ready for use.  Ordinary users can mount
       it by typing

$cryptmount -m opaque

       or

           cryptmount opaque

       and unmount it using

$cryptmount -u opaque