Bug 1015096

Summary:	Document thinpool recover steps
Product:	Red Hat Enterprise Linux 6	Reporter:	Zdenek Kabelac <zkabelac>
Component:	lvm2	Assignee:	Zdenek Kabelac <zkabelac>
Status:	CLOSED CURRENTRELEASE	QA Contact:	cluster-qe <cluster-qe>
Severity:	low	Docs Contact:
Priority:	high
Version:	6.4	CC:	agk, cmarthal, dwysocha, heinzm, jbrassow, msnitzer, nperic, prajnoha, prockai, slevine, thornber, zkabelac
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-21 13:51:29 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:
Bug Depends On:	1007074
Bug Blocks:	917102

Description Zdenek Kabelac 2013-10-03 12:54:47 UTC

Description of problem:

Since lvm2 is not capable to recover all possible broken variants of thin pool brokenness we need to create a documentation which will provide step-by-step guide how to move-on with repair of broken pool.

lvm2 provides some useful low-level command which should allow to fix and sync broken thin pool kernel metadata with lvm2 metadata.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Alasdair Kergon 2013-10-14 23:24:41 UTC

There will be no change to the lvm2 package for this, but some documentation will be provided, perhaps as a KB article.

Comment 6 Jonathan Earl Brassow 2015-03-03 20:30:33 UTC

Information has been added to the lvmthin(7) man page to try to shed more light on what should be done when devices fail in a thin-pool.  The section "Metadata check and repair" has been added.

This is not sufficient to describe all problems though, but it should be sufficient for this release.  I won't close this bug, but I will push it to 6.8.  We can consider at that time what new information can be added.