feat: SUCCESS-220 check vol is available

[valigula]

Please go the the Preview tab and select the appropriate sub-template:

test 1 👍

KO timeout

root@db-fswipshaopfljcvruhws:~# ./mount-volume.sh /dev/nvme2n1 /data/150008
Starting mount procedure for device /dev/nvme2n1 → /data/150008
Waiting for block device /dev/nvme2n1 to become available...
Error: /dev/nvme2n1 did not become ready after 60 seconds
root@db-fswipshaopfljcvruhws:~#

test 2 👍

KO mounting in an existing mount point

root@db-fswipshaopfljcvruhws:~# ./mount-volume.sh /dev/nvme2n1 /data/
Starting mount procedure for device /dev/nvme2n1 → /data/
Waiting for block device /dev/nvme2n1 to become available...
/dev/nvme2n1 is ready
/dev/nvme2n1 already has a filesystem — skipping format.
/data/ is already mounted
Setting ownership and permissions on /data/
UUID bfa2b8a8-fecc-4a86-9d9a-8ff47c3bc07e already in /etc/fstab — skipping
Mounted /dev/nvme2n1 at /data/ with owner=postgres:postgres and mode=750

test 3 👍

KO mounting in a filesystem with data

root@db-fswipshaopfljcvruhws:~# ./mount-volume.sh /dev/nvme2n1 /data/pgdata
Starting mount procedure for device /dev/nvme2n1 → /data/pgdata
Waiting for block device /dev/nvme2n1 to become available...
/dev/nvme2n1 is ready
Error: Mount point /data/pgdata is not empty. Aborting to protect existing data.

test 4 👍

OK

Root@db-fswipshaopfljcvruhws:~# ./mount-volume.sh /dev/nvme2n1 /data/150008
Starting mount procedure for device /dev/nvme2n1 → /data/150008
Waiting for block device /dev/nvme2n1 to become available...
/dev/nvme2n1 is ready
/dev/nvme2n1 already has a filesystem — skipping format.
Running e2fsck check on /dev/nvme2n1
/dev/nvme2n1: 11/655360 files (0.0% non-contiguous), 66753/2621440 blocks
Mounting /dev/nvme2n1 to /data/150008
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
Setting ownership and permissions on /data/150008
UUID bfa2b8a8-fecc-4a86-9d9a-8ff47c3bc07e already in /etc/fstab — skipping
Mounted /dev/nvme2n1 at /data/150008 with owner=postgres:postgres and mode=750
root@db-fswipshaopfljcvruhws:~# ls -rth /data/150008/
lost+found

test 5 👍

OK with a delay

root@db-fswipshaopfljcvruhws:~# ./mount-volume.sh /dev/nvme2n1 /data/150008
Starting mount procedure for device /dev/nvme2n1 → /data/150008
Waiting for block device /dev/nvme2n1 to become available...
/dev/nvme2n1 is ready
/dev/nvme2n1 already has a filesystem — skipping format.
Running e2fsck check on /dev/nvme2n1
/dev/nvme2n1: 11/655360 files (0.0% non-contiguous), 66753/2621440 blocks
Mounting /dev/nvme2n1 to /data/150008
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
Setting ownership and permissions on /data/150008
UUID bfa2b8a8-fecc-4a86-9d9a-8ff47c3bc07e already in /etc/fstab — skipping
Mounted /dev/nvme2n1 at /data/150008 with owner=postgres:postgres and mode=750
root@db-fswipshaopfljcvruhws:~#
root@db-fswipshaopfljcvruhws:~#
root@db-fswipshaopfljcvruhws:~# lsblk
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
nvme1n1     259:0    0   14G  0 disk /data
nvme0n1     259:1    0   10G  0 disk
├─nvme0n1p1 259:2    0   99M  0 part /boot/efi
└─nvme0n1p2 259:3    0  9.9G  0 part /
nvme2n1     259:4    0   10G  0 disk /data/150008
root@db-fswipshaopfljcvruhws:~#