Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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 the data space in thin pool is exhausted and pool waits for resize to get new free space to provision chunk - any try to read a thin volume seems to block as well.
Simple way to reproduce - create some thin LVs -
lvcreate -L10 -V20 -T vg/pool
lvcreate -V20 -T vg/pool
lvol1 & lvol2 should be available as thin volumes.
now fill thin volume via 'dd'
dd if=/dev/zero of=/dev/vg/lvol1 bs=1M
(this should block waiting on resize when thin pool dmeventd monitoring is disabled (see lvm.conf monitoring option).
In this case any try to read from either lvol2 or lvol1 blocks.
Here is stack trace from blkid /dev/vg/lvol2:
blkid D ffff88013594c980 0 1703 21936 0x00000000
ffff8800166e5cd8 0000000000000046 ffff88011d0324c0 ffff8800166e5fd8
00000000001d3e00 00000000001d3e00 ffff88011d0324c0 ffff8801375d4788
ffff8800166e5d60 0000000000000082 ffffffff811517c0 ffff8800166e5d50
Call Trace:
[<ffffffff811517c0>] ? sleep_on_page+0x20/0x20
[<ffffffff815c65fd>] io_schedule+0x9d/0x140
[<ffffffff811517ce>] sleep_on_page_killable+0xe/0x40
[<ffffffff815c6b6b>] __wait_on_bit_lock+0x7b/0xc0
[<ffffffff8115192a>] __lock_page_killable+0x6a/0x70
[<ffffffff8109d710>] ? autoremove_wake_function+0x40/0x40
[<ffffffff81154c98>] generic_file_aio_read+0x4a8/0x750
[<ffffffff811fd1db>] blkdev_aio_read+0x4b/0x70
[<ffffffff811bc60a>] do_sync_read+0x5a/0x90
[<ffffffff811bccce>] vfs_read+0x9e/0x170
[<ffffffff811bd7cc>] SyS_read+0x4c/0xa0
[<ffffffff815d4c96>] system_call_fastpath+0x1a/0x1f
dd which is waiting for pool resize:
dd D ffffffff81a114c0 0 1698 3195 0x00000000
ffff8800683d7c58 0000000000000046 ffff880135964980 ffff8800683d7fd8
00000000001d3e00 00000000001d3e00 ffff880135964980 ffff8801373d4788
ffff88013bf908e8 0000000000000002 ffffffff811517a0 ffff8800683d7cd0
Call Trace:
[<ffffffff811517a0>] ? wait_on_page_read+0x60/0x60
[<ffffffff815c65fd>] io_schedule+0x9d/0x140
[<ffffffff811517ae>] sleep_on_page+0xe/0x20
[<ffffffff815c6a32>] __wait_on_bit+0x62/0x90
[<ffffffff8115154f>] wait_on_page_bit+0x7f/0x90
[<ffffffff8109d710>] ? autoremove_wake_function+0x40/0x40
[<ffffffff81151661>] filemap_fdatawait_range+0x101/0x1b0
[<ffffffff81151737>] filemap_fdatawait+0x27/0x30
[<ffffffff8115374e>] filemap_write_and_wait+0x3e/0x60
[<ffffffff811fd9af>] __sync_blockdev+0x1f/0x40
[<ffffffff811fdd01>] __blkdev_put+0x61/0x1b0
[<ffffffff811fe7d0>] blkdev_put+0x50/0x160
[<ffffffff811fe998>] blkdev_close+0x28/0x30
[<ffffffff811bea10>] __fput+0xf0/0x240
[<ffffffff811bebae>] ____fput+0xe/0x10
[<ffffffff8107399c>] task_work_run+0xac/0xe0
[<ffffffff81002de1>] do_notify_resume+0x61/0xa0
[<ffffffff815d4fa2>] int_signal+0x12/0x17
Version-Release number of selected component (if applicable):
dm thin pool target version 1.10
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Volumes continue to be readable and block only when provisioning should happen.
Additional info:
Comment 2RHEL Program Management
2014-03-22 06:01:12 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 6RHEL Program Management
2020-12-15 07:29:34 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.