On Thu, Mar 21, 2019 at 11:27:42AM +0100, Lukas Czerner wrote:
>
> lv_role=public does not exclude snapshots and so it will fail later in
> e2scrub when you try to create a snapshot of a thicksnapshot which is
> not supported.
Ah, good point. Thanks for pointing that out.
> Also I am not sure what's the rush, but it seems you've ignored my other
> suggestions.
I did consider them all, but there were reasons why I didn't use them.
One of them wasn't practical because I needed LVM2_VG_NAME; when you
made that suggestion, I hadn't published the patch needed to fix
Debian Bug #924301. Of course, if we use your suggestion of using "-S
vg_free > ${snap_size}" it will obviate that need; so thanks for that
suggestion.
The reason why I didn't take one of your other suggestions is that we
need to check whether or not the file system is mounted, and so we
needed the mountpoint in lsblk, and once you ask for the mountpoint,
we can no longer use awk to select a field, since an unmounted file
system shows up as a an empty column.
% sudo lsblk -o MOUNTPOINT,FSTYPE,NAME -l
LVM2_member nvme0n1p3_crypt
ext4 lambda-uroot
[SWAP] swap lambda-swap_1
/ ext4 lambda-root
ext4 lambda-old--files
ext4 lambda-library
ext4 lambda-test--4k
ext4 lambda-scratch
ext4 lambda-test--1k
lambda-scratch2
lambda-scratch3
ext4 lambda-results
lambda-thinpool_tmeta
lambda-thinpool_tdata
I also really didn't like using grep to select the file system type
ext[234], since if it would falsely select a LV name that contained
"ext4", e.g.:
/home/dave xfs rhel-ext4--sucks
:-)
We could have used awk to select the field, but that still doesn't
deal with the mountpoint column being empty when it is unmounted. I
did briefly consider using lsblk -J, but I didn't want to add a
dependency on the jq[1] package (and I didn't even know if RHEL/Fedora
packages jq).
[1] https://packages.debian.org/stretch/jq
Cheers,
- Ted
