Bug 173201
Summary: | Unable to close device warnings when attempting to create a snapshot | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Corey Marthaler <cmarthal> |
Component: | lvm2 | Assignee: | Alasdair Kergon <agk> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | U3 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-03-08 15:24:35 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: |
Description
Corey Marthaler
2005-11-14 21:53:36 UTC
This one looks strange. It means that in some path through the program there is a 'close' that wasn't preceded by an 'open'. I haven't reproduced it. Please can you repeat with -vvvv to produce more detailed diagnostics. Also try to reproduce it with 'vgscan -vvvv'. What sort of partition tables were on those devices, and which kernel? Ah - I've just managed to reproduce it - no need for more information. -vvvv output shows the real problem: device/dev-io.c:514 /dev/sda: Immediate close attempt while still referenced Fix added to 2.02.01 fix verified in lvm2-2.02.01-1.3.RHEL4. |