RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When a thin pool reaches some usage levels (80%, 85%, 90% and 95%) a warning message should be provided, but it does not happen.


Version-Release number of selected component (if applicable):
lvm2-2.02.169-1.el7.x86_64
kernel-3.10.0-632.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Create a thin pool and thin device
fallocate -l 128M /tmp/loop0.img
losetup /dev/loop0 /tmp/loop0.img
vgcreate --force testvg /dev/loop0
lvcreate -V100m -L100m -T testvg/pool1 -n lv1

2.Make thin pool 80% full
dd if=/dev/zero of=/dev/testvg/lv1 bs=1M count=80
sleep 30

3.Check if warning shows on log
tail /var/log/messages

Actual results:
No warning message is shown

Expected results:
Warning message

Additional info:
If then 81% is used the warning message is shown:
dd if=/dev/zero of=/dev/testvg/lv1 bs=1M count=81; sleep 30; tail /var/log/messages
<snip>
Apr 19 05:17:59 localhost lvm[14037]: WARNING: Thin pool testvg-pool1-tpool data is now 81.00% full.


Further increase such to 85% or 90% does not give more warnings
# lvs testvg/pool1
  LV    VG     Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  pool1 testvg twi-aotz-- 100.00m             85.00  1.95

Yep - we print only warning on the crossing of 80% threshold but not for later once - this will need further thinking as we on the other hand gained option
to correctly work with thin-pool which has decreased its usage and crossed 80% again.

But it should be possible to restore warning also for 85% and more percent again.

Should be addressed by commit: 455a4de090f10f98ac2932a2540a30b7fdc34f61

https://www.redhat.com/archives/lvm-devel/2017-May/msg00031.html


Warning is printed with 80, 85, 90, 95, 100%

In release bugfix - moving to ON_QA.

Tested with lvm2-2.02.171-2.el7 and it works well.

I can see the messages below as the pool is being used.

WARNING: Thin pool testvg-pool3-tpool data is now 81.00% full.

WARNING: Thin pool testvg-pool3-tpool data is now 91.00% full.

WARNING: Thin pool testvg-pool3-tpool data is now 96.00% full.

In release bug. Closing as fixed.