| Summary: | Raid driver stays forever in raid5_quiesce | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Zdenek Kabelac <zkabelac> |
| Component: | kernel | Assignee: | Heinz Mauelshagen <heinzm> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 22 | CC: | gansalmon, heinzm, itamar, jonathan, kernel-maint, lvm-team, madhu.chinakonda, marcelo.barbosa |
| Target Milestone: | --- | Flags: | jforbes:
needinfo?
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-23 17:21:16 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Does this still occur on recent kernels? This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22 *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs. Fedora 22 has now been rebased to 4.2.3-200.fc22. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. |
Description of problem: Recent 3.12-rcX kernel seems to be blocking lvm2 test suite - raid test stays unfinished in this place: INFO: task lvm:6827 blocked for more than 120 seconds. Not tainted 3.12.0-0.rc3.git1.1.fc21.x86_64 #1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. lvm D ffff88007532ae60 4616 6827 636 0x00000080 ffff880065acdb28 0000000000000046 00000000001d52c0 ffff880065acdfd8 ffff880065acdfd8 00000000001d52c0 ffff880065b5dcc0 ffff880074ef6a40 ffff880074ef6c78 ffff880074ef6bc0 ffff880065868e00 ffff880065868000 Call Trace: [<ffffffff81748e79>] schedule+0x29/0x70 [<ffffffffa0135f8d>] raid5_quiesce+0xbd/0x190 [raid456] [<ffffffff810a2900>] ? wake_up_atomic_t+0x30/0x30 [<ffffffff8158575b>] mddev_suspend+0xab/0xd0 [<ffffffffa01558d7>] raid_ctr+0x12b7/0x1369 [dm_raid] [<ffffffff8159f3d7>] dm_table_add_target+0x167/0x470 [<ffffffff815a24df>] table_load+0x12f/0x350 [<ffffffff815a23b0>] ? list_devices+0x180/0x180 [<ffffffff815a32f5>] ctl_ioctl+0x275/0x520 [<ffffffff815a35b3>] dm_ctl_ioctl+0x13/0x20 [<ffffffff8120aad5>] do_vfs_ioctl+0x305/0x530 [<ffffffff81216db7>] ? fget_light+0x3a7/0x510 [<ffffffff8120ad81>] SyS_ioctl+0x81/0xa0 [<ffffffff817550a9>] system_call_fastpath+0x16/0x1b 1 lock held by lvm/6827: #0: (&md->type_lock){+.+.+.}, at: [<ffffffff8159cc37>] dm_lock_md_type+0x17/0x20 Lock is held forever and device cannot be removed. Version-Release number of selected component (if applicable): 3.12.0-0.rc3.git1.1.fc21.x86_64 How reproducible: Running lvm2 test suite make check_local T=lvconvert-raid.sh VERBOSE=1 Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: