Bug 1388107 - [RFE] Investigate what to do with 'error' space
Summary: [RFE] Investigate what to do with 'error' space
Keywords:
Status: NEW
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: 2.02.166
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: LVM and device-mapper development team
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-24 13:29 UTC by Zdenek Kabelac
Modified: 2016-10-24 13:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Zdenek Kabelac 2016-10-24 13:29:37 UTC 
Description of problem:

When some LV suffers 'write' failure leg and such LV is orphaned - it should be obvious for a user this 'extent' space is toxic and shall not be reused.

Maybe we need to pvmove all remaining LV users out of such PV ? (new bz ?)

Maybe we need to support some hidden LV_bad_blocks  to accumulate space we do not wish to reuse ?


Version-Release number of selected component (if applicable):
2.02.166

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Note You need to log in before you can comment on or make changes to this bug.