Bug 195502
Summary: | Regression: cluster mirror creation cmd hangs even though mirror gets created | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Corey Marthaler <cmarthal> |
Component: | kernel | Assignee: | Jonathan Earl Brassow <jbrassow> |
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.0 | CC: | agk, mbroz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | RHSA-2006-0575 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-08-10 23:34:03 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 180185, 181409 |
Description
Corey Marthaler
2006-06-15 15:06:54 UTC
This is the kernel bug that I will be posting a patch for soon. After the device is created, lvcreate will attempt to zero out the first bunch of blocks on the device. Doing this will cause writes to colide with resync'ing regions. This causes a hang in the 2.6.9-39.EL kernel. To test and see that this is the bug I think it is, you can do 'lvcreate --nosync ...' and you should not see the hang on lvcreate. This is because --nosync says that it will not initially re-sync the mirror - meaning there can be no colision. This hang does not happen when using the --nosync on creation. please retest with kernel > 39.EL committed in stream U4 build 39.2. A test kernel with this patch is available from http://people.redhat.com/~jbaron/rhel4/ An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2006-0575.html |